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!!!" Full disclosure: I'm left-handed so backwards things seem normal to me. :) On Thu, 2017-11-02 at 15:55 -0400, Matthew Miller wrote: > It turns out that the "Rain Date" concept is confusing to some people > (particularly where that idiom is not familiar). I propose that for F28 > and onward, we keep the basic concept, but ditch that term. Instead, we > use: > > * Release Date Target 1 > * Release Date Target 2 (a week later). > > As now, these will exist for both Beta and Final, and final will only > be pushed back if Beta Target 2 is missed. > > Then (and also new), if the Beta does slip past Target 2, we add a new > "Target 3". If Beta slips to Target 3, Final slips to Target 2 (and we > don't yet add a Target 3). If beta slips to Target 4, we cross off > Final Target 2 and add Final Target 3. > > I'm happy to bikeshed on calling "Target 1" something like "Early > Target". Langdon suggested just dropping any adjectives (hence just "1" > and "2", which works, but I want to balance between a feeling of "not > really important because it's a fake target" (bad!) and journalists > reporting "Fedora slipped once again, of course, because they're always > late", no matter how much we explain the process to them. > > > -- > Matthew Miller > <mattdm@xxxxxxxxxxxxxxxxx> > Fedora Project Leader > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
