Nearing 3.2b1

3 files changed, 9 insertions, 9 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index ff1ee52..7b9b2b1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -2,18 +2,18 @@
 Change history for Coverage.py

 ------------------------------

 

-Next version

-------------

+Version 3.2b1, 10 November 2009

+-------------------------------

+

+- Branch coverage!

 

-- Branch coverage.

+- XML reporting has file paths that let Cobertura find the source code.

 

 - The tracer code has changed, it's a few percent faster.

 

 - Some exceptions reported by the command line interface have been cleaned up

-  so that tracebacks inside coverage.py aren't shown.  Fixes `issue 23`_

+  so that tracebacks inside coverage.py aren't shown.  Fixes `issue 23`_.

   

-- XML reporting has file paths that let Cobertura find the source code.

-

 .. _issue 23: http://bitbucket.org/ned/coveragepy/issue/23

   

 

diff --git a/coverage/__init__.py b/coverage/__init__.py
index 16db463..bf0f302 100644
--- a/coverage/__init__.py
+++ b/coverage/__init__.py
@@ -5,7 +5,7 @@ http://nedbatchelder.com/code/coverage
 
 """
 
-__version__ = "3.2a1"    # see detailed history in CHANGES.txt
+__version__ = "3.2b1"    # see detailed history in CHANGES.txt
 
 __url__ = "http://nedbatchelder.com/code/coverage"
 
diff --git a/doc/branch.rst b/doc/branch.rst
index 9b03861..32f7b92 100644
--- a/doc/branch.rst
+++ b/doc/branch.rst
@@ -42,8 +42,8 @@ file is an execution opportunity, as is each branch destination.
 
 Currently, only HTML reports give information about which lines had missing
 branches.  Lines that were missing some branches are shown in yellow, with an
-annotation at the far right of branch destination line numbers that were not
-exercised.
+annotation at the far right showing branch destination line numbers that were
+not exercised.
 
 
 How it works