Ubuntu Jammy Jellyfish Release Schedule
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 |
October 2021 |
|
|
1 |
October 21 |
|
2 |
October 28 |
php8.1 |
November 2021 |
|
|
3 |
November 04 |
OpenSSL3 |
4 |
November 11 |
|
5 |
November 18 |
Ruby 3.0 |
6 |
November 25 |
|
December 2021 |
|
|
7 |
December 02 |
systemd v249 |
8 |
December 09 |
DPDK 21.11 |
9 |
December 16 |
binutils 2.38 |
10 |
December 23 |
|
11 |
December 30 |
|
January 2022 |
|
|
12 |
January 06 |
|
13 |
January 13 |
Python 3.10 |
14 |
January 20 |
OpenLDAP 2.6 (tentative; depends on upstream release schedule) – Cancelled, see this comment |
15 |
January 27 |
|
February 2022 |
|
|
16 |
February 03 |
Glibc 2.35 |
17 |
February 10 |
|
18 |
February 17 |
GNOME 42 Beta, Golang 1.18 |
19 |
February 24 |
|
March 2022 |
|
|
20 |
March 03 |
|
21 |
March 10 |
|
22 |
March 17 |
LLVM 14 |
23 |
March 24 |
GNOME 42.0 |
24 |
March 31 |
Openstack Yoga |
April 2022 |
|
|
25 |
April 07 |
|
26 |
April 14 |
|
27 |
April 21 |
|
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 |
Feature Freeze |
|
n/a |
n/a |
|
UI Freeze |
|
n/a |
n/a |
|
Doc String Freeze |
|
n/a |
n/a |
|
22.04 Beta |
March 31 2022 |
@sil2100 |
|
@sil2100 |
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.
9 Likes