Ubuntu Kinetic Kudu Release Schedule
|Week||Date (Thursday)||22.10 events|
|1||April 28||Toolchain Uploaded|
|10||June 30||Ubuntu Testing Week (optional)|
|18||August 25||Feature Freeze, Debian Import Freeze|
|19||September 01||Ubuntu Testing Week (optional)|
|21||September 15||User Interface Freeze|
|22||September 22||Documentation String Freeze, Kernel Feature Freeze|
|23||September 26 (Monday)||Beta Freeze, Hardware Enablement Freeze|
|⠀||September 29||Beta (mandatory)|
|24||October 06||Kernel Freeze, Non Language Pack Translation Deadline|
|25||October 13||Final Freeze, Release Candidate, Language Pack Translation Deadline|
|26||October 20||Final Release|
Planned and potentially disruptive archive-wide activities
If you’re planning a change that might have a disruptive effect on the archive - e.g. transitions or switches of important defaults (such as compiler versions) - list it here.
|Week||Date (Thursday)||Planned activity|
|7||June 09||First test rebuild (+/- 1 week)|
|8||June 16||binutils 2.39|
|10||June 30||systemd v251|
|14||July 28||glibc 2.36|
|15||August 04||GCC 12 as default|
|16||August 11||GNOME 43 Beta|
|19||September 01||LLVM 15|
|20||September 08||Second test rebuild (+/- 1 week)|
|22||September 22||GNOME 43.0|
Ubuntu K Release Task Signup Sheet
This signup sheet is to be used for planning release milestone tasks.
The Alpha and Beta 1 milestones have been replaced with Testing Weeks, which are organized ad hoc at this point.
|Milestone||Date||Image (Nusakan) Engineering||Checklist Tracking||Announcement Email|
|UI Freeze||September 15 2022||n/a||n/a||Łukasz ‘sil2100’ Zemczak|
|Doc String Freeze||n/a||n/a|
|22.10 Beta||September 29 2022||Łukasz ‘sil2100’ Zemczak, Brian Murray||Graham Inggs|
|22.10 Release||October 20 2022|
When the archive is frozen, all members of the release team are expected to participate in bug fix reviews.
After Feature Freeze, all members of the release team are expected to participate in Feature Freeze Exception reviews in their particular area of expertise.
After Final Beta, all members of the release team are expected to participate in Bug fix reviews in their particular area of expertise.