On Thu, Feb 3, 2011 at 6:30 AM, Barry Warsaw <ba...@python.org> wrote: >>Just exactly the reverse of current workflow. > > And for good reason (IMO). It's often much less clear exactly how far back a > specific patch should be committed when it's first being developed. It makes > much more sense to me to fix a problem in the current development branch > first, and then determine if, how, and where the patch should be back ported.
Indeed. Mainline is the only branch where we *know* most patches need to be applied. It also means that people can contribute while maintaining only a single checkout, rather than necessarily needing all active versions. I suspect this problem with the preferred DVCS workflow is going to cut fairly heavily into the number of bug fixes applied to the maintenance branches. 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
