KDE 4 Release Schedule clear-up

16Mar07


Well the news is going around the net that KDE 4.0 will be released by October 23rd. This is a very early date and will most-likely not be the final day. The worst part probably though is that it is a Tuesday. I think were are looking more at a Monday-release well and at a “huge” presentation. There hasn’t been the word out about that but the KDE 4.0 release needs more then a simple release party and the best would be a Steve Jobs-like show somewhere with a lot of media attention. Well this is a tuff one to figure out even with which distribution this show would run but 4.0 should be another take-on lowering the differences between all the distros to finally “kill” the main aspect of the damn distros that only create trouble for new users to make their way to Linux. Well back to the date. There shouldn’t be a KDE 4.0 release with missing features and a soon 4.1 when new features follow. Microsoft pulled that with Vista and the whole OS is just another embarassement for this company but 4.0 should set a new standard right away and not fill things in later because then it should be called pre4.0 or 3.9 or something but 4 dot 0. That’s why the time that is needed will be used so the release date will be pushed back – hopefully still 2007. (Rumor has it for an early christmas present)

Take your time and thing about it. Currently discussing is going on (http://thread.gmane.org/gmane.comp.kde.devel.core/40575) and I might join it later but for now just this blog about it. Just took a look at the Kubuntu herd 5 preview and I got so scared, need to do another entry for that though.

At the end… lets take a look at the draft:

Take the latest off:

4.0 Roadmap: http://techbase.kde.org/Schedules/KDE4/4.0_Release_Roadmap

Feature Plan: http://techbase.kde.org/Schedules/KDE4/4.0_Feature_Plan

Status of the parts: http://techbase.kde.org/Schedules/KDE4/Module_Status

KDE 4.0 Release Roadmap

Milestone: Subsystem Freeze

Date: 1 April 2007

Goals:

  • 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: kdelibs Hackathon Week

Start: 15 Apr 2007 (estimated) End: 21 Apr 2007 Duration: 1 week

Goals:

  • kdelibs polishing and fine-tuning.
  • Developer meeting (possible, planning TBD).
  • Full API review of Phonon and Solid (Oslo meeting)

Milestone: Alpha Release + kdelibs soft API Freeze

Date: 1 May 2007

Goals:

  • 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.

Milestone: Usability and Accessibility Review

Date: 8 May 2007

Goals:

  • Application Usability Review
  • Application Accessibility Review
  • Continues until the start of the Beta Cycle

Milestone: Feature Freeze

Date: 1 June 2007

Goals:

  • 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.

Milestone: Beta Cycle, Full kdelibs API Freeze

Start: 25 June 2007 End: 24 September 2007 Duration: 3 months (estimated)

Goals:

  • 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.

Milestone: Release Candidate Cycle

Start: 25 September 2007 End: 22 October 2007 Duration: 4 weeks (estimated)

Goals:

  • 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.

Milestone: KDE 4.0 Released

Date: 23 October 2007

Goals:

  • This date is based on an estimated 3 Beta’s and 2 Release Candidates.
Advertisements


No Responses Yet to “KDE 4 Release Schedule clear-up”

  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: