In article <4de47a7a.1060...@v.loewis.de>, "Martin v. Löwis" <mar...@v.loewis.de> wrote: > Am 30.05.2011 23:36, schrieb Benjamin Peterson: > > 2011/5/30 Victor Stinner <victor.stin...@haypocalc.com>: > >> Le dimanche 29 mai 2011 22:55:17, Benjamin Peterson a écrit : > >>> Hi, > >>> I'm going to start spinning those releases now. I'll make a branch for > >>> 2.7.2 but not for 3.1.4. Please stop committing to 3.1; it's going > >>> into security only mode. > >> > >> I would like to commit something into the 2.7 branch. The NEWS file starts > >> with: > >> > >> What's New in Python 2.7.2? > >> =========================== > >> > >> *Release date: 2011-05-29* > >> > >> Python 2.7.2 was released yesterday, or was it the RC1? > >> > >> I don't care if my commit (better fix for #1195) doesn't go into Python > >> 2.7.2, > >> so should I start an empty "Python 2.7.3" section? > > > > Yes, go ahead. > > Really??? I have some changes that I need to commit to 2.7 that do need > to go into 2.7.2. So how are you going to manage these? > > I rather recommend that the 2.7 branch is frozen until the final > release, and any changes are only merged afterwards.
I would think the easiest approach is to have a 2.7.2 releasing branch where changes for 2.7.2 are applied and immediately merged into the main 2.7 branch. It's trivial to create such a branch off of the 2.7.2rc1 tag but (I think) you wouldn't be able to push the resulting repo into the main repo because it creates a new head. and there's a hook to prevent that. Someone would have to create it specially. -- Ned Deily, n...@acm.org _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
