On Mon, 2019-08-12 at 22:39 +0200, Kamil Paral wrote: > On Sat, Aug 10, 2019 at 4:04 AM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> > wrote: > > > > > +++++++++++ DRAFT START +++++++++++ > > > > === Exceptional cases === > > > > Generally speaking, any bug that is agreed to be a violation of the > > [[Fedora Release Criteria|release criteria]] should be accepted as a > > blocker bug for the next relevant milestone release. However, bearing > > in mind the [[Fedora_Release_Life_Cycle|Fedora life cycle's]] emphasis > > on '''both''' time '''and''' quality, in some cases we may make an > > exception. There are two main categories of bug that may be > > 'exceptional': > > > > # '''Last minute blocker bugs''' - bugs proposed as blockers 7 days or > > fewer before the scheduled [[Go_No_Go_Meeting]] for a milestone release > > (Beta or Final) can be considered under this policy, as there are some > > circumstances in which we believe it is not sensible to delay an > > otherwise-impending release to fix a bug which would usually be > > accepted as a blocker if discovered earlier. In these circumstances, > > the bug can instead be accepted as a blocker for the ''next'' milestone > > release. [snip] > That's very well written and I don't have any concerns about its wording. > I'm a bit hesitant whether 7 is the right number, but we can try it and see. I should've called that up for discussion more prominently, I guess. Yes, I just picked that number out of the air, it's absolutely up for debate. Do you think it should be a bigger number or a smaller number? :) I wondered about whether to build in some fudge space here - say the number's a guideline and we can go beyond it if we think it's a good idea - but worried that might be a bit too messy. > Whether this new policy is a good idea, that's a separate question. The > idealist in me cries every time we sacrifice quality. And this policy will > probably result in more bugs being waved compared to the past. However, I > feel it's better to have the rules formalized than to wave such bugs > without any real grounds and feel like cheating on our policies every time > we actually need waive something. FWIW my intent would be to use this no more often than we currently do this in a non-formalized way. But of course it's possible that having it written down will make us use it more, that's a risk indeed. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
