(be more precise on when it happened. remove link to discussion, as all this is already done.)

(11 intermediate revisions by 8 users not shown)

Line 1:

Line 1:

−

KDE 3.5 is the fifth (and this time really last) feature release in the KDE 3.x series.

+

KDE 3.5 is the fifth (and this time really last) feature release in the KDE 3.x series. The list of planned features can be found in a [http://developer.kde.org/development-versions/kde-3.5-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.5 releases.

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

Line 6:

Line 6:

===August 1st, 2005: Officially close of feature list===

===August 1st, 2005: Officially close of feature list===

−

The list of features for KDE 3.5 should already be settled by then, but after that date are only KDE 4 features. At this date, /branches/KDE/3.5 is frozen for feature commits that are not listed in the [[KDE 3.5 Feature Plan|feature plan]].

+

The list of features for KDE 3.5 should already be settled by then, but after that date are only KDE 4 features. At this date, /branches/KDE/3.5 is frozen for feature commits that are not listed in the [http://developer.kde.org/development-versions/kde-3.5-features.html feature plan].

===August 5th, 2005: Alpha 1 prepared===

===August 5th, 2005: Alpha 1 prepared===

Line 88:

Line 88:

===January 23rd, 2007: Expected release date of KDE 3.5.6===

===January 23rd, 2007: Expected release date of KDE 3.5.6===

+

Delay see http://bugs.kde.org/show_bug.cgi?id=140307

== KDE 3.5.7 ==

== KDE 3.5.7 ==

−

===April 16th, 2006: Message and documentation freeze===

+

===April 16th, 2007: Message and documentation freeze===

After this date the same message freeze applies as for released versions (i.e. only previously untranslated strings or clear errors in strings can be fixed - no new strings).

After this date the same message freeze applies as for released versions (i.e. only previously untranslated strings or clear errors in strings can be fixed - no new strings).

−

===April 30th, 2007: Tagging KDE 3.5.7===

+

===May 14th, 2007: Tagging KDE 3.5.7===

−

===May 8th, 2007: Expected release date of KDE 3.5.7===

+

===May 22nd, 2007: Expected release date of KDE 3.5.7===

+

+

== KDE 3.5.8 ==

+

+

===October 7th, 2007: Tagging KDE 3.5.8===

+

+

===October 15th, 2007: Expected release date of KDE 3.5.8===

+

+

== KDE 3.5.9 ==

+

+

===February 13th, 2008: Tagging KDE 3.5.9===

+

+

===February 19th, 2008: Expected release date of KDE 3.5.9===

+

+

== KDE 3.5.10 ==

+

===August 26th, 2008: Expected release date of KDE 3.5.10 ===

==Frequently Asked Questions==

==Frequently Asked Questions==

;What's the deal with that feature-plan?: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.5 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".<br />The feature-plan is open for commits till August 1st 2005. ''Later additions'' require review first. I will try to respect outstanding entries in the release schedule.<br />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.

;What's the deal with that feature-plan?: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.5 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".<br />The feature-plan is open for commits till August 1st 2005. ''Later additions'' require review first. I will try to respect outstanding entries in the release schedule.<br />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.

Latest revision as of 14:26, 9 January 2009

KDE 3.5 is the fifth (and this time really last) 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.
Stephan Kulow is acting as release coordinator for the 3.5 releases.

The list of features for KDE 3.5 should already be settled by then, but after that date are only KDE 4 features. At this date, /branches/KDE/3.5 is frozen for feature commits that are not listed in the feature plan.

For the GUI strings (also known as messages), you can fix typos and make small
changes to them. You can also add new error messages to improve error
feedback to users. (Adding other kinds of messages are not allowed. In case
of questions or doubts, please ask the kde-i18n-doc@kde.org mailing list.)
For the documentation, the changes should also be rather small, except when
fixing inaccurate or outdated documentation. You can also port documentation
that has been prepared in the trunk/KDE modules. (If you change any
documentation for the KDE 3.5 branch, please be sure that the change is also
in the corresponding module of trunk/KDE. However you can do a little later,
in case that you would not have much time during the lift period.)

For the GUI strings (also known as messages), you can fix typos and make small changes to them. You can also add new error messages to improve error feedback to users. (Adding other kinds of messages are not allowed. In case of questions or doubts, please ask the kde-i18n-doc@kde.org mailing list.)

For the documentation, the changes should also be rather small, except when fixing inaccurate or outdated documentation. You can also port documentation that has been prepared in the trunk/KDE modules. (If you change any documentation for the KDE 3.5 branch, please be sure that the change is also in the corresponding module of trunk/KDE. However you can do a little later, in case that you would not have much time during the lift period.)

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.5 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 August 1st 2005. 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.