All dates given here are subject to revision, but we will try our best to stick to them if possible. Note that "Tagging" that the codebase is closed for this release on the date mentioned. The tarballs and packages are then being prepared and released approximately one week later. The KDE Release Team is acting as the coordinator for the 4.0 release.
Note the release is done in two portions: the KDE Development Platform 4.0 and the KDE Desktop 4.0. The KDE Desktop contains the complete package: all the main modules plus a release of the extragear module. The KDE Development Platform contains all the bits and pieces necessary to develop KDE4 applications. This means kdesupport, kdelibs, kdepimlibs and kdebase/runtime. Note the earlier freeze date for those modules and make sure you don't miss the deadline to get your fixes in.
Milestones help guide us toward a final release, and the dates are subject to change. For more details see our roadmap.
- 1 KDE 4.0
- 1.1 Upcoming milestones
- 1.2 Past Milestones
- 1.2.1 October 8, 2007: Beta3
- 1.2.2 October 8, 2007: KDE Development Platform frozen solid
- 1.2.3 August 29, 2007: Beta2
- 1.2.4 July 26, 2007: Beta1
- 1.2.5 July 24, 2007: Core Library Freeze
- 1.2.6 June 27, 2007: Alpha2 Tagging
- 1.2.7 June 1, 2007: trunk/KDE is module frozen
- 1.2.8 May 3, 2007: Alpha Tagging
- 1.2.9 May 1, 2007: kdelibs Soft Freeze
- 1.2.10 April 2, 2007: Subsystem Freeze
- 1.2.11 February 2007: Technical Preview 3
- 1.2.12 November 2006: Technical Preview 2
- 1.2.13 August 2006: Technical Preview 1
These are the upcoming milestones. When they have been passed move them to the top of the Past Milestones section.
October 19, 2007: Total Release Freeze
This is the very last chance for committing anything that isn't reviewed on the development lists. If in doubt, ask the release coordinator.
October 24, 2007: Tagging Release Candidate 1, Tagging KDE Development Platform
Release Candidate 1 of the Desktop is prepared, initially tested and released on October 30. The KDE Development Platform is tagged for final release and released on October 30.
November 14, 2007: Tagging Release Candidate 2
Release Candidate 2 is prepared, initially tested and released on November 20.
December 5, 2007: Tagging Final Release
Final release candidate is prepared and tested.
December 11, 2007: Targeted KDE 4.0 Release Date
These milestone have already been passed. They are listed in reverse chronological order to keep the most recent milestones at the top of the list.
October 8, 2007: Beta3
Beta 3 is prepared, initially tested and released on October 18.
October 8, 2007: KDE Development Platform frozen solid
The KDE Development Platform is frozen. For the modules that are included in the KDE Development Platform, only patches reviewed on the development lists are permitted. If in doubt, contact the release coordinator. The KDE Development Platform covers kdesupport, kdelibs, kdepimlibs, kdebase/runtime and kdebindings (Ruby and Python bindings only).
August 29, 2007: Beta2
Beta 2 is prepared and released after some initial testing.
Trunk is frozen for feature commits. i18n string changes are allowed.
July 26, 2007: Beta1
Beta 1 is prepared and released after some initial testing.
July 24, 2007: Core Library Freeze
The core library APIs are frozen solid.
June 27, 2007: Alpha2 Tagging
The Alpha2 will be source only -- without translations.
June 1, 2007: trunk/KDE is module frozen
Trunk is frozen for new or resurrected applications.
A list of main modules that will be included in the final release will be made.
May 3, 2007: Alpha Tagging
The Alpha will be source only -- without translations.
May 1, 2007: kdelibs Soft Freeze
The kdelibs API is "soft-frozen", meaning that changes can be made but only with the consent of the core developers.
April 2, 2007: Subsystem Freeze
From this date forward, no new KDE subsystem or major changes can be committed to kdelibs.
The buildsystem requirements (i.e. cmake version) are fixed.
February 2007: Technical Preview 3
The third technical preview, a developer release.
The kdelibs API will remain as stable as possible after that, so that application developers (in particular those not having their code in the KDE SVN) can start porting towards a stable kdelibs API.
Of course the applications in the KDE SVN will have been ported all along, and it will possible to alpha-test them at this stage.
November 2006: Technical Preview 2
The second technical preview, a developer release.
August 2006: Technical Preview 1
The first technical preview, a developer release.