[pypy-svn] r39074 - pypy/dist/pypy/doc
pedronis at codespeak.net
pedronis at codespeak.net
Sat Feb 17 01:15:03 CET 2007
Author: pedronis
Date: Sat Feb 17 01:15:00 2007
New Revision: 39074
Modified:
pypy/dist/pypy/doc/confrest.py
pypy/dist/pypy/doc/how-to-release.txt
Log:
formatting
Modified: pypy/dist/pypy/doc/confrest.py
==============================================================================
--- pypy/dist/pypy/doc/confrest.py (original)
+++ pypy/dist/pypy/doc/confrest.py Sat Feb 17 01:15:00 2007
@@ -1,6 +1,9 @@
import py
from py.__.doc.confrest import *
+#import docage
+
+
class PyPyPage(Page):
def fill_menubar(self):
self.menubar = html.div(
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 Sat Feb 17 01:15:00 2007
@@ -16,21 +16,25 @@
Release Steps
----------------
-* at code freeze make a release branch under http://codepeak.net/svn/pypy/release/x.y(.z). IMPORTANT: bump the pypy version number in module/sys/version.py,
- notice that the branch will capture the revision number of this change
- for the release;
- 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
+* at code freeze make a release branch under
+ http://codepeak.net/svn/pypy/release/x.y(.z). IMPORTANT: bump the
+ pypy version number in module/sys/version.py, notice that the branch
+ will capture the revision number of this change for the release;
+ 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
* 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 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/makerelease.py to make the tarballs
- on codespeak; this generates html doc for the tarballs too.
- (XXX what about tagging?)
-* 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.
+* use, after the necessary updates, dist/pypy/tool/makerelease.py to
+ make the tarballs on codespeak; this generates html doc for the
+ tarballs too. (XXX what about tagging?)
+* 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 ...
+* send announcements to pypy-dev, pypy-funding, python-list,
+ python-announce, python-dev ...
More information about the Pypy-commit
mailing list