Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2049849 Information from BlockerBugs App: <img alt="2049849" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2049849" />
Commented but haven't voted yet: coremodule, chrismurphy
The votes have been last counted at 2022-03-27 21:23 UTC and the last processed comment was #comment-787821
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
AGREED AcceptedFinalBlocker
Discussed during the 2022-02-07 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"The installer must be able to install into free space alongside an existing clean Windows installation and install a bootloader which can boot into both Windows and Fedora" in the case of Windows being installed with Bitlocker enabled (as is increasingly common).
We recognize this is technically difficult to fix and may change or defer.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-07/f36-blocker-review.2022-02-07-17.00.txt
The following votes have been closed:
Upstream GRUB discussion continues. I expect there won't be a resolution this cycle. I think we could punt this to Fedora 37, and focus on ways we could determine what configurations are affected and how many users are affected.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.