From Fedora Project Wiki

(use the new milestone freeze name (i'l make the page any time now, honest))
(no more TCs)
Line 3: Line 3:
 
Or, '''when does this process affect me?'''
 
Or, '''when does this process affect me?'''
  
The process of nominating and reviewing {{{type|$TYPE}}} bugs is active to some degree at all times. It is particularly visible, however, after the [[Milestone freezes]] for each milestone of a release (Alpha, Beta, Final). At the ''Milestone freeze'' (''Alpha freeze'', ''Beta freeze'' etc), the stable [[Repositories#fedora|''fedora'']] package repository is frozen, meaning packages can no longer move from the [[Repositories#updates-testing|updates-testing]] repository to the ''stable'' repository from which the [[QA:SOP_compose_request|test compose and release candidate]] builds are created.
+
The process of nominating and reviewing {{{type|$TYPE}}} bugs is active to some degree at all times. It is particularly visible, however, after the [[Milestone freezes]] for each milestone of a release (Alpha, Beta, Final). At the ''Milestone freeze'' (''Alpha freeze'', ''Beta freeze'' etc), the stable [[Repositories#fedora|''fedora'']] package repository is frozen, meaning packages can no longer move from the [[Repositories#updates-testing|updates-testing]] repository to the ''stable'' repository from which the [[QA:SOP_compose_request|'candidate']] composes are created.
  
 
If a Fedora milestone release is currently in a milestone freeze (you can check [[Releases/{{FedoraVersionNumber|next}}/Schedule|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 ''milestone freeze'', 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.
 
If a Fedora milestone release is currently in a milestone freeze (you can check [[Releases/{{FedoraVersionNumber|next}}/Schedule|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 ''milestone freeze'', 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.

Revision as of 22:25, 25 April 2016

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 Milestone freezes for each milestone of a release (Alpha, Beta, Final). At the Milestone freeze (Alpha freeze, Beta freeze etc), the stable fedora package repository is frozen, meaning packages can no longer move from the updates-testing repository to the stable repository from which the 'candidate' composes are created.

If a Fedora milestone release is currently in a milestone freeze (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 milestone freeze, 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 milestone freeze is lifted and builds can be marked as 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.