[python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

Nick Coghlan ncoghlan at gmail.com
Wed Feb 2 23:54:40 CET 2011


On Thu, Feb 3, 2011 at 6:30 AM, Barry Warsaw <barry at 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   |   ncoghlan at gmail.com   |   Brisbane, Australia


More information about the python-committers mailing list