THIS IS NOT OFFICIAL AND AT THE MOMENT WORK IN PROGRESS
Add your features to Schedules/KDE4/4.13 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.
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.
To allow the bindings people to have proper time to do their work in preparation to the final release, the API should now be 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.
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.
Trunk is frozen for all feature commits. Only bug fixes are allowed.
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.
Beta is tagged from trunk. 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 from trunk. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released
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.
Beta is tagged from trunk. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released
The release candidate is tagged from the branch. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released
The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.
Final release is released for general consumption.
A KDE minor release is tagged and made available to the packagers.
A KDE minor release is released to the public.
A KDE minor release is tagged and made available to the packagers.
A KDE minor release is released to the public.
A KDE minor release is tagged and made available to the packagers.
A KDE minor release is released to the public.
A KDE minor release is tagged and made available to the packagers.
A KDE minor release is released to the public.
A KDE minor release is tagged and made available to the packagers.
A KDE minor release is released to the public.
KDE TechBase 