Home Original page

[Python-Dev] Hg: inter-branch workflow

Benjamin Peterson benjamin at python.org
Mon Mar 21 22:15:19 CET 2011 
2011/3/21 Raymond Hettinger <raymond.hettinger at gmail.com>:
>
> On Mar 21, 2011, at 11:56 AM, Daniel Stutzbach wrote:
>
> People love it because it's a very powerful tool.  People hate it because it
> allows you to shoot yourself in the foot.
>
> There's a certain irony in this.   The original motivation for version
> control
> was to be a safety rope, to serve as a productivity tool to make sure
> that work never got lost.
> Now we seem to be advocating a complex, fragile workflow that
> is hard to learn, hard to get right, that let's you shoot yourself in
> the foot, and that has rebasing/collapsing steps that destroy and
> rewrite history (an possibly muck-up your repo if there was an
> intervening push).
> If we gave-up on the "svnmerge on steroids workflow",
> the use of Hg would become dirt simple.   I've used it that way
> in personal projects for a couple months and it is
> remarkably easy, taking only minutes to learn.
> It also works with Hg right out of the box; no need
> for extensions, customizations, or a slew of advanced Hg
> features.

Python, though, is not your run-of-the-mill pet project. There's
always going to be a learning curve into its development.



-- 
Regards,
Benjamin
More information about the Python-Dev mailing list