This is a tracking bug for Change: Unified Kernel Support Phase 1 For more details, see: https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_1 Add support for unified kernels images to Fedora. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Today we reached the Code Complete (Testable) milestone on the F38 schedule: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html At this time, all F38 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F39, please NEEDINFO me. Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.
Current state of affairs: * kernel-ark update just landed (https://gitlab.com/cki-project/kernel-ark/-/commit/2ae6999edba357f38ae7a403c2a2571bddcc6aaa) - I can't see the update in rawhide compose yet, but it should show up RSN. * grub changes are not yet in, so right now it only works with non-default setups, i.e. (a) Using systemd-boot, or (b) Configure the UEFI firmware to boot the UKI directly, without boot loader. [ Cc'ing Oliver who works on grub2 ] * Made progress on systemd changes (kernel-install scripts). Some the changes made it into v253 and are in rawhide already, some changes are scheduled to me merged after the v253 release and will most likely miss F38. kernel rpms use some (temporary) quirks because of that. * Made progress on installer support. - blivet changes are in (see bug 1075288). - anaconda changes TBD (see bug 2160074). [ Cc'ing Daniel ] So, unified kernel images itself are made it but the surrounding support bits are not (yet) where we want them to be. Not sure whenever that is enough to qualify for MODIFIED or whenever we better defer to F39.
> Not sure whenever that is enough to qualify for MODIFIED or whenever we better defer to F39. For the scope of this Change, I think only working with a non-default setup is fine, but I'll leave that to FESCo to decide.
Today we reached the Code Complete (100% complete) milestone on the F38 schedule: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html At this time, all F38 Changes should be 100% complete. You can indicate this by setting this tracker to the ON_QA status. If you need to defer this Change to F39 please NEEDINFO me. Note that we are entering the Beta freeze. Additional package changes to complete this Change will need an approved blocker or freeze exception. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for more information. Changes that have not reached the ON_QA status will be given to FESCo for evaluation of contingency plans.
We have now reached the Final freeze. FESCo did not decide to defer this previously. Can it be considered complete enough for Changes tracking purposes? (Note that that doesn't mean more work can't happen post-release. It's basically a question of "can we include this in marketing materials etc" at this point)
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days