Proposal refinement of the late blocker exception

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

In other words, we can choose to waive a bug, but if it turns out we
have another week, then the bug is no longer waived. We could, of
course, later choose to waive it under the "difficult to fix"
exception when appropriate. This would allow us to just make a
decision independent of other bugs, but still allow the bug to be
fixed when the release date slips.

[1] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases
[2] I say "suggests" because the word is "can", not "must" or similar.
It's word lawyering, yes, but that's what I enjoy. :-)

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
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




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux