Create coverage-X.Y aliases also. Closes #111.

1 files changed, 6 insertions, 3 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index 7f77a131..bc54896e 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -27,9 +27,11 @@ Version 3.5.4b1
 - Embarrassingly, the `[xml] output=' setting in the .coveragerc file simply
   didn't work.  Now it does.
 
-- When installing, now in addition to creating a "coverage" command, a
-  "coverage2" or "coverage3" command will be created, depending on whether you
-  are installing in Python 2.x or 3.x.  Thanks, Julian Berman.
+- When installing, now in addition to creating a "coverage" command, two new
+  aliases are also installed.  A "coverage2" or "coverage3" command will be
+  created, depending on whether you are installing in Python 2.x or 3.x.
+  A "coverage-X.Y" command will also be created corresponding to your specific
+  version of Python.  Closes `issue 111`.
 
 - On Windows, files are now reported in their correct case, fixing `issue 89`_
   and `issue 203`_.
@@ -56,6 +58,7 @@ Version 3.5.4b1
 - Other minor bugs fixed: `issue 153`_.
 
 .. _issue 89: https://bitbucket.org/ned/coveragepy/issue/89/on-windows-all-packages-are-reported-in
+.. _issue 111: https://bitbucket.org/ned/coveragepy/issue/111/when-installing-coverage-with-pip-not
 .. _issue 139: https://bitbucket.org/ned/coveragepy/issue/139/easy-check-for-a-certain-coverage-in-tests
 .. _issue 143: https://bitbucket.org/ned/coveragepy/issue/143/omit-doesnt-seem-to-work-in-coverage
 .. _issue 153: https://bitbucket.org/ned/coveragepy/issue/153/non-existent-filename-triggers