-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F32 rebase tracker for changes discussion #372
Comments
We discussed this in the meeting today. Some interesting things from the F32 Changeset:
|
In the meeting on 04/29 we proposed this schedule for the switch to f32 in our other streams:
which translates to:
|
Moving testing-devel to f32: coreos/fedora-coreos-config#394 |
hold that for now as we might need to spin a new testing: #479 (comment) |
Considering #481 we have pushed out the schedule a bit to let the fix propagate. Here is the newly proposed schedule:
|
Tested OKD-on-FCOS, booting from stable 31.20200420.3.0 and updating to machine-os-content based on |
We discussed this in the community meeting today. We're still planning to go ahead with the dates suggested in #372 (comment). |
updates:
|
Fedora CoreOS |
The tentative schedule for F32 is:
While we aren't beholden to that schedule and will likely switchover to F32 some time after the official release date we should have a discussion about what changes we need to make as part of the rebase and also enumerate and discuss the changes that are being made to Fedora for F32 to see if they affect us and we should react to them in any way.
Currently the changes to Fedora are enumerated and linked from https://fedoraproject.org/wiki/Releases/32/ChangeSet. We should evaluate that change set to see if there is anything we need to do regarding those changes.
The following section will be updated/edited during investigation:
Noteworthy Fedora Changes from FCOS context
Changes we are considering making to FCOS
Should we switch to cgroups v2 for F32: F32: should we switch to cgroups v2 #373The text was updated successfully, but these errors were encountered: