tagged KDE 3.96
Stephan Kulow
coolo at kde.org
Thu Nov 15 12:46:01 CET 2007
Am Donnerstag 15 November 2007 schrieb Cyrille Berger:
> On Thursday 15 November 2007, Aaron J. Seigo wrote:
> > > Heck, we could eliminate RCs completely and go directly from Beta6 to
> > > 4.0.0. Hm... why not do that?
> >
> > ditto.
> >
> > rather unconventional of course =)
>
> If I may (and you may as well discard my opinion), but usually you need to
> plan one RC (no real need for a RC2 unless you plan to have a critical bug
You think backwards. You assume we'll release the RC when all bugs are fixed.
While in reality we release RC1 on week X. And _after_ we released RC1, we're
going to decide which bugs left in there (I through a "Total: 15052 bugs and
13244 wishes" in here :) are to be fixed and while we fix them, heading
towards RC2, new bugs are found that need discussing.
Now something dangerous comes into play, which makes your "usually" pretty
unusual: KDE 4.0 will gain tons of new users/testers once RC1 is released and
find tons of different bugs that weren't found before. So the risk of finding
critical bugs once RC1 is out, is immense.
So the question is: how long are we going to play this iteration. Till
eternity or till RC3 or RC5 or till the majority of the release-team gives a
GO or till Dirk gives it? Or everyone in the release-team (for that we need a
list of who's in - the list has 103 members, that's quite some to ask :)
So executive summary: If you plan for only one RC, you can just as well plan
KDE 4.0.1 right away.
Greetings, Stephan
More information about the release-team
mailing list