On second though, go back to the old order.

pep-3108.txt

@@ -958,13 +958,6 @@ example of how to approach this.
 Python 2.6
 //////////
 
-#. Update all import statements in the stdlib to use the new name.
-
-#. Rename the module in the documentation (both its own and all
-   references).
-
-#. Commit the changes (this checkin should be allowed to propagate to py3k).
-
 #. Use ``svn move`` to rename the module.
 
 #. Create a stub module in ``Lib/lib-old``::
@@ -979,6 +972,17 @@ Python 2.6
 
 #. Add a test to ``test_py3kwarn``.
 
+#. Add an entry in ``Misc/NEWS``.
+
+#. Commit the changes (**block** in py3k).
+
+#. Update all import statements in the stdlib to use the new name.
+
+#. Rename the module in the documentation (both its own and all
+   references).
+
+#. Commit the changes (this checkin should be allowed to propagate to py3k).
+
 #. Add stub entries in the documentation for the old names which
    lists the module as deprecated under that name and points to the
    new name (see the module removal steps on the required steps).
@@ -987,11 +991,10 @@ Python 2.6
    ``versionchanged`` directive mentioning that the module was
    renamed in Python 2.6.
 
-#. Add an entry in ``Misc/NEWS``.
-
 #. Commit the changes (**block** in py3k).
 
 
+
 Python 3.0
 //////////