[pypy-svn] r75348 - pypy/trunk/pypy/doc

[fijal at codespeak.net]

Author: fijal
Date: Sat Jun 12 23:24:54 2010
New Revision: 75348

Modified:
   pypy/trunk/pypy/doc/how-to-release.txt
Log:
Update this file. I think that's fine for now


Modified: pypy/trunk/pypy/doc/how-to-release.txt
==============================================================================
--- pypy/trunk/pypy/doc/how-to-release.txt	(original)
+++ pypy/trunk/pypy/doc/how-to-release.txt	Sat Jun 12 23:24:54 2010
@@ -4,12 +4,13 @@
 Overview
 ---------
 
-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.
+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. 
+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!
 
@@ -25,34 +26,21 @@
   necessary
 * update pypy/doc/contributor.txt (and possibly LICENSE)
 * update README
-* update pypy.org (under extradoc/pypy.org), rebuild and commit
-* build following binaries (supported versions for now):
-  JIT: windows, linux, os/x
-  no JIT: windows, linux, os/x
-  sandbox: linux, os/x
-  stackless: windows, linux, os/x
+* go to pypy/tool/release and run:
+  force-builds.py /release/<release branch>
+* wait for builds to complete, make sure there are no failures
+* run pypy/tool/release/make_release.py, this will build necessary binaries
+  and upload them to pypy.org
+
+  Following binaries should be built, however, we need more buildbots:
+    JIT: windows, linux, os/x
+    no JIT: windows, linux, os/x
+    sandbox: linux, os/x
+    stackless: windows, linux, os/x
 
-XXX stuff below is out-of-date or at least needs some review
 * write release announcement pypy/doc/release-x.y(.z).txt
   the release announcement should contain a direct link to the download page
-* update 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, pypy/tool/makerelease.py to
-  make the tarballs on codespeak; this generates html doc for the
-  tarballs too.  Use::
-     
-     makerelease -tag .z pypy-x.y.z
-
-  to tag and produce final tarballs. Without the '-tag' this can
-  be used to make pre-release testing tarballs.
-* 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. We have some support for running part of
-  our nightly tests on tarballs (see
-  http://codespeak.net/svn/user/pedronis/tarball-testing).
-* write a news item for the release in pypy/doc/news.txt
-* update http://codespeak.net/svn/pypy/dist and codespeak's
-  precomputed html files
-* send announcements to pypy-dev, pypy-funding, python-list,
+* update pypy.org (under extradoc/pypy.org), rebuild and commit
+* post announcement on morepypy.blogspot.com
+* send announcements to pypy-dev, python-list,
   python-announce, python-dev ...