[Python-Dev] Looking for VCS usage scenarios

Brett Cannon brett at python.org
Tue Nov 4 03:33:51 CET 2008

On Mon, Nov 3, 2008 at 14:58, Barry Warsaw <barry at python.org> wrote:
> Hash: SHA1
> On Nov 3, 2008, at 5:03 PM, Brett Cannon wrote:
>> As I said, one of the scenarios already says patches can be whatever
>> the DVCS supports the best; plain diffs, branches, etc. And the
>> comments for that scenario will point out any perks from that feature.
> It's actually a profound improvement not to have to deal with traditional
> patch files as much.  The feel... dead somehow, compared to a live branch
> which can track changes to the trunk, etc.

Which I am sure will be pointed out in the scenario. I just want some
file I can attach to an issue, period. After that the perks of what
that file contains in terms of history, etc., can be enumerated.

>> As for the "via mail" feature, I use Gmail so it doesn't mean anything to
>> me. =)
> It should though.  In Bazaar, a bundle is essentially the revisions in your
> branch that are packaged to transport over RFC 2821 and 2822. :)  That opens
> up some really cool abilities, such as sending a bundle to a buildbot or
> patch queue manager for automated testing.

But this just smells of premature optimization to me. For instance, as
of this exact moment Martin is basically the only person staying on
top of the tracker. He also is typically the buildbot person as well.
And this is not from a lack of trying to get help with the tracker
multiple times. It's just people just don't stick around, as you know.

Trying to expand our buildbot infrastructure to accept patches to test
out or some patch queue manager might be nice, but I want to be
realistic with what we have now. That's why I am not worrying about
this email feature; until I know that we will actually use it and have
the manpower to implement it I consider it a perk that might never be
used. It's all great to dream about the future and what could be, but
that is far beyond just trying to get us to switch to a DVCS and is
just icing on the cake.


More information about the Python-Dev mailing list