From Fedora Project Wiki

Revision as of 21:56, 24 September 2014 by Adamwill (talk | contribs) (add a 'schedule' section (to FE and blocker SOPs) to help people understand the process and link in to other docs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Template documentation [edit]

This documentation is transcluded from Template:Blocker freeze exception schedule/doc. It will not be transcluded on pages that use this template.
This template is used to share very similar content between the QA:SOP_blocker_bug_process and the QA:SOP_freeze_exception_bug_process, for efficiency and consistency.

Schedule

Or, when does this process affect me?

The process of nominating and reviewing $TYPE bugs is active to some degree at all times. It is particularly visible, however, after the Change_deadlines for each milestone of a release (Alpha, Beta, Final). At the Change deadline, the 'stable' package repository is frozen, meaning packages can no longer move from the updates-testing repository to the stable repository from which the test compose and release candidate builds are created.

If a Fedora milestone release is currently in the post-Change deadline stage (you can check the schedule for the next release here) and you are a packager or tester and you believe a build of your package or a package you are testing should be in the milestone release, this process concerns you. After the Change deadline, the build can only be promoted to 'stable' and included in the release if it fixes a bug that is granted blocker or freeze exception status.

After the milestone release is finished, the Change deadline freeze is lifted and builds can move to 'stable' again without following this process, so if the build can wait until after the milestone release, you do not need to follow this process.

Retrieved from "https://fedoraproject.org/w/index.php?title=Template:Blocker_freeze_exception_schedule&oldid=388646"