Difference between revisions of "Schedules/KDE4/4.0 Release Schedule"

Jump to: navigation, search
(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 Technical Working Group is acting as release coordinator for the 4.0 releases
+
The KDE Release Team is acting as the coordinator for the 4.0 release.
  
 
==Timeline==
 
==Timeline==
Line 48: Line 48:
  
  
== Already released ==
+
= KDE 4.0 =
  
===Technical Preview 1===
+
== August 2006: Technical Preview 1 ==
'''Date:''' August 2006<br />
+
The [http://dot.kde.org/1155935483/ first technical preview], a developer release.
Release date of the [http://dot.kde.org/1155935483/ first technical preview], a developer release.
+
  
===Technical Preview 2===
+
== November 2006: Technical Preview 2 ==
 +
The [http://dot.kde.org/1162475911/ second technical preview], a developer release.
  
'''Date:''' November 2006<br />
+
== February 2007: Technical Preview 3 ==
Release date of the [http://dot.kde.org/1162475911/ second technical preview], a developer release.
+
The [http://dot.kde.org/1172249109/ third technical preview], a developer release.
 
+
===Technical Preview 3===
+
 
+
'''Date:''' February 2007<br />
+
Release date of 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.
  
== Upcoming releases  ==
+
=== May 1, 2007: Alpha Release + kdelibs soft API Freeze ===
 +
Alpha will be source only - without translations.
  
=== Milestone: Subsystem Freeze===
+
The kdelibs API is "soft-frozen", meaning that changes can be made but only with the consent of the core developers.
'''Date:''' 1 April 2007<br />
+
'''Goals:'''<br />
+
*From this date forward, no major KDE subsystem can be committed to kdelibs.
+
*The location of all classes are fixed within kdelibs
+
*Trunk is expected to contain KDE4 code only now. This effectively means that all scripts processing translations for KDE3 in trunk will cease.
+
*Extragear applications that want to release based on KDE3 are expected to move to /branches/stable and work from there.
+
* The buildsystem requirements are fixed; i.e, must not require a version of cmake greater than 2.4.5.
+
  
=== Milestone: Alpha Release + kdelibs soft API Freeze ===
+
=== June 1, 2007: trunk/KDE is feature frozen ===
'''Date:''' 1 May 2007<br />
+
Trunk is frozen for feature commits. i18n string changes are allowed.
'''Goals:'''<br />
+
* Qt 4.3 is required from here until release.
+
* The kdelibs API is frozen. This means that the classes and interfaces are not allowed to change, except with permission of the core developers.
+
* To make an API change, post a kdelibs API exception request to the kde-core-devel mailinglist with an explanation and the code. If there are no objections after a week, the change can be committed.
+
  
'''Note''': all affected modules must continue to compile and work as expected.
+
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.
  
=== Milestone: Feature Freeze ===
+
=== July 20, 2007: Message Freeze ===
'''Date:''' 1 June 2007<br />
+
Only previously untranslated strings or clear errors in strings can be fixed - no new strings.
'''Goals:'''<br />
+
*The KDE main modules are frozen for new features.
+
*No new features are allowed, the focus is on stabilizing the applications and fixing all bugs.
+
*The main module maintainers must indicate if they will follow the release schedule or will divert and not be released together with KDE 4.0.
+
  
 +
=== July 25, 2007: Beta2 ===
 +
Beta 2 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
  
=== Milestone: Beta Cycle, Full kdelibs API Freeze ===
+
=== August 25, 2007: Beta3 ===
'''Start''': 25 June 2007<br />
+
Beta 3 is prepared and released after some initial testing. The incoming bugs will be reviewed for their severity.
'''End:''' 24 September 2007<br />
+
'''Duration:''' 3 months (estimated)<br />
+
'''Goals:'''<br />
+
*From this date forward, a Beta Version will be published every month until most grave bugs are resolved.
+
*The kdelibs API is now frozen solid.
+
*Translations are included starting with the second Beta, thus beginning a string freeze. Exceptions can be requested on the kde-i18n mailinglist.
+
  
 +
=== 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.
  
=== Milestone: Release Candidate Cycle ===
+
=== September 25, 2007: Release Candidate 1 ===
'''Start:''' 25 September 2007  <br />
+
Targetted date for first release candidate. Only regressions (breakage caused by the KDE4 port) or grave bugs can be fixed.
'''End:''' 22 October 2007  <br />
+
'''Duration:''' 4 weeks (estimated)<br />
+
'''Goals:'''<br />
+
*From this date forward, a Release Candidate will be released every two weeks until *all* grave bugs are resolved.
+
* After the first Release Candidate there is a total release freeze. This means only regressions (breakage caused due to the KDE4 port) or grave bugs can be fixed, but nothing else.
+
* With the first Release Candidate, a list of languages which will be included with the KDE 4.0 release will be made available, based on the usual rules.
+
  
 +
=== October 9, 2007: Release Candidate 2 ===
 +
Targetted date for second release candidate and then wait for show stoppers to appear.
  
=== Milestone: KDE 4.0 Released ===
+
=== October 23, 2007: Targetted Release Date ===
'''Date:''' 23 October 2007<br />
+
'''Goals:'''<br />
+
* This date is based on an estimated 3 Beta's and 2 Release Candidates.
+

Revision as of 18:08, 16 March 2007

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.

Contents

Timeline


KDE 4.0

August 2006: Technical Preview 1

The first technical preview, a developer release.

November 2006: Technical Preview 2

The second technical preview, a developer release.

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.

Milestones

Milestones help guide us toward a final release, and the dates are subject to change. For more details see our 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


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal