Release Planning Schedule
The following is the template for the Workstation Working Group’s release schedule. It follows the main Fedora release schedule, with additional check-in steps.
The schedule is meant to evolve as we use it, so please update this page as necessary.
| Week | Milestone | Tasks |
|---|---|---|
1 |
Fedora development cycle begins |
|
20 |
System-wide change proposal deadline |
|
21 |
Self-contained change proposal deadline |
|
26 |
GNOME beta target date & UI freeze |
1. check that all GNOME modules have releases, 2. update packages with the GNOME beta, 3. notify QA when the GNOME beta is available in Fedora, 4. plan a test week for when the beta will be available |
27 |
Fedora branches from rawhide |
|
28 |
GNOME test week happens around now |
|
30 |
GNOME RC target date |
|
32 |
Fedora beta release |
|
33 |
GNOME stable target date |
1. update packages with the new GNOME release, 2. notify QA when the update is complete, 3. start preparing GNOME Fedora Flatpak updates |
35 |
Fedora final freeze |
Start distributing GNOME Fedora Flatpak updates (should happen 2 weeks prior to expected release date) |
37 |
Fedora stable release early target date |
Workstation publicity to be released with the new stable release: blog post, website updates, talks, etc |
Want to help? Learn how to contribute to Fedora Docs ›