[pypy-commit] pypy default: tweak release document

mattip pypy.commits at gmail.com
Mon Jun 5 16:49:40 EDT 2017


Author: Matti Picus <matti.picus at gmail.com>
Branch: 
Changeset: r91544:fc6cbab9b7aa
Date: 2017-06-05 23:45 +0300
http://bitbucket.org/pypy/pypy/changeset/fc6cbab9b7aa/

Log:	tweak release document

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
@@ -5,8 +5,8 @@
 ++++++++++++++
 
 We try to create a stable release a few times a year. These are released on
-a branch named like release-2.x or release-4.x, and each release is tagged,
-for instance release-4.0.1. 
+a branch named like release-pypy3.5-v2.x or release-pypy3.5-v4.x, and each
+release is tagged, for instance release-pypy3.5-v4.0.1. 
 
 After release, inevitably there are bug fixes. It is the responsibility of
 the commiter who fixes a bug to make sure this fix is on the release branch,
@@ -33,7 +33,7 @@
 * If needed, make a release branch
 * Bump the
   pypy version number in module/sys/version.py and in
-  module/cpyext/include/patchlevel.h and . The branch
+  module/cpyext/include/patchlevel.h and in doc/conf.py. 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


More information about the pypy-commit mailing list