OK. Happy day, we have maybe come full circle. Here's my attempt at a summary: * systemd-boot should be evaluated for Secure Boot signing, so that it can be a viable and testable alternative bootloader to GRUB. Maybe this opens the door to changing the default bootloader in Fedora down the road. It already supports modifying the UEFI bootnext variable, followed by a reboot, when choosing Windows from its menu. Thus it could help resolve the Bitlocker issue. * Unresolved is how to address the current blocker bug Long term approaches (not Fedora 37, maybe Fedora 38 or beyond): - fix/enhance GRUB (no interest so far upstream) - use systemd-boot in lieu of GRUB Short term approaches: - Documentation: GRUB's Windows boot option may not work, how to use efibootmgr --bootnext and --bootorder Unknown time frame approaches: - A GUI utility wrapper for efibootmgr. (The seemingly simple often isn't so simple, or maybe it is. I don't know.) In the near term, we're looking at an awareness and documentation effort, while seeing how the other options shake out. And it probably doesn't significantly matter whether we change the release criterion now or also wait a bit longer. ack/nack/patch? -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
