We do not slip only on Beta or Final. In the past we had also some troubles during Mass Rebuild which were causing slip of a whole release. As I like the idea Matthew proposed I would like to expand the "Slipping policy" with a rule: If Mass Rebuild slips for a week the Beta release date moves to Beta Target #2 and Final release date moves to Final Target #2 without adding Target #3 date for Beta nor Final. Does it makes sense ? Jan On Thu, Nov 2, 2017 at 10:06 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Thu, Nov 02, 2017 at 04:40:30PM -0400, John Florian wrote: >> Call me crazy, I don't mind, but what about scheduling the release >> dates in reverse, using whatever naming scheme? Then as the release is >> finalized, we either stick to the last release date if there were lots >> of "slips" or we select an earlier release date because things went >> really well. This might then be viewed as "Fedora released on time!" >> or "Fedora released early!!!" > > > Yeah, that's basically the idea, except only building in two target > dates in advance. If we have, like, six, I'm definitely sure no one > will take the first once seriously. > > -- > Matthew Miller > <mattdm@xxxxxxxxxxxxxxxxx> > Fedora Project Leader > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
