diff options
| author | mshields@google.com <mshields@google.com@09200d28-7f98-11dd-ad27-0f66e57d2035> | 2011-02-09 23:43:00 +0000 |
|---|---|---|
| committer | mshields@google.com <mshields@google.com@09200d28-7f98-11dd-ad27-0f66e57d2035> | 2011-02-09 23:43:00 +0000 |
| commit | bdbbe2efcd912a744897eb1937e72055ec5edf08 (patch) | |
| tree | c39706ff7422e4e817bb0c5613b89ba155199d5b | |
| parent | 5ea3a17bdf7f96e6f4b667bb18eef3f14ff96d26 (diff) | |
| download | ipaddr-py-bdbbe2efcd912a744897eb1937e72055ec5edf08.tar.gz | |
Edited wiki page Releasing through web user interface.
git-svn-id: https://ipaddr-py.googlecode.com/svn@214 09200d28-7f98-11dd-ad27-0f66e57d2035
| -rw-r--r-- | wiki/Releasing.wiki | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/wiki/Releasing.wiki b/wiki/Releasing.wiki index 2014d8e..1162867 100644 --- a/wiki/Releasing.wiki +++ b/wiki/Releasing.wiki @@ -11,9 +11,10 @@ If preparing for a micro release, first switch your client to the release branch == Actually making a release == # Run `python2.4 ipaddr_test.py; python2.6 ipaddr_test.py' to double-check that everything passes. + # Write ReleaseNotes in the wiki. + # Copy the release notes to ./RELEASENOTES and commit. # Update `__version__` in ipaddr.py to a string like `'1.0.0'`, and commit to the release branch. # Tag the version: `svn copy -m'Tagging 1.0.0 release' https://ipaddr-py.googlecode.com/svn/branches/1.0.x https://ipaddr-py.googlecode.com/svn/tags/1.0.0` - # Write ReleaseNotes in the wiki. # Prepare tarball: `./setup.py sdist`. It will appear in `./dist`. # Create a [http://code.google.com/p/ipaddr-py/downloads/entry new download] on Google Code. Use the labels `Featured`, `Type-Source`, and `OpSys-All`. # Remove the `Featured` label from the previous release. Files with this label will appear on the project front page in a green box. |