In the last QA team meeting (04/29/2019) I volunteered to help with
adding something to the blocker bug process to handle Last Minute
I started by reading:
Followed by: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
I agree that the provisions for how to handle last minute proposed
blocker bugs should be in the Blocker Bug Process rather than Blocker
Here's my draft:
Exceptions for Last Minute Proposed Blocker Bugs
Last Minute Proposed Blocker Bugs must meet Blocker Bug Criteria before
being processed per this section.
Last Minute Blocker Bugs shall be evaluated for being delayed to the
next release cycle according to the criteria below. Last Minute Proposed
Blocker Bugs that meet any of the listed criteria may be delayed to the
next release cycle as Blocker Bugs if the Release Team agrees. Other
Last Minute Proposed Blocker Bugs must be corrected before the current
cycle Final Release.
1) Any bug that can not be fixed in a reasonable amount of time
considering the current Release Cycle or due to complexity or resource
2) Any bug in non-vital system operation or release package installed
Delaying the current Release:
Delaying the current release cycle must take into account all of the
1) Consider if the cause of the delay should have been caught earlier in
the current cycle. What changes in process could help moving such
discoveries earlier in the cycle?
2) Adding the current proposed delay to any prior delays, is the total
delay becoming unacceptable in regard to Fedora release policy?
3) Will the current proposed delay enable other desirable work to be
completed for the release?
4) Impact on down stream projects.
Looking forward to your feedback.
Have a Great Day!