Schedules/KDE4/4.10 Release Schedule: Difference between revisions
(add 4.10.5) |
m (13 revisions imported: Import Schedules subpages from techbase) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 59: | Line 59: | ||
The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately. | The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately. | ||
=== Wednesday, January 2, | === Wednesday, January 2, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 2 === | ||
During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer. | During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer. | ||
| Line 65: | Line 65: | ||
Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. | Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. | ||
=== | === Friday, January 4, 2013: KDE SC 4.10 Release Candidate 2 Release === | ||
The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately. | The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately. | ||
=== Wednesday, January 16, 2013: KDE SC 4.10 Final Tag === | === Wednesday, January 16, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 3 === | ||
During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer. | |||
=== Thursday, January 17, 2013: KDE SC 4.10 Release Candidate 3 Tagging === | |||
Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. | |||
=== Friday, January 18, 2013: KDE SC 4.10 Release Candidate 3 Release === | |||
The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately. | |||
=== Wednesday, January 30, 2013: KDE SC 4.10 Final Tag === | |||
The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. | The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. | ||
=== Wednesday, | === Wednesday, February 6, 2013: KDE SC 4.10 Release === | ||
Final release is released for general consumption. | Final release is released for general consumption. | ||
Latest revision as of 18:52, 8 March 2016
Add your features to Schedules/KDE4/4.10 Feature Plan
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 http://www.kde.org/releaseschedule.ics as remote calendar to korganizer so you always have the release schedule near you.
Thursday, October 25, 2012: KDE SC 4.10 Soft Feature Freeze
Trunk is frozen for feature commits that are not listed in the planned feature document. Only bugfixes and the code implementing the listed features are to be committed after this date. The feature list also closes today.
Features not already finished or not listed on the planned features page will have to wait until the next KDE SC release.
Thursday, November 1, 2012: KDE SC 4.10 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 reviewboard 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 8, 2012: KDE SC 4.10 Soft Message Freeze
All translated messages (GUI strings) are frozen on this date. Only previously untranslated strings or clear errors in strings can be fixed. No major new strings changes should be done. You cannot add new strings, if you really need one ask kde-i18n-doc for an exception. It is ok to remove strings. Exception: Artwork (try to keep the number of new strings low anyways). Exception: Typo fixes can be fixed until the Hard Message Freeze, but you have to mail kde-i18n-doc saying you made a typo fix change.
Thursday, November 8, 2012: KDE SC 4.10 Soft API Freeze
To allow the bindings people to have proper time to do their work in preparation to the final release, the API should now be mostly fixed. Changing API is allowed, but commits have to be cc'ed to the kde-bindings mailinglist. This is including older APIs and newly introduced libraries/APIs.
Thursday, November 8, 2012: KDE SC 4.10 Hard Feature Freeze
Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed.
Thursday, November 15, 2012: KDE SC 4.10 Beta 1 Tagging
Trunk is frozen for beta release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated.
Wednesday, November 21, 2012: KDE SC 4.10 Beta 1 Release
The beta becomes available for general consumption.
Thursday, November 29, 2012: KDE SC 4.10 Beta 2 Tagging
Trunk is frozen for beta release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated.
Wednesday, December 5, 2012: KDE SC 4.10 Beta 2 Release
The beta becomes available for general consumption.
Monday, December 17, 2012: KDE SC 4.10 Tagging Freeze for Release Candidate 1
During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer.
Monday, December 17, 2012: KDE SC 4.10 Hard API Freeze
To allow the bindings people to have proper time to do their work in preparation to the final release, the API is now frozen. No more changes to APIs or header files (except docs) after this date, including older APIs and newly introduced libraries/APIs.
Monday, December 17, 2012: KDE SC 4.10 Hard Message Freeze
Up to now you were able to do typo changes, but you had to mail kde-i18n-doc saying you made a typo fix change. From this moment on you need to contact kde-i18n-doc for every single string change, if noone objects in 5 days you can commit the change.
Monday, December 17, 2012: KDE SC 4.10 Artwork and Bindings Freeze
All artwork is frozen on this date. No new artwork should be added. Existing artwork can continue to be tweaked and fixed.
No new additions to the language bindings, except optional bindings as permitting by the kde-bindings team.
Monday, December 17, 2012: KDE SC 4.10 Documentation Freeze
No more changes to documentation or handbooks after this date. For typos, spelling and simple grammar changes you have to mail kde-i18n-doc for approval.
Tuesday, December 18, 2012: KDE SC 4.10 Release Candidate 1 Tagging
Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.
Wednesday, December 19, 2012: KDE SC 4.10 Release Candidate 1 Release
The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately.
Wednesday, January 2, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 2
During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer.
Thursday, January 3, 2013: KDE SC 4.10 Release Candidate 2 Tagging
Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.
Friday, January 4, 2013: KDE SC 4.10 Release Candidate 2 Release
The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately.
Wednesday, January 16, 2013: KDE SC 4.10 Tagging Freeze for Release Candidate 3
During tagging freeze only compilation fixes for all platforms are allowed to be committed. Everything else (even showstopper fixes) *have* to be run through reviewboard, with the release-team and the affected maintainers as reviewer.
Thursday, January 17, 2013: KDE SC 4.10 Release Candidate 3 Tagging
Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.
Friday, January 18, 2013: KDE SC 4.10 Release Candidate 3 Release
The release candidate is tagged from the branch. Only urgent fixes, such as those fixing compilation errors, should be committed.As soon as the RC has been confirmed to build it will be released immediately.
Wednesday, January 30, 2013: KDE SC 4.10 Final Tag
The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.
Wednesday, February 6, 2013: KDE SC 4.10 Release
Final release is released for general consumption.
Thursday, February 28, 2013: KDE SC 4.10.1 tagging
A KDE SC minor release is tagged and made available to the packagers.
Tuesday, March 5, 2013: KDE SC 4.10.1 release
A KDE SC minor release is released to the public.
Thursday, March 28, 2013: KDE SC 4.10.2 tagging
A KDE SC minor release is tagged and made available to the packagers.
Tuesday, April 2, 2013: KDE SC 4.10.2 release
A KDE SC minor release is released to the public.
Thursday, May 2, 2013: KDE SC 4.10.3 tagging
A KDE SC minor release is tagged and made available to the packagers.
Tuesday, May 7, 2013: KDE SC 4.10.3 release
A KDE SC minor release is released to the public.
Thursday, May 30, 2013: KDE SC 4.10.4 tagging
A KDE SC minor release is tagged and made available to the packagers.
Tuesday, June 4, 2013: KDE SC 4.10.4 release
A KDE SC minor release is released to the public.
Thursday, June 27, 2013: KDE SC 4.10.5 tagging
A KDE SC minor release is tagged and made available to the packagers.
Tuesday, July 2 2013: KDE SC 4.10.5 release
A KDE SC minor release is released to the public.