From Fedora Project Wiki

Revision as of 01:54, 23 January 2013 by Adamwill (talk | contribs) (convert to the 'freeze exception' wording and the new alias names / whiteboard fields)


Fedora uses a system of tracker bugs to keep track of freeze exception bugs - bugs which do not block a given pre-release or release, but which are considered high priority for tracking and fixing, and for which fixes may be accepted even during the freeze period for that release. This page defines the process by which bugs are proposed, reviewed and accepted as freeze exception bugs, and how freeze exception bugs are then tracked.

Note that freeze exception bugs used to be called nice-to-have or NTH bugs, and you may still find this name mentioned or used here and there.

See also the blocker bug process, which defines the similar process for blocker bugs - bugs that are blocking the release of its pre- and final releases and which must be fixed before these releases can proceed.

Freeze exception bug principles

Strict Fedora_Release_Criteria are used to define whether a bug should block a Fedora release, but determining whether a bug is worthy of a freeze exception is a more flexible process and should be done on a case-by-case basis. However, we have evolved some principles to be taken into account when evaluating a bug for freeze exception status.

In general, freeze exception bugs are usually bugs for which an update is not an optimal solution, and for which the fix is reasonably small and testable (this consideration becomes progressively more important as a release nears, so bugs may be downgraded from freeze exception status late in the release process if it transpires that the fix is complex and hard to test).

Types of bugs which are typically likely to be accepted as freeze exception bugs include:

  1. bugs which constitute infringements of the desktop-related Fedora_Release_Criteria as applied to non-default desktops
  2. bugs which result in a system being unable to reach a graphical environment
  3. significant installer bugs which do not meet the criteria to be blocker bugs

Proposing freeze exception bugs

To propose a bug as a freeze exception for a release, mark it as blocking the tracker bug for freeze exception bugs in that release. To do this, enter the alias or bug ID of the tracker bug into the Blocks: field in Bugzilla. The aliases for the freeze exception tracker bugs follow a consistent naming scheme. For the next release, the Alpha tracker will always be called AlphaFreezeException, the Beta tracker will always be called BetaFreezeException, and the final release tracker will always be called FinalFreezeException. Rarely, you may need to propose a bug as a freeze exception for the next release but one - in this case, prepend FXX (where XX is the release number) to the name of the alias and change Exception to Except, e.g. F31AlphaFreezeExcept. So, to mark a bug as a freeze exception for the release of Fedora 30 Beta, you would set it to block the bug BetaFreezeException.

Must use Red Hat Bugzilla
Only bugs reported against a Fedora component in Red Hat Bugzilla can be marked as freeze exceptions for a Fedora release. If the bug you wish to mark as a freeze exception is being tracked in an upstream bug tracking system, you must file a corresponding bug in the Fedora bug tracking system before proposing it.

Reviewing freeze exception bugs

Proposed freeze exception bugs are reviewed and either accepted or rejected in collaboration between the three stakeholder groups: QA, Development and ReleaseEngineering. This is mostly done during the weekly blocker review meeting. Blocker review meetings usually occur every Friday during release periods, but special review meetings can be scheduled at other times when necessary. When appropriate, proposed freeze exception bugs may also be reviewed between meetings or during other meetings, such as the engineering readiness meeting (also known as a go/no-go meeting) which is convened to decide whether a release candidate should be approved as a final release. In these cases, consensus between the three stakeholder groups should still be reached in order to accept or reject a bug as a freeze exception.

Bugs that are accepted as freeze exceptions for the relevant release will be marked with the Whiteboard field AcceptedFreezeException. Bugs which are rejected will be updated to no longer block the relevant tracker bug, and have the RejectedFreezeException Whiteboard field added so that if they are proposed again, it is clear they have already been considered and rejected. Therefore, a bug which has been proposed but not accepted or rejected can be identified by the lack of a relevant Whiteboard field. All changes to freeze exception status should also be documented with a comment.

Tracking freeze exception bugs

Again, tracking freeze exception bugs and making a best effort to fix them is a collaborative effort between the QA, Development and Release Engineering groups. After blocker bugs, QA group members are encouraged to prioritize testing of freeze exception bug fixes, development group members are encouraged to prioritize developing fixes for freeze exception bugs, and release engineering group members are encouraged to prioritize the release of fixes for freeze exception bugs (after appropriate testing). Each group should have its own processes for ensuring its responsibilities in relation to freeze exception bugs are met.

In Bugzilla, freeze exception bugs should follow the normal workflow, with special attention paid by the development group to submitting proposed fixes to the updates-testing repository so they reach MODIFIED and ON_QA status, and special attention paid by the QA group to testing proposed fixes and setting ones that are tested successfully to the VERIFIED status. Builds that fix freeze exception bugs should be pulled into TC and RC builds by the release engineering team as long as they are submitted as proposed updates and meet the necessary karma requirements. No freeze exception bug should be set to CLOSED ERRATA until a fix is actually released to the stable repository for the release in question: if a working fix is added to a test candidate or release candidate build, but not yet pushed to the stable repository, the bug should not be marked CLOSED ERRATA, as this may result in the fix not being pushed to the stable repository and the fix accidentally omitted from the next candidate build as it is no longer possible to track the bug.