[python-committers] branches and merging

[Dirkjan Ochtman]

On Tue, Mar 2, 2010 at 15:17, Barry Warsaw <barry at python.org> wrote:
> We really need to move to a dvcs for development sooner rather than later.
> It's been a year since the decision was made.  I understand that it will suck
> for Windows developers in the short term, but with all the discussion about
> the PSF paying for pdo infrastructure work, I think getting us off of
> Subversion would have the most immediate positive impact for development of
> Python.  If the EOL issue is the holdup, what can we do *right now* to break
> that logjam?  Can't the PSF pay somebody to make this happen?

For the EOL issue, there is code, it needs testing. Martin Geisler
(the primary author so far) and I issued a call for testing on
python-dev last week, but without any response so far. As for paying
someone, I have a full-time job already, so I don't really have the
time to do consulting. I could ask around for other Mercurial team
members, but I'm not sure there's much point to it if no one is
testing the extension that exists right now.

The other thing is that I need a good way to prune branches. I wrote
up some code to do branch renaming last week, but there's another
issue to tackle. Meanwhile, I've been busy with moving ahead on the
Jython conversion, since they don't have the EOL requirements at this
time. I hope to complete that project this week. I've also been
setting up some infrastructure last week, to make it usable for
distutils2/unittest2. I set up changegroup (i.e. push) emails to
python-checkins for distutils2 last night, but I'm not sure the first
email got through (might be stuck in moderation?).

Cheers,

Dirkjan