Ubuntu Jammy Jellyfish Release Schedule
|Week||Date (Thursday)||22.04 events|
|1||October 21||Toolchain Uploaded|
|10||December 23||Ubuntu Testing Week (optional)|
|16||February 03||Chinese New Year week|
|17||February 10||20.04.4 point release|
|19||February 24||Feature Freeze, Debian Import Freeze|
|20||March 03||Ubuntu Testing Week (optional)|
|22||March 17||User Interface Freeze|
|23||March 24||Documentation String Freeze, Kernel Feature Freeze|
|24||March 28 (Monday)||Beta Freeze, Hardware Enablement Freeze|
|⠀||March 31||Beta (mandatory)|
|25||April 07||Kernel Freeze, Non Language Pack Translation Deadline|
|26||April 14||Final Freeze, Release Candidate, Language Pack Translation Deadline|
|27||April 21||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|
|5||November 18||Ruby 3.0|
|7||December 02||systemd v249|
|8||December 09||DPDK 21.11|
|9||December 16||binutils 2.38|
|13||January 13||Python 3.10|
|14||January 20||OpenLDAP 2.6 (tentative; depends on upstream release schedule)|
|16||February 03||Glibc 2.35|
|18||February 17||GNOME 42 Beta, Golang 1.18|
|22||March 17||LLVM 14|
|23||March 24||GNOME 42.0|
Ubuntu Jammy Jellyfish 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|
|Doc String Freeze||n/a||n/a|
|22.04 Beta||March 31 2022|
|Final Freeze||April 14 2022|
|22.04 Release||April 21 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.