Difference between revisions of "Schedules/KDE4/4.12 Release Schedule"

Jump to: navigation, search
(first stab)
 
(Wednesday, October 30, 2013: KDE 4.12 Message Freeze)
Line 11: Line 11:
  
 
=== Wednesday, October 30, 2013: KDE 4.12 Message Freeze ===
 
=== Wednesday, October 30, 2013: KDE 4.12 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.
+
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.
  
 
=== Wednesday, October 30, 2013: KDE 4.12 API Freeze ===
 
=== Wednesday, October 30, 2013: KDE 4.12 API Freeze ===

Revision as of 18:44, 3 August 2013

THIS IS NOT OFFICIAL YET THIS IS NOT OFFICIAL YET THIS IS NOT OFFICIAL YET THIS IS NOT OFFICIAL YET

Add your features to Schedules/KDE4/4.12 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.

Contents

Wednesday, October 30, 2013: KDE 4.12 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.

Wednesday, October 30, 2013: KDE 4.12 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.

Wednesday, October 30, 2013: KDE 4.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 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.

Wednesday, October 30, 2013: KDE 4.12 Feature Freeze

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

Wednesday, October 30, 2013: KDE 4.12 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.

Wednesday, October 30, 2013: KDE 4.12 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.

Wednesday, November 6, 2013: KDE 4.12 Beta 1 Tagging and Release

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. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released

Wednesday, November 20, 2013: KDE 4.12 Release Candidate 1 Tagging and 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 tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released

Wednesday, December 4, 2013: KDE 4.12 Final Tag

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

Wednesday, December 11, 2013: KDE 4.12 Release

Final release is released for general consumption.

Thursday, January 9, 2014: KDE 4.12.1 tagging

A KDE minor release is tagged and made available to the packagers.

Tuesday, January 14 2014: KDE 4.12.1 release

A KDE minor release is released to the public.

Thursday, January 30, 2014: KDE 4.12.2 tagging

A KDE minor release is tagged and made available to the packagers.

Tuesday, February 4, 2014: KDE 4.12.2 release

A KDE minor release is released to the public.

Thursday, February 27, 2014: KDE 4.12.3 tagging

A KDE minor release is tagged and made available to the packagers.

Tuesday, March 4, 2014: KDE 4.12.3 release

A KDE minor release is released to the public.

Thursday, March 27, 2014: KDE 4.12.4 tagging

A KDE minor release is tagged and made available to the packagers.

Tuesday, April 1, 2014: KDE 4.12.4 release

A KDE minor release is released to the public.

Thursday, May 1, 2014: KDE 4.12.5 tagging

A KDE minor release is tagged and made available to the packagers.

Tuesday, May 76 2014: KDE 4.12.5 release

A KDE minor release is released to the public.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal