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

List:       kde-core-devel
Subject:    Re: KDE 2.0.1 and 2.1 Release Schedule
From:       Thomas <zander () xs4all ! nl>
Date:       2000-11-22 23:22:55
[Download RAW message or body]

> On Wednesday 22 November 2000 14:40, David Faure wrote:
> > On Wednesday 22 November 2000 22:31, Dirk Mueller wrote:
> > > On Mit, 22 Nov 2000, Christian Gebauer wrote:
> > > > kdenetwork/KNode should go into 2.1, we already have a number
> > > > of nice additions in there and it seems to be quite stable again.
> > >
> > > KDE 2.1 is as in "kdelibs and kdebase" ;)
> >
> > Why exclude other packages if they are ready to be released ?
> >
> > Do you really think we want to maintain 8 release schedules ?
> >
> > I think the point is: if some modules have significant changes and
> > are ready, they should go in. If modules have almost no change
> > (kdetoys?), then there's no point, and if modules are not yet ready
> > (e.g. kword might not be), then they can be released separately....
> 
>   I don't think that any application which was in KDE 2.0 is in worse shape 
> in the CVS than it was before, so I really think we need to put all of them 
> in the beta. KWord which has a branch is a special case. 

Simply because it has a branch means that it can be released. Just that about
5 fixes have been made on HEAD..

-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new

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