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 2056661 - ship Firefox 99 in Fedora 36
Summary: ship Firefox 99 in Fedora 36
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F36FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2022-02-21 18:38 UTC by Chris Murphy
Modified: 2022-04-12 21:28 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-12 21:28:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Chris Murphy 2022-02-21 18:38:13 UTC 
Firefox 99 schedule for released on 2022-04-05

F36 final freeze 2022-04-05, final release early target 2022-04-19, and final release target, 2022-04-26
Comment 1 Fedora Blocker Bugs Application 2022-02-21 18:39:19 UTC 
Proposed as a Freeze Exception for 36-final by Fedora user chrismurphy using the blocker tracking app because:

 Due to the timing, Firefox 99 will surely not be read by final freeze, but we want it on the media.
Comment 2 Adam Williamson 2022-03-14 16:12:07 UTC 
+4 in https://pagure.io/fedora-qa/blocker-review/issue/619 , marking accepted.
Comment 3 Fedora Update System 2022-04-09 11:35:10 UTC 
FEDORA-2022-aa2081a292 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-aa2081a292
Comment 4 Fedora Update System 2022-04-11 03:36:10 UTC 
FEDORA-2022-aa2081a292 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 5 František Zatloukal 2022-04-12 21:28:38 UTC 
The issue has been fixed by an update mentioned above.
Note You need to log in before you can comment on or make changes to this bug.