Bug 1349189 (F26FinalFreezeException) - Fedora 26 Final freeze exception bug tracker
Summary: Fedora 26 Final freeze exception bug tracker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: F26FinalFreezeException
Product: Fedora
Classification: Fedora
Component: distribution
Version: 26
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Václav Pavlín
QA Contact: Fedora Extras Quality Assurance
URL: https://fedoraproject.org/wiki/QA:SOP...
Whiteboard:
Depends On: 1404918 1416961 1416962 1435623 1439492 1446782 1449643 1451071 1451914 1463297 1464555 1465208 1465278 1465281 1465283 1465284 1465285 1465286 1465287 1465288 1465440 1465610 1465662 1465663 1466267 1466356 1466689 1466907 1466957 1467355 1467383
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-22 22:08 UTC by Adam Williamson
Modified: 2017-07-24 23:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-10 16:13:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2016-06-22 22:08:01 UTC
Fedora 26 Final freeze exception bug tracker: http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

To propose a bug as a freeze exception bug for the Fedora 26 Final release, mark it as blocking this bug, or use the webapp: https://qa.fedoraproject.org/blockerbugs/propose_bug . It will be reviewed according to https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process .

If you think the bug is sufficiently serious to block the Final release, instead mark it as blocking the bug F26FinalBlocker. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process for the blocker process.

Comment 1 Adam Williamson 2017-07-10 16:13:31 UTC
Fedora 26 was released. Bug closed per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

Comment 2 Adam Williamson 2017-07-10 16:19:50 UTC
Fedora 26 was released. Bug closed per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers


Note You need to log in before you can comment on or make changes to this bug.