[pypy-svn] r38991 - pypy/dist/pypy/doc

pedronis at codespeak.net pedronis at codespeak.net
Thu Feb 15 23:59:25 CET 2007


Author: pedronis
Date: Thu Feb 15 23:59:21 2007
New Revision: 38991

Modified:
   pypy/dist/pypy/doc/how-to-release.txt
Log:
some updates to this. we don't have a status in architecture anymore.
we have a battery of nightly builds and test runs now.



Modified: pypy/dist/pypy/doc/how-to-release.txt
==============================================================================
--- pypy/dist/pypy/doc/how-to-release.txt	(original)
+++ pypy/dist/pypy/doc/how-to-release.txt	Thu Feb 15 23:59:21 2007
@@ -5,11 +5,13 @@
 ---------
 
 As a meta rule setting up issues in the tracker for items here may help not forgetting things.
+A set of todo files may also work.
 
 Check and prioritize all issues for the release, postpone some if necessary,
 create new  issues also as necessary. A meeting (or meetings) should be organized
 to decide what things are priorities, should go in and work for the release. 
-An important thing is to get the documentation into an up-to-date state.
+
+An important thing is to get the documentation into an up-to-date state!
 
 Release Steps
 ----------------
@@ -17,16 +19,15 @@
 * at code freeze make a release branch under http://codepeak.net/svn/pypy/release/x.y(.z) ,
   some of the next updates may be done before or after branching;
   make sure things are ported back to the trunk and to the branch as necessary
-* XXX find out and list the set  of testing necessary
-* update dist/pypy/doc/contributort.txt (and possibly dist/LICENSE)
+* update dist/pypy/doc/contributor.txt (and possibly dist/LICENSE)
 * update dist/README
 * write release announcement dist/pypy/doc/release-x.y(.z).txt
-* update the status section in dist/pypy/doc/architecture.txt
 * update dist/pypy/doc/getting-started.txt links at the top
   and release number references, make sure it is generally up-to-date
 * use, after the necessary updates, dist/pypy/tool/makerealase.py to make the tarballs 
   on codespeak (XXX what about tagging the release?)
-* test the download links in dist/pypy/doc/getting-started.txt and possibly in the release announcement,
-  ask people to test them
+* nowadays we have an extensive set of nightly builds and test runs. Is probably
+  good to do some minimal testing of the tarballs, especially to check that things
+  work even outside a working copy or if some stuff is missing.
 * write a news item for the release in dist/pypy/doc/news.txt
 * send announcements to pypy-dev, pypy-funding, python-list, python-announce, python-dev ...



More information about the Pypy-commit mailing list