Author: Antonio Cuni <anto.c...@gmail.com>
Branch: py3.5
Changeset: r95728:75ae721dc112
Date: 2019-01-25 16:44 +0100
http://bitbucket.org/pypy/pypy/changeset/75ae721dc112/
Log: hg merge default
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
@@ -16,9 +16,6 @@
How to Create a PyPy Release
++++++++++++++++++++++++++++
-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.
@@ -28,17 +25,54 @@
Release Steps
--------------
+++++++++++++++
-* If needed, make a release branch
-* Bump the
- pypy version number in module/sys/version.py and in
- module/cpyext/include/patchlevel.h and in doc/conf.py. The branch
- will capture the revision number of this change for the release.
+Make the release branch
+------------------------
- 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.
+This is needed only in case you are doing a new major version; if not, you can
+probably reuse the existing release branch.
+
+We want to be able to freely merge default into the branch and vice-versa;
+thus we need to do a complicate dance to avoid to patch the version number
+when we do a merge::
+
+ $ hg up -r default
+ $ # edit the version to e.g. 7.0.0-final
+ $ hg ci
+ $ hg branch release-pypy2.7-7.x && hg ci
+ $ hg up -r default
+ $ # edit the version to 7.1.0-alpha0
+ $ hg ci
+ $ hg up -r release-pypy2.7-7.x
+ $ hg merge default
+ $ # edit the version to AGAIN 7.0.0-final
+ $ hg ci
+
+Then, we need to do the same for the 3.x branch::
+
+ $ hg up -r py3.5
+ $ hg merge default # this brings the version fo 7.1.0-alpha0
+ $ hg branch release-pypy3.5-7.x
+ $ # edit the version to 7.0.0-final
+ $ hg ci
+ $ hg up -r py3.5
+ $ hg merge release-pypy3.5-7.x
+ $ # edit the version to 7.1.0-alpha0
+ $ hg ci
+
+To change the version, you need to edit three files:
+
+ - ``module/sys/version.py``
+
+ - ``module/cpyext/include/patchlevel.h``
+
+ - ``doc/conf.py``
+
+
+Other steps
+-----------
+
* Make sure the RPython builds on the buildbot pass with no failures
diff --git a/pypy/module/cpyext/include/patchlevel.h
b/pypy/module/cpyext/include/patchlevel.h
--- a/pypy/module/cpyext/include/patchlevel.h
+++ b/pypy/module/cpyext/include/patchlevel.h
@@ -32,7 +32,7 @@
* module/sys/version.py
* doc/conf.py
*/
-#define PYPY_VERSION "7.1.0"
+#define PYPY_VERSION "7.1.0-alpha0"
#define PYPY_VERSION_NUM 0x07010000
/* Defined to mean a PyPy where cpyext holds more regular references
to PyObjects, e.g. staying alive as long as the internal PyPy object
diff --git a/pypy/module/sys/version.py b/pypy/module/sys/version.py
--- a/pypy/module/sys/version.py
+++ b/pypy/module/sys/version.py
@@ -13,7 +13,7 @@
# make sure to keep PYPY_VERSION in sync with:
# module/cpyext/include/patchlevel.h
# doc/conf.py
-PYPY_VERSION = (7, 1, 0, "alpha0", 0)
+PYPY_VERSION = (7, 1, 0, "alpha", 0)
import pypy
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
https://mail.python.org/mailman/listinfo/pypy-commit
