testtools-dev team mailing list archive

[Jonathan Lange <jml@xxxxxxxxx>]

Jonathan Lange has proposed merging lp:~jml/testtools/release-improvements into lp:testtools.

Requested reviews:
  testtools developers (testtools-dev)


Fixes to bug 623483 and bug 623487.  Makes the release process smoother by making the documentation on how to release include tagging steps, and makes setup.py correctly provide license and readme info.
-- 
https://code.launchpad.net/~jml/testtools/release-improvements/+merge/38649
Your team testtools developers is requested to review the proposed merge of lp:~jml/testtools/release-improvements into lp:testtools.

=== modified file 'HACKING'
--- HACKING	2010-05-13 12:39:18 +0000
+++ HACKING	2010-10-17 11:11:44 +0000
@@ -111,30 +111,20 @@
 Release tasks
 -------------
 
-In no particular order:
-
-* Choose a version number.
-
-* Ensure __init__ has that version.
-
-* Add a version number to NEWS immediately below NEXT.
-
-* Possibly write a blurb into NEWS.
-
-* Replace any additional references to NEXT with the version being released.
-  (should be none).
-
-* Create a source distribution and upload to pypi ('make release').
-
-* Upload to Launchpad as well.
-
-* If a new series has been created (e.g. 0.10.0), make the series on Launchpad.
-
-* Merge or push the release branch to trunk.
-
-* Make a new milestone for the *next release*. We don't really know how we want
-  to handle these yet, so this is a suggestion not actual practice:
-
-  * during release we rename NEXT to $version.
-
-  * we call new milestones NEXT.
+ 1. Choose a version number, say X.Y.Z
+ 1. Branch from trunk to testtools-X.Y.Z
+ 1. In testtools-X.Y.Z, ensure __init__ has version X.Y.Z.
+ 1. Replace NEXT with the version number X.Y.Z, adjusting the reST.
+ 1. Possibly write a blurb into NEWS.
+ 1. Replace any additional references to NEXT with the version being
+    released. (should be none).
+ 1. Commit the changes.
+ 1. Tag the release, bzr tag testtools-X.Y.Z
+ 1. Create a source distribution and upload to pypi ('make release').
+ 1. Upload to Launchpad as well.
+ 1. Merge the release branch testtools-X.Y.Z into trunk. Before the commit,
+    add a NEXT heading to the top of NEWS. Push trunk to Launchpad.
+ 1. If a new series has been created (e.g. 0.10.0), make the series on Launchpad.
+ 1. Make a new milestone for the *next release*.
+    1. During release we rename NEXT to $version.
+    1. We call new milestones NEXT.

=== modified file 'setup.py'
--- setup.py	2009-12-13 00:34:05 +0000
+++ setup.py	2010-10-17 11:11:44 +0000
@@ -2,6 +2,8 @@
 """Distutils installer for testtools."""
 
 from distutils.core import setup
+import os
+
 import testtools
 version = '.'.join(str(component) for component in testtools.__version__[0:3])
 phase = testtools.__version__[3]
@@ -15,11 +17,19 @@
         # Preserve the version number but give it a revno prefix
         version = version + '~%s' % t.branch.revno()
 
+
+def get_long_description():
+    manual_path = os.path.join(os.path.dirname(__file__), 'MANUAL')
+    return open(manual_path).read()
+
+
 setup(name='testtools',
       author='Jonathan M. Lange',
       author_email='jml+testtools@xxxxxxxxx',
       url='https://launchpad.net/testtools',
       description=('Extensions to the Python standard library unit testing '
                    'framework'),
+      long_description=get_long_description(),
       version=version,
+      classifiers=["License :: OSI Approved :: MIT License"],
       packages=['testtools', 'testtools.testresult', 'testtools.tests'])