lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lilypond patchy and other Lilypond problems


From: David Kastrup
Subject: Re: Lilypond patchy and other Lilypond problems
Date: Fri, 27 Apr 2012 10:28:54 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> OK.  Regtest checking can mean three things.  1) Between releases,
> comparing the output of the regtests with what they looked like before
> and flagging any differences as potential problems.  I do this.  2)
> Doing the same thing for patches.  Patchy does this, helped by a
> human, currently James and was David.

There is no reason whatsoever that this should only be done by a single
person.  I would expect that _every_ person contributing more than two
patches per month should be able, after uploading a patch, to be running
test-patches.py and thus emptying the queue.

This has the consequences that

a) his own submission will get timely and qualified testing
b) the queue does not build up
c) it is not always the same people who get stuck with testing
d) he can be more nonchalant about testing his submission in advance
   since a bad test upload mostly implies more work for himself, and
   then not all that much.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]