[pypy-svn] pypy default: edit how to release to include changing the tracker so we don't make that mistake again (no way for people to file bugs against the new release)
lac
commits-noreply at bitbucket.org
Sun May 1 07:44:47 CEST 2011
Author: Laura Creighton <lac at openend.se>
Branch:
Changeset: r43819:d5b7af1357f8
Date: 2011-05-01 07:44 +0200
http://bitbucket.org/pypy/pypy/changeset/d5b7af1357f8/
Log: edit how to release to include changing the tracker so we don't make
that mistake again (no way for people to file bugs against the new
release)
diff --git a/pypy/doc/how-to-release.rst b/pypy/doc/how-to-release.rst
--- a/pypy/doc/how-to-release.rst
+++ b/pypy/doc/how-to-release.rst
@@ -31,6 +31,7 @@
necessary
* update pypy/doc/contributor.txt (and possibly LICENSE)
* update README
+* change the tracker to have a new release tag to file bugs against
* go to pypy/tool/release and run:
force-builds.py /release/<release branch>
* wait for builds to complete, make sure there are no failures
More information about the Pypy-commit
mailing list