KDE CVS Commit Policy

[Marc Mutz]

On Monday 19 May 2003 00:01, Cornelius Schumacher wrote:
<snip>
> At http://developer.kde.org/policies/commitpolicy.html you will now
> find the KDE CVS Commit Policy.
<snip>

Sorry for being late, but I've stumbled across this one (currently 
missing) rule:

n. If you fix a bug, add a regression test.

If you fix a bug in (esp. non-GUI) code, then, if feasible, add an 
automated regression test (TESTS, check_PROGRAMS in Makefile.am) for 
that bug. If there's already a regression test, add cases showing the 
bug (and related bugs) to the test program. If not, consider creating a 
new test. Strive to make the test self-checking.

Marc

-- 
We notice things that don't work. We don't notice things that do.
We notice computers, we don't notice pennies.
We notice e-book readers, we don't notice books.
                                          -- Douglas Adams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
Url : http://mail.kde.org/pipermail/kde-policies/attachments/20030520/3315dfa9/attachment.bin