Bug 1396705 (F27FinalFreezeException) - Fedora 27 Final freeze exception bug tracker
Summary: Fedora 27 Final freeze exception bug tracker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: F27FinalFreezeException
Product: Fedora
Classification: Fedora
Component: distribution
Version: 27
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: 1446934 1471401 1476603 1478089 1478141 1479932 1482692 1487787 1489942 1490632 1490668 1491006 1495509 1496327 1496489 1497458 1497854 1499170 1499260 1499683 1500834 1502827 1502915 1503843 1505090 1505997 1506802 1506894 1507296 1507676 1507931 1508706
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-19 01:36 UTC by Adam Williamson
Modified: 2017-11-23 22:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-23 22:16:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2016-11-19 01:36:41 UTC
Fedora 27 Final freeze exception bug tracker: http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

To propose a bug as a freeze exception bug for the Fedora 27 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 F27FinalBlocker. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process for the blocker process.

Comment 1 Adam Williamson 2017-11-23 22:16:09 UTC
Fedora 27 was released. Bug closed per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

Comment 2 Adam Williamson 2017-11-23 22:28:05 UTC
Fedora 27 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.