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

List:       kde-core-devel
Subject:    Re: KRASH release: about the freeze.
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-11-17 13:59:02
[Download RAW message or body]

"Dirk A. Mueller" wrote:
> 
> On Mit, 17 Nov 1999, Waldo Bastian wrote:
> 
> > 1)
> >
> > kdelibs is frozen. This means that you should not introduce any changes
> > to the API of kdelibs. If you _really_ need a change in the API discuss
> > it on kde-core-devel first. (Hint to some: Discuss it _before_ you
> > commit :-)
> > Basic rules: fix all the code your change breaks and document the
> > changes in KDE2PORTING.
> 
> Just a small question: Wasn't the idea of Krash that we provide an API that
> won't change much until KDE 2.0 release?
> 
> Right now there are some things held back, i.e. the new KFileDialog, because
> it changes the API.

The above two statements are in direct contradiction ;-) If we hold
something back from Krash because it changes the API then put it in
afterwards Krash no longer represents the KDE2.0 API. The API will
change on certain components that are being reimplemented or are
incomplete, and there no way to avoid that. The goal I believe is to
provide something reasonably stable and as close to what will be KDE2 as
possible. It will allow people to develop betas of their ports then
update to the final KDE2 with minimal fuss.

In my opinion this is more of a standardized developers preview, not a
API guarantee. Developers can familiarize themselves with the new code
and by the time KDE2 is ready hopefully have their applications ready to
be released as well with minimal changes.

> 
> Dirk

-- 
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com

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