Schedules/release service/19.12 Release Schedule: Difference between revisions
(Initial proposal (based on Applications 18.12)) |
No edit summary |
||
| (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 12: | Line 5: | ||
You can also add [https://phabricator.kde.org/calendar/export/ics/en57n5ovb3k6vg4mtqbx/events_release.ics phabricator's calendar events_release.ics] as remote calendar to korganizer so you always have the release schedule near you. | You can also add [https://phabricator.kde.org/calendar/export/ics/en57n5ovb3k6vg4mtqbx/events_release.ics phabricator's calendar events_release.ics] as remote calendar to korganizer so you always have the release schedule near you. | ||
=== Thursday, November 7, 2019: | === Thursday, November 7, 2019: release service 19.12 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. | 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. | 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, November 14, 2019: | === Thursday, November 14, 2019: release service 19.12 Freeze and Beta (19.11.80) tag & release === | ||
Only bugfixes from this point on. Bugfixes needing user visible text changes need approval from [email protected] | Only bugfixes from this point on. Bugfixes needing user visible text changes need approval from [email protected] | ||
Beta is tagged (tag name is v19.11.80). As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released | Beta is tagged (tag name is v19.11.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, November 28, 2019: | === Thursday, November 28, 2019: release service 19.12 RC (19.11.90) Tagging and Release === | ||
Release Candidate is tagged (tag name is v19.11.90). As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released | Release Candidate is tagged (tag name is v19.11.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, December 5, 2019: | === Thursday, December 5, 2019: release service 19.12 Tagging === | ||
The branch is frozen for final release tagging (tag name is v19.12.0). Only urgent fixes, such as those fixing compilation errors, should be committed. | The branch is frozen for final release tagging (tag name is v19.12.0). Only urgent fixes, such as those fixing compilation errors, should be committed. | ||
=== Thursday, December 12, 2019: | === Thursday, December 12, 2019: release service 19.12 Release === | ||
Final release is released for general consumption. | Final release is released for general consumption. | ||
=== Monday, January 6, 2020: | === Monday, January 6, 2020: release service 19.12.1 tagging === | ||
Minor release is tagged and made available to the packagers. | Minor release is tagged and made available to the packagers. | ||
=== Thursday, January 9, 2020: | === Thursday, January 9, 2020: release service 19.12.1 release === | ||
Minor release is released to the public. | Minor release is released to the public. | ||
=== Monday, February 3, 2020: | === Monday, February 3, 2020: release service 19.12.2 tagging === | ||
Minor release is tagged and made available to the packagers. | Minor release is tagged and made available to the packagers. | ||
=== Thursday, February 6, 2020: | === Thursday, February 6, 2020: release service 19.12.2 release === | ||
Minor release is released to the public. | Minor release is released to the public. | ||
=== Monday March 2, 2020: | === Monday March 2, 2020: release service 19.12.3 tagging === | ||
Minor release is tagged and made available to the packagers. | Minor release is tagged and made available to the packagers. | ||
=== Thursday, March 5, 2020: | === Thursday, March 5, 2020: release service 19.12.3 release === | ||
Minor release is released to the public. | Minor release is released to the public. | ||
Latest revision as of 12:07, 26 November 2019
All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team.
Applications in 19.12 can only be based on KDE Frameworks 5. Please make sure all your dependencies or people that depend on you are aware of your decision to not cause problems.
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, November 7, 2019: release service 19.12 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, November 14, 2019: release service 19.12 Freeze and Beta (19.11.80) tag & release
Only bugfixes from this point on. Bugfixes needing user visible text changes need approval from [email protected]
Beta is tagged (tag name is v19.11.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, November 28, 2019: release service 19.12 RC (19.11.90) Tagging and Release
Release Candidate is tagged (tag name is v19.11.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, December 5, 2019: release service 19.12 Tagging
The branch is frozen for final release tagging (tag name is v19.12.0). Only urgent fixes, such as those fixing compilation errors, should be committed.
Thursday, December 12, 2019: release service 19.12 Release
Final release is released for general consumption.
Monday, January 6, 2020: release service 19.12.1 tagging
Minor release is tagged and made available to the packagers.
Thursday, January 9, 2020: release service 19.12.1 release
Minor release is released to the public.
Monday, February 3, 2020: release service 19.12.2 tagging
Minor release is tagged and made available to the packagers.
Thursday, February 6, 2020: release service 19.12.2 release
Minor release is released to the public.
Monday March 2, 2020: release service 19.12.3 tagging
Minor release is tagged and made available to the packagers.
Thursday, March 5, 2020: release service 19.12.3 release
Minor release is released to the public.