Schedules/release service/20.04 Release Schedule: Difference between revisions
(tweak) |
(20.04.1 delayed by one day) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team. | All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team. | ||
Line 35: | Line 27: | ||
Minor release is tagged and made available to the packagers. | Minor release is tagged and made available to the packagers. | ||
=== | === Friday, May 15 2020: 20.04.1 release === | ||
Minor release is released to the public. | Minor release is released to the public. | ||
=== Monday, June | === Monday, June 8, 2020: 20.04.2 tagging === | ||
Minor release is tagged and made available to the packagers. | Minor release is tagged and made available to the packagers. | ||
=== Thursday, June | === Thursday, June 11, 2020: 20.04.2 release === | ||
Minor release is released to the public. | Minor release is released to the public. | ||
Latest revision as of 21:02, 12 May 2020
All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team.
You can also add phabricator's calendar events_release.ics as remote calendar to korganizer so you always have the release schedule near you.
Thursday, March 12, 2020: 20.04 Dependency Freeze
From this moment on it is not allowed to add new dependencies or bump dependencies versions. It is possible to get an exception for this. Post the patch to phabricator and add the release-team as reviewer. We will check if the dependency is needed and is available on all platforms.
In other words: If you have a feature that requires a new dependency or a version of a dependency that is higher than currently checked for in the build system, you need to have committed this change before this date.
Thursday, March 19 2020: 20.04 Freeze and Beta (20.03.80) tag & release
- Only bugfixes from this point on.
- User visible strings are frozen: neither string changes nor new strings are allowed in the stable branch. Exceptions need approval from [email protected].
- If a string was already part of the software but was not correctly exposed for translation, it can be added to the stable branch.
- Documentation (handbook) is frozen: exceptions need approval from [email protected].
Beta is tagged (tag name is v20.03.80). As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released.
Thursday, April 2, 2020: 20.04 RC (20.03.90) Tagging and Release
Release Candidate is tagged (tag name is v20.03.90). As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released
Thursday, April 16, 2020: 20.04 Tagging
The branch is frozen for final release tagging (tag name is v20.04.0). Only urgent fixes, such as those fixing compilation errors, should be committed.
Thursday, April 23, 2020: 20.04 Release
Final release is released for general consumption.
Monday, May 11, 2020: 20.04.1 tagging
Minor release is tagged and made available to the packagers.
Friday, May 15 2020: 20.04.1 release
Minor release is released to the public.
Monday, June 8, 2020: 20.04.2 tagging
Minor release is tagged and made available to the packagers.
Thursday, June 11, 2020: 20.04.2 release
Minor release is released to the public.
Monday, July 6, 2020: 20.04.3 tagging
Minor release is tagged and made available to the packagers.
Thursday, July 9, 2020: 20.04.3 release
Minor release is released to the public.