On 08/02/2017 05:16 PM, Adam Williamson wrote: > Hi, folks! So I've (finally) got ready an initial round of draft > changes to various wiki pages for the purpose of implementing the 'No > More Alphas' Change. You can find all the drafts in the NoMoreAlphas > category: > > https://fedoraproject.org/wiki/Category:NoMoreAlpha ...snip.. > I do *NOT* propose to have any kind of > blocker tracking bug for the Basic release criteria; it doesn't seem to > fit in the process, there is no Alpha release to block, and we can't > realistically block nightly composes on manual test results. So a > tracker bug wouldn't really have any reason to exist. In the case where > a violation of the Basic criteria makes it into composes despite the > automated testing, it should be marked as a Beta blocker. Not that I like more bugs, but I wonder if it might be useful to have two more tracker bugs: * Compose breaking - Something that causes the compose to fail (ie, makes it so a required deliverable isn't made) and * Basic release critera breaking - Something got through the automated testing for whatever reason (we don't automatedly (is that a word) test it yet, or the test wasn't complete or something). The reason I think these might be useful is so we can look at them and see what broke things in the past and slipped past tests so we can improve them. Also, if we can upfront test some of the compose ones we might have less failures. Not a big deal, just a thought... (note that these would just be trackers not blockers, since as you point out there is nothing to block. ;) > * There is a problem with what to do about the Change schedule: our two > sources for it don't actually agree on what the schedule *is*. The > Changes Policy page - https://fedoraproject.org/wiki/Changes/Policy - > claims that the 'Completion deadline' "falls on the same day as the > Alpha milestone freeze", but the Fedora Release Life Cycle page - > https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle - claims it > falls on the same day as the branch point, which is two weeks *before* > the Alpha freeze. Given this inconsistency I didn't really feel > confident proposing a draft for the Changes/Policy page yet; probably > it'd be good for FESCo(?) as owners of the Change process to decide > when they actually want the key dates of the Change process to be, In A > World Without Alphas. If FESCo wants to figure that out and let me > know, I can draft the changes. Can you file a fesco ticket on this and mark it 'meeting' so we get it on the agenda? > > Please do look these over and provide any kind of feedback! Thanks. > kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
