Fedora Operations Report – Fedora Community Blog
Happy October folks! In this post you’ll find some information on our F41 and F42 releases, plus a few lines on a couple of topics happening around the project lately. Read on to find out more!
Fedora Linux 41
We are nearing the end of the Fedora Linux 41 release cycle! Our Go/No-Go meeting will happen next Thursday 17th October @ 1700 UTC. To join, you can find the information on the fedocal calendar entry.
There are still some proposed blockers for F41 too, so if you can help resolve some of these bus, please check out our blocker bugs app, or for a more condensed summary, please read out blocker bug report email.
Fedora Linux 42
Fedora Linux 42 is currently in development, and for the most recent set of changes planned in this rel;ease, please refer to our change set page. Our release schedule is also live, and a reminder of some key dates are below:
- December 18th – Changes requiring infrastructure changes
- December 24th – Changes requiring mass rebuild
- December 24th – System Wide changes
- January 14th – Self Contained changes
- February 4th – Changes need to be Testable
- February 4th – Branching
- February 18th – Changes need to be Complete
The changes that are currently in our community feedback period are :
Hot Topics
For all the latest on boot-c, check out the bootc post on discourse!
Our Git Forge evaluation is taking shape. We have an instance of both Forgejo and GitLab CE available to try out in the Communshift app. Details of how to get access can be found on this discussion thread, and we are encouraging folks to try out each instance and report their feedback, preferably against the user stories collected, on this discussion thread. Directly linked to the git forge evaluation, following Wednesdays council meeting, we have decided to extend the report comparing both Forgejo and GitLab CE to be due by December 5th to allow our QA team, and other teams impacted by the F41 release, time to properly validate their use cases against each forge option. This means the council decision may not happen until early January, but we do hope to proceed with a decision as early as possible so the CPE team can help create a migration plan for affected workflows that can be shared and agreed to in good time to allow minimal disruption to the project as a whole as possible.
There is still time to share feedback on the proposal to amend the Editions Promotion policy. You can read the current policy, and what the council would like to change, in this discussion thread.
FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February! The call for devrooms has passed, but the call for stands is still open until November 7th.
A new episode of The Fedora Podcast is now available! Details of episode 38 and how to listen can be found on the discussion post and by visiting the audio post for the latest, and all episodes.