[pypy-commit] pypy default: start updating for bug-fix releases

mattip pypy.commits at gmail.com
Thu Feb 25 08:39:12 EST 2016


Author: mattip <matti.picus at gmail.com>
Branch: 
Changeset: r82504:2828af388188
Date: 2016-02-25 12:58 +0100
http://bitbucket.org/pypy/pypy/changeset/2828af388188/

Log:	start updating for bug-fix releases

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
@@ -1,5 +1,20 @@
-Making a PyPy Release
-=====================
+The PyPy Release Process
+========================
+
+Release Policy
+++++++++++++++
+
+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. 
+
+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,
+so that we can then create a tagged bug-fix release, which will hopefully
+happen more often than stable releases.
+
+How to Create a PyPy Release
+++++++++++++++++++++++++++++
 
 Overview
 --------


More information about the pypy-commit mailing list