Schedules/KDE4/4.9 Release Schedule

KDE SC 4.9 is a feature release for KDE SC 4. All dates given here are subject to revision, but we will try our best to stick to them if possible. The KDE Release Team is acting as the coordinator for this release.

All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team.

(the below schedule is generated based on software. Don't edit below, but edit the software and regenerate the schedule.)

You can also add http://www.kde.org/releaseschedule.ics as remote calendar to korganizer so you always have the release schedule near you.

KDE SC 4.9

Thursday, May 3, 2012: KDE SC 4.9 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, May 10, 2012: KDE SC 4.9 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, May 17, 2012: KDE SC 4.9 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, May 17, 2012: KDE SC 4.9 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, May 17, 2012: KDE SC 4.9 Hard Feature Freeze

Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed.

Thursday, May 24, 2012: KDE SC 4.9 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, May 30, 2012: KDE SC 4.9 Beta 1 Release

The beta becomes available for general consumption.

Thursday, June 7, 2012: KDE SC 4.9 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, June 13, 2012: KDE SC 4.9 Beta 2 Release

The beta becomes available for general consumption.

Monday, June 25, 2012: KDE SC 4.9 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, June 25, 2012: KDE SC 4.9 Hard API Freeze

To allow the bindings people to have proper time to do there 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, June 25, 2012: KDE SC 4.9 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, June 25, 2012: KDE SC 4.9 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, June 25, 2012: KDE SC 4.9 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, June 26, 2012: KDE SC 4.9 Release Candidate 1 Tagging

Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.

Wednesday, June 27, 2012: KDE SC 4.9 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.

Monday, July 9, 2012: KDE SC 4.9 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.

Tuesday, July 10, 2012: KDE SC 4.9 Release Candidate 2 Tagging

Branch is frozen for release candidate tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.

Wednesday, July 11, 2012: KDE SC 4.9 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, July 25, 2012: KDE SC 4.9 Final Tag

The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.