[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    deeper freeze
From:       Stephan Kulow <coolo () kde ! org>
Date:       2003-11-11 9:43:30
[Download RAW message or body]

Hi!

The actual freeze didn't really work out as expected. The
rate of reorganizing commits isn't really what it should be
in this time of release schedule ;(

Starting with tomorrow I'd like to emphasize the release
freeze even more in applying the following commit rules:
* all non-oneliner commits have to have an "reviewed by"
  line where another developer, that can be expected to know
  the topic, is named that gave his ok.
* all commits to kdelibs + kdebase have to be posted to 
  kde-core-devel first (the only exception to this are apidocs 
  changes and artwork changes)

Starting with next monday (17.11) the extra rule applies:
* Every commit to released modules beside kde-i18n have 
  to contain a bug number with severity >= major. I'm trying 
  to watch the activities around bugs.kde.org as close as I can,
  so make reasonable use of the severities.

So far I count 50 confirmed bugs >= major. Every other bug 
can wait for 3.2.1. We made excellent progress and KDE CVS 
is an excellent shape (if you look at the 50 bugs, you'll figure that
most of them aren't new) - it just got some rough edges.

Everyone that isn't able to help with the big bugs I'd like to ask 
to test (e.g. move away your .kde for a moment and look at 
KDE as a user :) and/or send Lauri patches for updated docu
(but avoid duplicated work and check 
http://people.fruitsalad.org/lauri/doc-patches/ before you start
writing)

Greetings, Stephan
P.S. feedback and discussion welcome - I'm little disappointed
  on the little feedback I get about the schedule.

-- 
There may be no I in TEAM, but a M and an E.
[prev in list] [next in list] [prev in thread] [next in thread]