Update changelog and release process

CHANGELOG.rst

@@ -1,12 +1,12 @@
-0.4.5 In progress, unreleased
+0.4.5 Current release
   * Catch a racy ValueError that could occur on exit.
   * Create README-hacking.md, for Colorama contributors.
   * Tweak some README unicode characters that don't render correctly on PyPI.
   * Fix some tests that were failing on some operating systems.
   * Add support for Python 3.9.
   * Add support for PyPy3.
   * Add support for pickling with the ``dill`` module.
-0.4.4 Current release
+0.4.4
   * Re-org of README, to put the most insteresting parts near the top.
   * Added Linux makefile targets and Windows powershell scripts to
     automate bootstrapping a development environment, and automate the

README-hacking.md

@@ -67,8 +67,10 @@ target.
 ## Release checklist
 
 1. Check the CHANGELOG is updated with everything since the last release.
+   Update CHANGELOG.rst with the new release version (move the comment for
+   "Current release")
 
-2. First we'll make a candidate release. Ensure  the '-candidate1' suffix is
+2. First we'll make a candidate release. Ensure  the '.rc1' suffix is
    present on `__version__` in `colorama/__init.py__.py`.
 
 3. Run the tests locally on your preferred OS, just to save you from doing
@@ -124,7 +126,7 @@ target.
 11. Maybe wait a day for anyone using pre-release installs to report any
     problems?
 
-12. Remove the '.candidateX' suffix from `__version__` in
+12. Remove the '.rcX' suffix from `__version__` in
     `colorama/__init__.py`.
 
 13. Repeat steps 5 to 10, for the actual (non-candidate) release.
@@ -136,4 +138,3 @@ target.
 
     so that any build artifacts created are clearly labelled as not a real
     release. Commit and push this (directly to master is fine.)
-