deeper freeze

Ingo Klöcker kloecker at kde.org
Tue Nov 11 22:50:47 GMT 2003


On Tuesday 11 November 2003 10:43, Stephan Kulow wrote:
> 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.

So we can stop fixing crashes? Great news! :-p

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031111/a67e2ed3/attachment.sig>


More information about the kde-core-devel mailing list