Update the status list on PEP 512 (#149)

pep-0512.txt

@@ -534,8 +534,8 @@ library would be extremely beneficial as generating such a report can
 take quite a while to produce.
 
 There are a couple pre-existing services that provide free test
-coverage for open source projects. Which option is best is an open
-issue: `Choosing a test coverage service`_.
+coverage for open source projects. In the end, Codecov [#codecov]_ was
+chosen as the best option.
 
 
 Notifying issues of pull request comments
@@ -682,25 +682,24 @@ Required:
     (need to find out where the code lives)
   - `Update PEP 101`_ (commitment from Ned Deily to do this)
   - Email python-checkins for each commit (PR or direct)
-    (https://help.github.com/articles/managing-notifications-for-pushes-to-a-repository/;
-    need to get notifications@github.com cleared for posting)
+    (https://help.github.com/articles/managing-notifications-for-pushes-to-a-repository/)
   - Message #python-dev for each commit (PR or direct)
     (https://github.com/python/cpython/settings/hooks/new?service=irc;
     commitment from R. David Murray)
-  - Migrate buildbots to be triggered and pull from GitHub
-    (looking into requirements)
 
 * In progress
 
   - `Linking a pull request to an issue`_
     (http://psf.upfronthosting.co.za/roundup/meta/issue589;
-    review committal from Ezio Melotti)
+    field added to bugs.python.org, now need bot to notice issues in PRs)
   - `Notify the issue if a commit is made`_
     (http://psf.upfronthosting.co.za/roundup/meta/issue590;
     review committal from Ezio Melotti)
   - `Deprecate sys._mercurial`_
     (http://bugs.python.org/issue27593;
     review committal from Ned Deily)
+  - Migrate buildbots to be triggered and pull from GitHub
+    (Zach Ware is looking into requirements)
 
 * Completed
 
@@ -734,11 +733,11 @@ Optional features:
     (http://psf.upfronthosting.co.za/roundup/meta/issue592)
   - Convert b.p.o patches to GitHub PRs
     (http://psf.upfronthosting.co.za/roundup/meta/issue600)
-  - `Test coverage report`_
 
 * Completed
 
   - `A CI Service`_
+  - `Test coverage report`_
 
 
 Open Issues
@@ -794,21 +793,6 @@ The names must come from Monty Python, which is only fitting since
 Python is named after the comedy troupe.
 
 
-Choosing a test coverage service
---------------------------------
-
-Getting basic test coverage of Python's standard library can be
-created simply by using coverage.py [#coverage]_. Getting
-thorough test coverage is actually quite tricky, with the details
-outlined in the devinabox's README [#devinabox-repo]_. It would be
-best if a service could be found that would allow for thorough test
-coverage, but it might not be feasible.
-
-Free test coverage services include Coveralls [#coveralls]_ and
-Codecov [#codecov]_. Testing is occuring in the
-https://github.com/brettcannon/cpython-ci-test repository.
-
-
 Rejected Ideas
 ==============