KDE/kdelibs

[Thiago Macieira]

Em Sexta-feira 27 Novembro 2009, às 10:51:37, Oswald Buddenhagen escreveu:
> > It has to be the responsibility of library developers to test their
> > work to the greatest extent possible before releasing it, regardless
> > of whether any application finds a use for it.
> 
> quite to the contrary, new major functionality (classes) is not
> permitted into kdelibs unless there are at least two real-world users
> (i'm pretty sure it was three in earlier times).

These are not exclusive things.

The fact that you're only allowed into kdelibs once you've secured two users 
of your code doesn't mean you shouldn't test it.

Usually what happens is that the functionality is born in one application, 
then moves to kdelibs when another needs it. At that point, it needs to be 
tested without either, to ensure that it will work for the third and fourth 
ones that will come by.

But either way, it is the responsibility of the library developer to test 
their work to the greatest extent possible. It should happen more or less at 
the same time as the move into kdelibs, but definitely before the next kdelibs 
release.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20091127/8afc6b1c/attachment.sig>