From kde-core-devel  Tue Nov 26 03:20:34 2002
From: Trevor Harmon <trevor () vocaro ! com>
Date: Tue, 26 Nov 2002 03:20:34 +0000
To: kde-core-devel
Subject: Re: KDE 3.1 final tarballs
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=103828092824543

> How did you get the idea that you were only allowed to fix showstopper
> bugs during the RC cycle?

The KDE 3.1 Release Plan at=20
http://developer.kde.org/development-versions/kde-3.1-release-plan.html say=
s:
"Monday September 30, 2002: i18n string freeze. The i18n strings are frozen=
=2E=20
The HEAD branch is frozen for release. Any non-trivial patches to CVS have =
to=20
be approved by at least one other related developer."

I thought this meant that, since Sept. 30, I can't go to bugs.kde.org, find=
=20
just any old bug, and apply a patch for it. It has to be a serious bug, suc=
h=20
as a crash or file corruption/deletion. And even then, my patch must be=20
reviewed by another developer. Otherwise, my bug fix may have a side-effect=
=20
that introduces more bugs, which would then have to be fixed, which may cau=
se=20
more side-effects, and so on and so on, causing the release schedule to dra=
g=20
on forever. I thought that was the whole point of freezing the HEAD. Or hav=
e=20
I misunderstood something yet again?

Trevor