On Thu, Feb 3, 2011 at 9:35 AM, Steve Holden <st...@holdenweb.com> wrote: > Call me unadventurous, but i'd quite like to see how we get on ding things > the *right* way first.
Call me pessimistic, but I'm predicting that quite a few people (including me) will continue their existing workflow, which is to work primarily on the main development branch. Without a reasonable backporting workflow, the end result will simply be stuff not being incorporated into maintenance branches. The backport approach allows the backport to be handled by someone other than the original committer, and defers the decision on whether or not a change is suitable for a maintenance branch until a more reasonable time in the process (i.e. after you have tried it out on the developmental branch first). The recommended Mercurial way asks people to make the decision of which branch to target *far* too early in the process. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
