KDE 3.1 release schedule draft

Neil Stevens neil at qualityassistant.com
Mon Jun 3 09:42:21 BST 2002

Hash: SHA1

On Monday June 03, 2002 01:26, Rob Kaper wrote:
> On Sun, Jun 02, 2002 at 11:50:41PM -0700, Neil Stevens wrote:
> > > I have to second this. Why is there a need to rush into new .X
> > > release ? I think a new .0.X is enough at the moment.
> >
> > 1. Anyone who wants/needs an application or a feature that is new in
> > KDE 3.1 won't find that a new 3.0.2 will be enough at the moment.
> On the other hand, anyone who wants/needs an application or feature that
> is new in KDE 3.1 would like to have the time to finish it as well.

Well, I've removed two of my own planned features because I won't have 
time, so I know what you mean here.  But wouldn't you like us to learn 
from mistakes?  In the past, we've had lax freezes.  In the past, we've 
had long delays from cramming in every feature.  In the past, we've had 
synchronization problems due to long release cycles.

But now Dirk has proposed a relatively short cycle (~1 month from the 
.0.1), and has suggested that the freeze will mean something.  These two 
suggestions together should allow the release to actually get out 
promptly.  And if the suggestions are held for 3.2, then 3.2 will be able 
to get out promptly after!  So if your feature doesn't get in 3.1, 3.2 
won't be too much of a wait either!

Dirk tried an experiment with 3.1 - the features list.  I'm surprised that 
I seem to be the only person who likes *this* cycle's new feature - its 
- -- 
Neil Stevens - neil at qualityassistant.com
"I always cheer up immensely if an attack is particularly wounding
because I think, well, if they attack one personally, it means they
have not a single political argument left." - Margaret Thatcher
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


More information about the kde-core-devel mailing list