Re: KDE CVS Commit Policy

Marc Mutz <[email protected]> Tue, 20 May 2003 15:17:16 +0200

Newsgroups	gmane.comp.kde.policies
Organization	KDE
Message-ID	<[email protected]>

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

_______________________________________________
Kde-policies mailing list
[email protected]
http://mail.kde.org/mailman/listinfo/kde-policies

signature.asc (application/pgp-signature, 189 B)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+yird3oWD+L2/6DgRAsl2AJ9RbHt0UDO1pil4p5imlTXf2jbcYgCggiT6
Z3KJabUa0RMqBSpMs9yVrpQ=
=b3Ni
-----END PGP SIGNATURE-----