breaking BIC for new addon libs in minor releases (was: Re: Goals? How are we doing?)
Albert Astals Cid
aacid at kde.org
Tue May 6 21:21:58 CEST 2008
A Dimarts 06 Maig 2008, Tom Albers va escriure:
> 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?
I disagree, this was never a promise we made outside kdelibs + kdepimlibs +
maybe kdebase-runtime. I agree it is good not changing SC/BC for the sake of
doing it but let's not make things imposible to work, or do you want
libokteta (e.g) to virtually be forked until KDE5 if current api is not good
> > > 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