The planned schedule:
| Date | Weeks from Release | Branches Affected | Events |
|---|---|---|---|
| Oct 1 | -8 Weeks | Ask ecosystems for desired changes, in “Feature Freeze” | |
| Oct 15 | -6 Weeks |
staging-next, staging
|
Restrict breaking changes to Release Critical Packages |
| Oct 29 | -4 Weeks |
staging-next, staging
|
Restrict all breaking changes: allow only non-breaking updates and Desktop Manager changes |
| Nov 4 | -3 Weeks | master |
(Day before ZHF) merge staging-next into master, prep for ZHF |
| Nov 5 | -3 Weeks | master |
Begin ZHF, Focus on minimizing regressions in PRs targeting master
|
| Nov 12 | -2 Weeks | master |
Merge first staging-next fixes into master; begin second staging-next cycle |
| Nov 12 | -2 Weeks | staging |
Unrestrict all breaking changes; new changes will not be present in master before branch-off |
| Nov 19 | -1 Weeks | master |
Merge second staging-next fix cycle |
| Nov 19 | -1 Weeks | staging-next |
Unrestrict all breaking changes; new changes will not be present in master before branch-off |
| Nov 19 | -1 Weeks |
master, release
|
Perform Branch-off, create release channels, create new beta / unstable tags |
| Nov 19 | -1 Weeks |
master, release
|
ZHF transitions to “backporting” workflow |
| Nov 19 | -1 Weeks | release |
Prepare for release, finish remaining issues |
| Nov 26 | 0 Weeks | release |
Release! |
| Nov 26 | 0 Weeks | ZHF Ends |