Update PEP 374 to talk about DVCS decision, and point to PEP 385 for migration details.

pep-0374.txt

@@ -1,11 +1,12 @@
 PEP: 374
-Title: Migrating from svn to a distributed VCS
+Title: Chosing a distributed VCS for the Python project
 Version: $Revision$
 Last-Modified: $Date$
 Author: Brett Cannon <brett@python.org>,
         Stephen J. Turnbull <stephen@xemacs.org>,
         Alexandre Vassalotti <alexandre@peadrop.com>,
-        Barry Warsaw <barry@python.org>
+        Barry Warsaw <barry@python.org>,
+        Dirkjan Ochtman <dirkjan@ochtman.nl>
 Status: Active
 Type: Process
 Content-Type: text/x-rst
@@ -13,10 +14,6 @@ Created: 07-Nov-2008
 Post-History: 07-Nov-2008
               22-Jan-2009
 
-.. warning::
-   This PEP is in the draft stages and is still under active
-   development.
-
 
 Rationale
 =========
@@ -1453,18 +1450,28 @@ XXX ... usage on top of svn, filling in `Coordinated Development of a
 New Feature`_ scenario
 
 
-
 Chosen DVCS
 ===========
 
-XXX
+At PyCon 2009, a `decision
-::
+<http://mail.python.org/pipermail/python-dev/2009-March/087931.html>`_
+was made to go with Mercurial.
 
-    import random
+The choice to go with Mercurial was made for three important reasons:
-    print(random.choice(['svn', 'bzr', 'hg', 'git']))
 
+* According to a small survey, Python developers are more interested in
+  using Mercurial than in Bazaar or Git.
 
-Transition Plan
+* Mercurial is written in Python, which is congruent with the python-dev
-===============
+  tendency to 'eat their own dogfood'.
 
-XXX
+* Mercurial is significantly faster than bzr (it's slower than git, though
+  by a much smaller difference).
+
+* Mercurial is easier to learn for SVN users than bzr.
+
+Although all of these points can be debated, in the end a pronouncement from
+the BDFL was made to go with hg as the chosen DVCS for the Python project. A
+detailed plan for the migration strategy has been deferred to `PEP 385`_.
+
+.. _PEP 385: http://www.python.org/dev/peps/pep-0385/