The list of planned features can be found in a [http://developer.kde.org/development-versions/kde-3.2-features.html separate document].

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.

+

[mailto:coolo@kde.org Stephan Kulow] is acting as release coordinator for the 3.2 releases.

[mailto:coolo@kde.org Stephan Kulow] is acting as release coordinator for the 3.2 releases.

Latest revision as of 13:24, 9 May 2008

KDE 3.2 is the second feature release in the KDE 3.x series.
The list of planned features can be found in a separate document.
All dates given here are subject to revision, but we will try our best to stick to them if possible.

The HEAD branch is frozen for feature commits that are not listed in the planned-feature document. Only bugfixes and the listed feature-commits are to be committed. Still, binary compatibility is not required, i18n string changes are allowed. KDE 3.2 Alpha 1 is tagged and tarballs are made for testing.

The HEAD branch is tagged as Beta 2 and is released to the packagers. When the binaries are ready (to be expected 4th of December), the CVS opens again for the way it was after Beta1.
As most are to be expected to be on vacation towards the end of the year, commiters are asked to be very conservative with their changes and ask for second views on the lists.

Release Candidate 1 is prepared and tagged as KDE_3_2_0_RELEASE and a KDE_3_2_BRANCH is created. New Release Candidates will be released as show stopper bugs appear (and are fixed). If everything goes fine...

In the past, there were a lot of complaints about a rather long "freeze period", so this is an attempt to address this issue. Basically the idea is that you add an entry about what feature you want to finish in the 3.2 timeframe and mark it as done when you completed it. This helps me to get an overview about the outstanding changes and in return allows you to work on the missing parts even in the "freeze period".

The feature-plan is open for commits till September 1st. Later additions require review first. I will try to respect outstanding entries in the release schedule.

Please understand that although this gives you greater freedom over SVN, it also requires more discipline in making sure that your additions don't have unwanted side effects.