On Thu, Feb 13, 2014 at 8:46 AM, Georg Brandl <g.bra...@gmx.net> wrote: > Am 13.02.2014 14:15, schrieb Antoine Pitrou: >> >> Hello, >> >> So how is the RC phase supposed to work this time? Usually only critical >> patches get in, but I see a lot of commits in the last few days. > > For 3.3.0 bugfixing continued on default, and I cherry-picked patches I > considered critical enough into my release repo. The rest of the > fixes were then merged after final and made their way into 3.3.1. > > Larry has a similar plan for 3.4, and I think he will announce it here > shortly.
That sounds like a good plan to me, and if that's going to be the plan for the foreseeable future I think the devguide needs bit of an update. In particular, with this plan the absolute requirement of having another core developer review a patch before commit can be relaxed somewhat, since the RM would be reviewing any post-RC patches in any case to decide if they should make Final. Either way, some clarification would be good; I have a couple of issues that I'd like to commit, but I'm wary of doing so until current protocol is better defined. -- Zach _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
