[Kde-pim] Testing changes before commiting
Thomas McGuire
Thomas.McGuire at gmx.net
Thu May 8 18:08:20 BST 2008
Hello,
after the recent broken KMail folder index branch merging, I've the urge to
say this again (even though we already talked on IRC):
TEST YOUR CHANGES before committing or merging something.
Even totally superficial testing would have prevent things like the folder
index breakage or many of the older broken enterprise merges (these are of
course not the only cases).
The folder index commit didn't even build on Linux.
(Yes, I know that it was tested on Windows, but for such changes that is not
enough)
It is of course understandable when some things break or regress, everybody
makes mistakes. But a bit of testing will prevent the worst problems, and
that's all I ask.
Not doing any testing is not acceptable.
So please test your commits in the future more.
--
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20080508/e6ce01af/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
More information about the kde-pim
mailing list