m (Schedules/KDE 4.0 Release Schedule moved to Schedules/KDE4/4.0 Release Schedule: consistency) |
(scrubbing. make it read more like the 3.5 release schedules) |
||
| Line 1: | Line 1: | ||
All dates given here are subject to revision, but we will try our best to stick to them if possible. | All dates given here are subject to revision, but we will try our best to stick to them if possible. | ||
| − | The KDE | + | The KDE Release Team is acting as the coordinator for the 4.0 release. |
==Timeline== | ==Timeline== | ||
| Line 48: | Line 48: | ||
| − | = | + | = KDE 4.0 = |
| − | == | + | == August 2006: Technical Preview 1 == |
| − | + | The [http://dot.kde.org/1155935483/ first technical preview], a developer release. | |
| − | + | ||
| − | == | + | == November 2006: Technical Preview 2 == |
| + | The [http://dot.kde.org/1162475911/ second technical preview], a developer release. | ||
| − | + | == February 2007: Technical Preview 3 == | |
| − | + | The [http://dot.kde.org/1172249109/ 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. | 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. | ||
| Line 68: | Line 63: | ||
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. | 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 == | ||
| + | |||
| + | Milestones help guide us toward a final release, and the '''dates are subject to change'''. For more details see our [[Schedules/KDE4/4.0_Release_Roadmap|roadmap]]. | ||
| + | |||
| + | === April 1, 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. | ||
| − | == | + | === May 1, 2007: Alpha Release + kdelibs soft API Freeze === |
| + | Alpha will be source only - without translations. | ||
| − | + | The kdelibs API is "soft-frozen", meaning that changes can be made but only with the consent of the core developers. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | === | + | === June 1, 2007: trunk/KDE is feature frozen === |
| − | + | Trunk is frozen for feature commits. i18n string changes are allowed. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | A list of main modules that will be included in the final release will be made. | |
| + | === June 25, 2007: Beta1 === | ||
| + | Beta 1 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity. | ||
| − | === | + | === July 20, 2007: Message Freeze === |
| − | + | Only previously untranslated strings or clear errors in strings can be fixed - no new strings. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | === July 25, 2007: Beta2 === | ||
| + | Beta 2 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity. | ||
| − | === | + | === August 25, 2007: Beta3 === |
| − | + | Beta 3 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | === September 23, 2007: Total Release Freeze | ||
| + | This is the very last for committing anything that isn't reviewed on the development lists. If in doubt, ask the release coordinator. | ||
| − | === | + | === September 25, 2007: Release Candidate 1 === |
| − | + | Targetted date for first release candidate. Only regressions (breakage caused by the KDE4 port) or grave bugs can be fixed. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | === October 9, 2007: Release Candidate 2 === | ||
| + | Targetted date for second release candidate and then wait for show stoppers to appear. | ||
| − | === | + | === October 23, 2007: Targetted Release Date === |
| − | + | ||
| − | + | ||
| − | + | ||
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.
Alpha will be source only - without translations.
The kdelibs API is "soft-frozen", meaning that changes can be made but only with the consent of the core developers.
Trunk is frozen for feature commits. i18n string changes are allowed.
A list of main modules that will be included in the final release will be made.
Beta 1 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
Only previously untranslated strings or clear errors in strings can be fixed - no new strings.
Beta 2 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
Beta 3 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
=== September 23, 2007: Total Release Freeze This is the very last for committing anything that isn't reviewed on the development lists. If in doubt, ask the release coordinator.
Targetted date for first release candidate. Only regressions (breakage caused by the KDE4 port) or grave bugs can be fixed.
Targetted date for second release candidate and then wait for show stoppers to appear.
KDE TechBase 