(→June 1, 2007: trunk/KDE is feature frozen) |
(→Milestones: targeted) |
||
| Line 100: | Line 100: | ||
=== September 25, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Release_Candidate_Cycle|Release Candidate 1]] === | === September 25, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Release_Candidate_Cycle|Release Candidate 1]] === | ||
| − | + | Targeted date for first release candidate. Only regressions (breakage caused by the KDE4 port) or grave bugs can be fixed. | |
=== October 9, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Release_Candidate_Cycle|Release Candidate 2]] === | === October 9, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Release_Candidate_Cycle|Release Candidate 2]] === | ||
| − | + | Targeted date for second release candidate and then wait for show stoppers to appear. | |
| − | === October 23, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_KDE_4.0_Released| | + | === October 23, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_KDE_4.0_Released|Targeted 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.
After 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 new or resurrected applications.
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.
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.
KDE TechBase 