Fedora Linux 36 development schedule

Originally published at: Fedora Linux 36 development schedule – Fedora Community Blog

Fedora Linux 35 branches from Rawhide today. While there’s still a lot of work before the Fedora Linux 35 release in October, this marks the beginning of the Fedora Linux 36 development cycle. Work you do in Rawhide now will be in the Fedora Linux 36 release in April.

With that in mind, here are some important milestones:

  • Wed 2021-12-22: Proposal submission deadline (Changes requiring infrastructure changes)
  • Tue 2021-12-28: Proposal submission deadline (Changes requiring mass rebuild & System-Wide Changes)
  • Tue 2022-01-18: Proposal submission deadline (Self Contained Changes)
  • Tue 2022-02-08:
    • Change Checkpoint: Completion deadline (testable)
    • Branch Fedora 36 from Rawhide
  • Tue 2022-02-22:
    • Change Checkpoint: 100% Code Complete Deadline
    • Beta Freeze begins
  • Tue 2022-03-15: Beta release (early target date)
  • Tue 2022-03-22: Beta release (target date #1)
  • Tue 2022-04-05: Final Freeze begins
  • Tue 2022-04-19: Final release (early target date)
  • Tue 2022-04-26: Final release (target date #1)

Of course, the schedule is subject to change. The schedules published to fedorapeople.org are always the most up-to-date.

As always, if your team needs additions, removals, or changes, you can file a ticket in the Pagure repo. Also, I’m still working on the F37–42 schedules, so please file any changes your team would like reflected in those schedules.

1 Like

Just looking at this schedule and the draft gnome schedule at FortyTwo - GNOME Wiki! and Gnome 42 rc will happen during the Fedora 36 beta freeze period.

I think that is a regular occurrence now, but it is always a shame that the rc is not scheduled to make it into the beta as that would be a good place for testing.

However aligning things better would require a 2 week delay, which isnt short.

Then again, technically Fedora isnt code complete without this either.

1 Like

Yeah, the timing means we often put a GNOME rc into the beta with a Freeze Exception.