On Mon, 2019-08-12 at 22:39 +0200, Kamil Paral wrote:
> On Sat, Aug 10, 2019 at 4:04 AM Adam Williamson <firstname.lastname@example.org>
> > +++++++++++ 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.
> 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.
I thought about it and 7 days probably sounds OK, considering it also includes the weekend. I think I wouldn't increase it, but consider decreasing it if people think it's the right way to go.