On Thu, Oct 30, 2008 at 06:14, Nick Coghlan
Ulrich Eckhardt wrote:
On Thursday 30 October 2008, Victor Stinner wrote:
One of the reasons why I'm very keen on us moving to a distributed version control system is to help break the logjam on core developers. Yeah, exactly :-) Does anyone already maintain a distributed tree? Mercurial, GIT, anything else?
Bazaar. Take a look at the developers' pages on python.org, they mention that a BZR checkout is available. I know that it works (though the initial checkout is glacially slow) but I don't know what "official" support it has or what is planned with it.
It's kept up to date, and will eventually move to a more complete DVCS experiment (there are also mercurial and git mirrors being maintained, but they haven't been linked from python.org yet - a trawl through the python-dev archives should turn up the links to the URLs).
The PSF's infrastructure committee isn't that big though (and all volunteers), and switching version control systems isn't exactly easy (even the migration from Sourceforge CVS to python.org SVN took quite a bit of effort from key people). The migration of all our regular workflows from the familiar centralised VCS style to a DVCS style of development promises to be pretty disruptive in the short term, no matter how beneficial it will be in the long run.
That said, with the tracker migration from Sourceforge to Roundup behind us, and a hopefully successful 3.0 release not too far away, it's probably time to start giving the idea more serious thought.
Ultimately, any complete plan for migration from SVN to a DVCS will likely need to come in the form of a meta-PEP like the one MvL wrote to justify and document the migration from CVS to SVN: http://www.python.org/dev/peps/pep-0347/
I have actually started such a PEP, so this is being worked on. -Brett