Bug 2083910 (F38BetaBlocker) - Fedora 38 Beta blocker bug tracker
Summary: Fedora 38 Beta blocker bug tracker
Alias: F38BetaBlocker
Product: Fedora
Classification: Fedora
Component: distribution
Version: 38
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Aoife Moloney
QA Contact: Fedora Extras Quality Assurance
URL: https://fedoraproject.org/wiki/QA:SOP...
Depends On: 2110801 2139465 2146545 F38Workstationlivex86_64Oversize 2150155 F38Everythingbootx86_64Oversize F38Serverbootx86_64Oversize 2160293 2164594 2164667 2165136 2165433 2166412 2168034 2168186 2169401 2169836 2171888 2172342 2172406 2173298 2175151
TreeView+ depends on / blocked
Reported: 2022-05-11 01:41 UTC by Adam Williamson
Modified: 2023-09-03 17:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-04-18 16:59:34 UTC
Type: ---

Attachments (Terms of Use)

Description Adam Williamson 2022-05-11 01:41:58 UTC
Fedora 38 Beta blocker tracker bug: http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

To propose a bug as blocking the Fedora 38 Beta 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 F38BetaFreezeException . See https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for the freeze exception process.

Comment 1 Adam Williamson 2023-04-18 16:59:34 UTC
Fedora 38 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.