Fedora 22 Beta Freeze

Dennis Gilmore dennis at ausil.us
Thu Apr 2 18:49:00 UTC 2015

Hi all,

Tuesday was an important day on the Fedora 22 schedule[1], with two
significant cut-offs. 

Tuesday was the Beta freeze[2]. This means that only packages which
fix accepted blocker or freeze exception bugs[3][4] will be marked as
'stable' and included in the Beta composes. Other builds will remain
in updates-testing until the Beta release is approved, at which point
the Beta freeze is lifted and packages can move to 'stable' as usual
until the Final freeze.

Finally, Tuesday was the '100% code complete deadline' Change Checkpoint[8],
meaning that Fedora 22 Changes must now be ' New accepted changes must be code 
complete, meaning all the code required to enable to the new change is 
finished. The level of code completeness is reflected as tracker bug state 
ON_QA. The change does not have to be fully tested by this deadline'.



[1] https://fedoraproject.org/wiki/Releases/22/Schedule
[2] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[8] https://fedoraproject.org/wiki/Changes/Policy
devel-announce mailing list
devel-announce at lists.fedoraproject.org

More information about the devel mailing list