|Week||Date (Thursday)||24.04 events|
|1||October 26||Toolchain Uploaded|
|10||December 28||Ubuntu Testing Week (optional)|
|19||February 29||Feature Freeze, Debian Import Freeze|
|20||March 07||Ubuntu Testing Week (optional)|
|22||March 21||User Interface Freeze|
|23||March 28||Documentation String Freeze, Kernel Feature Freeze|
|24||April 01 (Monday)||Beta Freeze, Hardware Enablement Freeze|
|⠀||April 04||Beta (mandatory)|
|25||April 11||Kernel Freeze, Non Language Pack Translation Deadline|
|26||April 18||Final Freeze, Release Candidate, Language Pack Translation Deadline|
|27||April 25||Final Release|
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|
|2||November 02||Python 3.12 as supported Python3 version|
|9||December 21||binutils 2.42|
|11||January 04||ruby 3.2|
|12||January 11||OpenJDK-21 (default transition)|
|14||January 25||Python 3.12 as default version|
|15||February 01||glibc 2.39 in -proposed|
|17||February 15||GNOME 46 Beta|
|18||February 22||Go 1.22 as default / GCC 14 as non-default|
|22||March 21||GNOME 46.0|
|23||March 28||LLVM 18 as default|
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||utkarsh|
|24.04 Release||April 25 2024||utkarsh||utkarsh|
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.