Fedora Ops Architect Report

Originally published at: Fedora Ops Architect Report – Fedora Community Blog

Hello Fedora folks! Can you believe this is the end of September already? Blink and you might have missed the month! I’ve rounded up a few things that are happening around the project that may be of interest, so read on for more.

Fedora Linux 41 Development

We are right in the thick of release season, and if you have a change landing in F41, now is the best time to make sure everything is working as planned. If you get a notification that you are tagged in a release notes ticket, please do verify if your change needs a release note or not, and if so please write one.

We enter Final Freeze on October 15th, and help with identifying and resolving blocker bugs would be hugely appreciated. You can propose and help out through our Blocker Bugs app.

A reminder that Fedora Linux 39 goes EOL on November 19th, and for other key milestones, please reer to the Fedora Linux 41 schedule.

Fedora Linux 42 Development

Fedora Linux 42

A.K.A, the answer to life, the universe and everything. Below are some changes currently in review by our community, and some that are now with FESCo for voting.

Our Change Set page has a list of the currently accepted changes, and below are a list of some key dates:

  • 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 our Fedora Linux 43 and Fedora Linux 44 are now live also.

Hot Topics

The Fedora Council has proposed an update to our policy governing the promotion to Edition status. You can read more about this change on the blog post and or on discussions.fpo.

There is some great things happening in the boot-c initiative right now! A report on the activity was published last week, and you can read about the progress on the discussions.fpo post.

Our git forge investigation is still in progress with instances of both Forgejo and GitLab available for testing purposes. Please read Akashdeep Dhar’s post about how to get involved with the testing and where to go for help when doing so. We are aiming for the end of October to complete the investigation of the user stories we received and for a report to be submitted to the Council for review, deliberation and decision. The report will also be made public too.

2 Likes