Update documentation

sebastinas · sebastinas · commit 871d2931cf59 · 2015-02-07T01:47:21.000+01:00
Signed-off-by: Sebastian Ramacher &lt;sebastian+dev@ramacher.at&gt;
diff --git a/doc/sphinx/source/releases.rst b/doc/sphinx/source/releases.rst
@@ -5,26 +5,28 @@ Releases
 
 Release schedule
 ----------------
-bpython does not have a set release cycle. The developers will decide together when the time is ripe to release a version.
-For information what happens after the decision is made to make a release you should read the 'Release Path' section.
+bpython does not have a set release cycle. The developers will decide together
+when the time is ripe to release a version. For information what happens after
+the decision is made to make a release you should read the 'Release Path'
+section.
 
 Release Path
 ------------
-After it is decided to release a new version of bpython the following checklist is followed:
+After it is decided to release a new version of bpython the following checklist
+is followed:
 
 * The repository is frozen, nobody pushes until the version is built.
-* Bob (:ref:`authors`) makes a tarball of the new version and sends it to Simon (:ref:`authors`) who will host it on the  bpython website.
+* Bob (:ref:`authors`) makes a tarball of the new version and sends it to Simon
+  (:ref:`authors`) who will host it on the bpython website.
 * The package is then downloaded by all of the people who like to test it.
 * Everybody checks if there are no great problems:
-
-  * Version numbers correct?
-  * CHANGELOG is correct?
-  * AUTHORS?
-
-* After everybody says 'yes' the website and pypi are updated to point to this new version.
-
-  * Simon (:ref:`authors`) also checks if all numbers on the website have been updated.
-
+  - Version numbers correct?
+  - CHANGELOG is correct?
+  - AUTHORS?
+* After everybody says 'yes' the website and PyPI are updated to point to this
+  new version.
+  - Simon (:ref:`authors`) also checks if all numbers on the website have been
+    updated.
 * 24 hours later package maintainers could update their stuff.
 
 Checklist
@@ -34,7 +36,7 @@ A checklist to perform some manual tests before a release:
 
 Check that all of the following work before a release:
 
-* Runs under Python 2.6, 2.7, 3.3, and 3.4 (after 2to3).
+* Runs under Python 2.6, 2.7, 3.3, and 3.4.
 * Save
 * Rewind
 * Pastebin
