Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1396704 (F27FinalBlocker) - Fedora 27 Final blocker bug tracker
Summary: Fedora 27 Final blocker bug tracker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: F27FinalBlocker
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: 1193590 1451377 1451379 1451381 1451385 1456293 1459081 1464843 1468239 1475565 1476603 1477916 1478633 1479932 1482692 1483644 1484575 1484916 1485021 1485050 1485055 1490223 1490351 1490832 1491316 1491808 1491809 1493204 1494061 1494108 1495635 1497691 1498091 1498207 1499514 1500734 1501762 1503496 1504059 1505906 1506050 1506052 1508794 1508899
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-19 01:36 UTC by Adam Williamson
Modified: 2018-11-27 19:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-27 19:34:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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

To propose a bug as blocking 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_blocker_bug_process . If you can, please specify the release criterion that the bug violates. See https://fedoraproject.org/wiki/Fedora_Release_Criteria for details on the release criteria.

If the bug is not serious enough to block release but you believe it merits being fixed during a milestone freeze (see https://fedoraproject.org/wiki/Milestone_freezes ), you can propose it as a 'freeze exception' instead. To do this, mark it as blocking the bug F27FinalFreezeException . See https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for the freeze exception process.
Comment 1 Adam Williamson 2017-11-23 22:16:15 UTC 
Fedora 27 was released. Bug closed per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers
Comment 2 Adam Williamson 2017-11-23 22:28:10 UTC 
Fedora 27 was released. Bug closed per https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers
Comment 3 Adam Williamson 2017-11-30 00:50:54 UTC 
Re-opening for the purpose of the delayed Fedora 27 Server release we're going to discuss at a special go/no-go meeting tomorrow.
Comment 4 Ben Cotton 2018-11-27 16:30:30 UTC 
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Note You need to log in before you can comment on or make changes to this bug.