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

List:       kde-pim
Subject:    [Kde-pim] KMail independent releases
From:       Bernhard Reiter <bernhard () intevation ! de>
Date:       2002-11-28 10:43:32
[Download RAW message or body]

It is my general observation that 
it should be made easier to make independent releases of KMail
or other KDE components like kdepim.

It would help the stability of the interfaces of the various parts.
I've saw the hint: "Just update everything from" too often 
when watching KDE related development

The additional effort you describe to make releases of single parts
seems to be too high.

On Thursday 28 November 2002 09:22, Cornelius Schumacher wrote:

> About independent releases: I don't think it's a good idea to make
> independent releases of kdepim like KOffice does. We should take part in
> the normal release cycle, otherwise we would need a significant amount of
> additional work to organize the releases which I think is better spent on
> coding.
>
> This does not mean that it wouldn't make sense to make additional releases
> of parts of kdepim independently of the standard KDE release plan. For
> example we could release KitchenSync before 3.2, if it shows to be usable.
>
> > Moving the KMail Part interface into kdelibs isn't a good solution, as
> > it means pim users will end up having to update kdelibs to update
> > kdepim, and that means they will end up having to update all of KDE.
>
> As a developer you can update parts of kdelibs and you will have to anyway
> because libkabc is in kdelibs. Making a separate release of parts of
> kdelibs is certainly also possible, although it will require some
> additional effort.


[Attachment #3 (application/pgp-signature)]
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

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