Switch to pbr as a build system

This automates the manual dance around version numbers for less maintenance pain.

The main visible changes are:
- requirements are in requirements.txt for now
- tags must be just x.y.z not testtools-x.y.z
- version information in __init__ is dynamically looked up.
- we can probably cleanup a bunch of our bootstrap import glue but in
  the interest of clear reviews, and avoiding surprises, I'm leaving
  that alone for now.

Change-Id: Ia54f681b50764a94ada68a6b2ac1bc77bfb619c5

1 files changed, 1 insertions, 5 deletions

diff --git a/doc/hacking.rst b/doc/hacking.rst
index ccfc155..3d41ab8 100644
--- a/doc/hacking.rst
+++ b/doc/hacking.rst
@@ -169,20 +169,16 @@ Tasks
 +++++
 
 #. Choose a version number, say X.Y.Z
-#. In trunk, ensure __init__ has version ``(X, Y, Z, 'final', 0)``
 #. Under NEXT in NEWS add a heading with the version number X.Y.Z.
 #. Possibly write a blurb into NEWS.
 #. Commit the changes.
-#. Tag the release, ``git tag -s testtools-X.Y.Z``
+#. Tag the release, ``git tag -s X.Y.Z -m "Releasing X.Y.Z"``
 #. Run 'make release', this:
    #. Creates a source distribution and uploads to PyPI
    #. Ensures all Fix Committed bugs are in the release milestone
    #. Makes a release on Launchpad and uploads the tarball
    #. Marks all the Fix Committed bugs as Fix Released
    #. Creates a new milestone
-#. Change __version__ in __init__.py to the probable next version.
-   e.g. to ``(X, Y, Z+1, 'dev', 0)``.
-#. Commit 'Opening X.Y.Z+1 for development.'
 #. If a new series has been created (e.g. 0.10.0), make the series on Launchpad.
 #. Push trunk to Github, ``git push --tags origin master``