Fedora Operations Report

Originally published at: Fedora Operations Report – Fedora Community Blog

I’ve stopped calling it weekly…until it’s actually weekly again. Read on for a little roundup of some of the things happening around the Project!

Fedora Linux Development

Fedora Linux 40

We hope you are enjoying this release of Fedora! To shine a light on some of the folks who helped with in the quality department of this release, make sure to read the blog post Heroes of Fedora Linux 40. If you would like to help out with any Fedora release, make sure to get involved with Test Days. We are always happy to have more testers!

Fedora Linux 41

The F41 Beta will be arriving on Tuesday 17th September! We are really looking forward to hearing how the Beta performs, we know it wont be perfect, but its important to get some feedback so we can make sure F41 Final continues the trend of ‘the best version yet!’. Keep an eye out for announcements on the Beta in Fedora Magazine and in the usual places like discourse and mailing lists, and if you find a bug, please report it on the Blocker Bugs app.

We are going in to Final Freeze on 15th October, so please make sure you have made any necessary changes or updates to your work by then, as we are still on track to release F41 Final on 5th Novmeber 2024 at this time. Keep an eye on the schedule for a more detailed view of tasks and remember that F39 will EOL on 19th November 2024.

Fedora Linux 42 & Co.

A.K.A, the answer to life, the universe and everything. But this is also a fast approaching Fedora release! Development is now underway and change requests are starting to come in. We also have some changes accepted for this release too, so for a preview of what the release should include, check out the Change Set page. Here is also quick reminder of some important dates for changes if you are hoping to land one in time for this release:

  • 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

Be sure to keep an eye on the Fedora Linux 42 release schedule, and for those who are super-duper organized (I am very jealous), the Fedora Linux 43 and Fedora Linux 44 schedules are now live too to bookmark.

Hot Topics

Git Forge Replacement

The git forge replacement effort is still going strong, with members of the ARC team working through testing these user stories against instances of GitLab and Forgejo that are deployed in the Communishift app. We are asking anyone who would like to help out with testing to get involved by requesting access to these instances and working through the use cases in the investigation tracker. The team are collecting results as comments in the discussion thread for now and are working with Fedora QA on creating Test Days in the coming weeks.

At Flock this was a general topic of conversation, and as someone who is overseeing this work on behalf of the council, I was able to meet with Tomas Hckra who is leading this investigation and work on a proposed timeline. We are aiming to adhere to this high level timeline:

  • End of October ’24 – the report comparing the two git forges against the list of user stories/requirements is finished and submitted to Fedora Council for review.
  • Around the same time – the report is also made public
  • Mid – End of November ’24 – A decision is made on what git forge the project will migrate to
  • December ’24 – A migration plan for the project is created and shared publicly
  • January ’25 – A Giant Change Proposal, likely spanning many releases, is created and proposed.
  • Sometime a little later (probably Feb/Mar ’25) – The change proposal is iterated on based on feedback if appropriate, and the Change is broken down into smaller changes targeting specific Fedora releases so the migration can be rolled out slowly and with care

I expect next year we will see the git forge evaluation well concluded, a migration plan in place, and the project will begin to migrate to the new platform. The ideal milestone is that by F44 we will successfully be using the new git forge to build and release Fedora Linux, and by F45 we will look back on pagure with great fondness for the service it did provide us all for so many years 🙂

You can get involved with and follow the conversation by using the #git-forge-future tag on discussions.fpo and joining the ARC matrix room.

1 Like