On Sun, 2009-07-26 at 20:59 -0700, John Poelstra wrote: > Mark McLoughlin said the following on 07/24/2009 05:55 AM Pacific Time: > > On Mon, 2009-07-13 at 21:09 -0700, John Poelstra wrote: > > > >> http://poelstra.fedorapeople.org/schedules/f-12/f-12-releng-tasks.html > >> http://poelstra.fedorapeople.org/schedules/f-12/f-12-releng.ics > > > > In the F-11 schedule, we had 85 days between Feature Freeze and GA. And > > then GA slipped by two weeks. > > In the F-12 schedule, we now have 99 days between Feature Freeze and GA. > > For Fedora 12 An extra week was added to accommodate Linux plumbers > conference, etc...https://fedorahosted.org/rel-eng/ticket/1271 > > In addition there are four weeks in the Fedora 12 schedule for Alpha > (previously known as Beta) versus the three weeks in Fedora 11--this was > an oversight in the setting of the Fedora 11 schedule which did not > allow for three weekly snapshots. Okay, the extra two weeks are to allow for (rel-eng?) people being missing during plumbers and to allow for a third snapshot between alpha and beta. That makes sense on the face of it, but the end result for developers is a release cycle split into a 49 day development period followed by a 99 day stablization period. That's quite conservative for a bleeding edge distro. Constructive suggestion for the next cycle - we should go back to a shorter gap between Feature Freeze and GA. Cheers, Mark. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
