[python-committers] 3.2 -> 3.3 merge pending? (original) (raw)

R. David Murray rdmurray at bitdance.com
Wed May 29 21:53:20 CEST 2013

On Wed, 29 May 2013 21:41:58 +0200, Jesus Cea <jcea at jcea.es> wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 29/05/13 16:41, R. David Murray wrote: > I asked about this on IRC and was told that 3.2 is now a > standalone branch like 2.7. Security fixes will be applied by the > release manager only, and Georg doesn't see any point in null > merging the commits. Could this be written somewhere?. For instance, how the release manager must be notified about a potential relevant changeset for his/her branch.

By making it a release blocker in the tracker. (Once it is public...I would imagine release managers have to be on the security mailing list...though I don't know that for a fact.)

I imagine there's something in the devguide about security branches, this info could be added there.

--David

More information about the python-committers mailing list