Moving ThreadWeaver to kdelibs
Aaron J. Seigo
aseigo at kde.org
Wed Sep 14 00:20:09 BST 2005
On Tuesday 13 September 2005 09:46, Benjamin Meyer wrote:
> start from scratch. And if it goes in libs we probably want to start
> having everything in libs have some form of unit testing (the more the
> better of course)
i'd like to see this be a base requirement for every new class / lib that is
added to kdelibs for kde4, much like "must have a docbook manual" is for new
applications.
--
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050913/89b97442/attachment.sig>
More information about the kde-core-devel
mailing list