On Thu, Apr 16, 2020 at 11:07 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote:
We learned in today's Go/No-Go meeting that the late blocker
exception[1] has an edge case when the release slips. Currently, it
suggests[2] that the bug becomes a blocker for the next milestone. In
the case of a Final wallpaper bug, that doesn't make sense.
I propose the exception be changed FROM:
> Last minute blocker bugs - bugs proposed as blockers 5 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.
TO:
> Last minute blocker bugs - bugs proposed as blockers 5 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. If the release is declared go, the bug can instead be accepted as a blocker for the next milestone release. If the release is declared no-go, the bug loses last minute status.
I think this:
"If the release is declared no-go, the bug loses last minute status."
should be part of our policy. I considered it obvious, but I'm sure some people (/me looking at Frantisek) would argue. Let's put it there.
The proposed phrasing sounds ok to me, even though there is technically (since you enjoy it) a little bit of catch-22. You can't declare the release go, before you deal with all the blockers, and you can't postpone a last minute bug according to your phrasing, before you declare the release go. But it doesn't bother me too much.
Also, I think the "can be accepted" should be "must be accepted". Except the obvious case where it doesn't make sense, like the wallpapers bug. I think we don't need to codify that corner case.
_______________________________________________ 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
