[Koha-devel] Commit messages

[Jared Camins-Esakov]

I sent my message just a moment too soon.


>  3) A detailed test plan. When I say "detailed," I mean that it should
> include enough detail that it could be followed by someone familiar with
> Koha who does not use whatever section of the code you are editing. A test
> plan with forty steps may seem daunting, but it really isn't. It's
> considerate. Ideally, the test plan should cover how to confirm the bug
> *and* how to confirm that the patch fixed the problem, if the two
> procedures are not entirely identical (for example, if your patch involves
> Zebra configuration changes, note which files need to be updated; I favor a
> tl;dr section which includes information of this sort).
>

A perfect example of what I'm talking about is in the final comment on bug
8557: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8557#c16

In *7* sentences, Marc was able to provide all the information I needed for
testing.

Regards,
Jared

-- 
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcamins at cpbibliography.com
(web) http://www.cpbibliography.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20121128/7b18aa72/attachment.html>