Should BC be applied to new libraries? (was RFC: New Module kdesdklibs?)
Aaron J. Seigo
aseigo at kde.org
Sat Jul 25 19:25:53 BST 2009
On Saturday 25 July 2009, David Jarvie wrote:
> For established libraries, there are very good reasons to insist on BC
> being maintained for the life of KDE4. What I would question is whether
> there shouldn't be another category of "new library", which for a limited
> period of time - say 6 or 12 months - would be allowed to break BC.
this is what we did with libplasma from kde 4.0->4.2 and we defined this
policy for new additions to kdelibs that would benefit from such a period such
as KNotificationItem:
http://techbase.kde.org/Policies/New_KDE_Library_API_Policy
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Software
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090725/57af415c/attachment.sig>
More information about the kde-core-devel
mailing list