Tweaks for the 3.4 release.

1 files changed, 29 insertions, 16 deletions

diff --git a/doc/changes.rst b/doc/changes.rst
index 47e6e28c..e5c44037 100644
--- a/doc/changes.rst
+++ b/doc/changes.rst
@@ -15,6 +15,7 @@ Major change history for coverage.py
 :history: 20100725T211700, updated for 3.4.
 :history: 20100820T151500, updated for 3.4b1
 :history: 20100906T133800, updated for 3.4b2
+:history: 20100919T163400, updated for 3.4 release.
 
 These are the major changes for coverage.py.  For a more complete change
 history, see the `CHANGES.txt`_ file in the source tree.
@@ -22,8 +23,10 @@ history, see the `CHANGES.txt`_ file in the source tree.
 .. _CHANGES.txt: http://bitbucket.org/ned/coveragepy/src/tip/CHANGES.txt
 
 
-Version 3.4 beta --- 6 September 2010
--------------------------------------
+Version 3.4 --- 19 September 2010
+---------------------------------
+
+Controlling source:
 
 - BACKWARD INCOMPATIBILITY: the ``--omit`` and ``--include`` switches now take
   file patterns rather than file prefixes, closing `issue 34`_ and `issue 36`_.
@@ -38,18 +41,16 @@ Version 3.4 beta --- 6 September 2010
   to control what modules it measures.  This can speed execution and reduce the
   amount of data during reporting. Thanks Zooko.
 
-- Completely unexecuted files can now be included in coverage results, reported
-  as 0% covered.  This only happens if the --source option is specified, since
-  coverage.py needs guidance about where to look for source files.
-
-- Various warnings are printed to stderr for problems encountered during data
-  measurement: if a ``--source`` module has no Python source to measure, or is
-  never encountered at all, or if no data is collected.
-
 - The reporting commands (report, annotate, html, and xml) now have an
   ``--include`` switch to restrict reporting to modules matching those file
   patterns, similar to the existing ``--omit`` switch. Thanks, Zooko.
 
+Reporting:
+
+- Completely unexecuted files can now be included in coverage results, reported
+  as 0% covered.  This only happens if the --source option is specified, since
+  coverage.py needs guidance about where to look for source files.
+
 - Python files with no statements, for example, empty ``__init__.py`` files,
   are now reported as having zero statements instead of one.  Fixes `issue 1`_.
 
@@ -67,16 +68,30 @@ Version 3.4 beta --- 6 September 2010
   fixing `issue 65`_ and `issue 81`_, and the report is sorted by package
   name, fixing `issue 88`_.
 
+- The XML report is now sorted by package name, fixing `issue 88`_.
+
 - The precision of reported coverage percentages can be set with the
   ``[report] precision`` config file setting.  Completes `issue 16`_.
 
+- Line numbers in HTML source pages are clickable, linking directly to that
+  line, which is highlighted on arrival.  Added a link back to the index page
+  at the bottom of each HTML page.
+
+Execution and measurement:
+
+- Various warnings are printed to stderr for problems encountered during data
+  measurement: if a ``--source`` module has no Python source to measure, or is
+  never encountered at all, or if no data is collected.
+
+- Doctest text files are no longer recorded in the coverage data, since they
+  can't be reported anyway.  Fixes `issue 52`_ and `issue 61`_.
+
 - Threads derived from ``threading.Thread`` with an overridden `run` method
   would report no coverage for the `run` method.  This is now fixed, closing
   `issue 85`_.
 
-- Line numbers in HTML source pages are clickable, linking directly to that
-  line, which is highlighted on arrival.  Added a link back to the index page
-  at the bottom of each HTML page.
+- Programs that exited with ``sys.exit()`` with no argument weren't handled
+  properly, producing a coverage.py stack trace.  This is now fixed.
 
 - Programs that call ``os.fork`` will properly collect data from both the child
   and parent processes.  Use ``coverage run -p`` to get two data files that can
@@ -85,9 +100,6 @@ Version 3.4 beta --- 6 September 2010
 - When measuring code running in a virtualenv, most of the system library was
   being measured when it shouldn't have been.  This is now fixed.
 
-- Doctest text files are no longer recorded in the coverage data, since they
-  can't be reported anyway.  Fixes `issue 52`_ and `issue 61`_.
-
 .. _issue 1:  http://bitbucket.org/ned/coveragepy/issue/1/empty-__init__py-files-are-reported-as-1-executable
 .. _issue 16: http://bitbucket.org/ned/coveragepy/issue/16/allow-configuration-of-accuracy-of-percentage-totals
 .. _issue 34: http://bitbucket.org/ned/coveragepy/issue/34/enhanced-omit-globbing-handling
@@ -102,6 +114,7 @@ Version 3.4 beta --- 6 September 2010
 .. _issue 85: http://bitbucket.org/ned/coveragepy/issue/85/threadrun-isnt-measured
 .. _issue 88: http://bitbucket.org/ned/coveragepy/issue/88/xml-report-lists-packages-in-random-order
 
+
 Version 3.3.1 --- 6 March 2010
 ------------------------------