On Wed, 2014-09-24 at 12:41 -0700, Adam Williamson wrote: > Again, I'd recommend a renaming here. If we call the "Branch freeze" > something else then we can simply call those points the "Alpha Freeze", > "Beta Freeze" and "Final Freeze", which are the terms used informally in > any case, and would line up with the "freeze exception policy" which > determines what stuff can break those freezes. So since this email I've been engaged in a monumental wiki slash-n-burn expedition, but I just found some history I thought might be fun to share. I found that these points were actually called "Alpha Freeze", "Beta Freeze" and "Final Freeze" up until Fedora 13, then changed for Fedora 14 as a consequence of No Frozen Rawhide. The decision was documented by John Poelstra, but actually taken rather in passing in a FESCo meeting: http://meetbot.fedoraproject.org/teams/fesco/fesco.2010-05-18-19.03.log.html there's some suggestion that No Frozen Rawhide means there isn't really strictly speaking a "freeze" any more (as Branched uses Bodhi and has an updates-testing repo which does not freeze; under the old system, Rawhide's single repository was frozen and you simply could not send builds anywhere without a freeze exception). Then notting (j'accuse!) somewhat desultorily suggests "Change deadline", it gets a couple of half-hearted acks, a vote on the entire release schedule (which is what was under discussion) is passed and the meeting moves on. So, it wasn't exactly a heartfelt choice in the first place :) Given that, and the rather unfortunate collision with the "Change" process, I feel fairly comfortable about going ahead and renaming them back to "Alpha freeze", "Beta freeze", "Final freeze", with the generic term "Milestone freeze". I've run this by jreznik, dgilmore, nirik, mattdm, and pjones (who was at the initial FESCo meeting) and they're all OK with (or in support of) the change. This doesn't affect policy in any way, it's purely a naming issue. The most prominent page that actually talks about them is probably Updates_Testing in any case, and that page still uses the 'milestone freeze' names today, it links to the "Change deadlines" page but names the links as "Alpha freeze", "Beta freeze" etc. It's also the name I've observed most people actually using in blocker meetings and suchlike, and matches the name of the "Freeze exception policy", which seemed to get much better reviews than the old "nice-to-have policy". So I think it's a pretty sensible change. I'm going ahead and doing it right now, as part of my larger wiki overhauls. I'd figure it'd be easy enough to change the names for the rest of F21 (so Beta Change Deadline becomes Beta Freeze and Final Change Deadline becomes Final Freeze) on the schedules, but we don't have to if we don't want to, it'd be easy enough to just explain that it's in transition. I take the argument about there not strictly speaking being a 'freeze' of the entire product, but it seems reasonable to simply explain in the relevant documentation (Updates_Policy, the update HOWTO, etc) that it is a freeze of the ''stable'' repository/state, not a freeze of the entire tree. We could call them "Alpha stable freeze", "Beta stable freeze" etc but I'm not sure that's really any clearer. I'll drop a mail about the other significant changes I've made to the Wiki once I'm done with it, you can follow live on my Contributions page and yell at me on IRC if you like :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
