breaking BIC for new addon libs in minor releases (was: Re: Goals? How are we doing?)

Tom Albers tomalbers at
Tue May 6 18:39:06 CEST 2008

Op dinsdag 06 mei 2008 18:30 schreef u:
> > I disagree. I think it is a must to be BC between minor releases.
> For everything?


> > If you want to be bic && public, go to extragear/libs untill you are
> > ready...
> What would this change for 3rd-party developers? 

You can make a release whenever you like and bump the major so version of the lib as you like in each release.

> For me it would be more work, 
> as I would have development spanned between extragear/libs and kdeutils. And 
> it would add an additional (if only soft) dependency between modules. 

No, as long as you make releases from the library, it's is just another 'external' dependency. As long as it is not a cyclic dependency as we now face with libkipi, it is not a problem.


More information about the release-team mailing list