"Phil Holmes" <m...@philholmes.net> 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 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
