Am 16.01.2014 14:47, schrieb Antoine Pitrou: > On jeu., 2014-01-16 at 14:22 +0100, Georg Brandl wrote: >> Am 16.01.2014 12:17, schrieb Kristján Valur Jónsson: >> > This is such an obvious question that it probably has been raised before >> >> Oh, only once or twice for every 3.x release so far :) >> >> > but anyway: >> > >> > Why not branch 3.4 earlier than release? That is how big projects are >> > managed >> > nowadays, you create a staging branch early. >> > >> > I’d suggest branching it off at b3. There is no reason to keep all trunk >> > development frozen just because a particular version is in RC mode. >> >> There's also no reason to not use a personal clone if you want to develop a >> new feature. > > The question is less for us than for occasional contributors who see > their patches or feature requests languish on the tracker, and lose > interest.
To be honest, most patches and feature requests languish much longer than the beta period, because of lack of manpower and/or interest of a core developer. And when a core developer gets interested during the beta period, all they need to do is post "Nice patch/idea, let's discuss and commit it after feature freeze". If the contributor is put off by that, well. Georg _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
