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 the 4.0 release.
The first technical preview, a developer release.
The second technical preview, a developer release.
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.
Milestones help guide us toward a final release, and the dates are subject to change. For more details see our roadmap.
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.
The kdelibs API is "soft-frozen", meaning that changes can be made but only with the consent of the core developers.
The Alpha will be source only -- without translations.
Trunk is frozen for new or resurrected applications.
A list of main modules that will be included in the final release will be made.
The Alpha2 will be source only -- without translations.
The core library APIs are frozen solid.
Beta 1 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
Trunk is frozen for feature commits. i18n string changes are allowed.
Beta 2 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
This is the very last for committing anything that isn't reviewed on the development lists. If in doubt, ask the release coordinator.
Targeted date for first release candidate. Only regressions (breakage caused by the KDE4 port) or grave bugs can be fixed.
Targeted date for second release candidate and then wait for show stoppers to appear.