David Anderson <david.anderson@calixo.net> writes:
> Perhaps that last bit is a little complicated. Perhaps restrict the
> text in that section of hacking.html to "6-way tests if possible, or
> else as much as you can" and leave the "can we go public?" logic to
> the release manager's section. However, I find it good that people
> who are signing know what it will take to get a release out the door.
> It helps getting signatures for the bits that haven't been tested yet.
Maybe the best policy is simply for people to state what they tested,
when they post their sigs, and let the release manager keep track of
the coverage?
> This is why Karl (among others) is much appreciated at the signature
> stage, as he plays by the full rules and does full 6-way testing, thus
> letting us slackers be lazy.
Why, I appreciate the appreciation, sir.
http://pastebin.ca/30394 has the script (make-checks.sh) I use to do
this. It doesn't use davautocheck.sh, so one does need to tweak one's
httpd.conf before running it. We could put it in tools/dev/ if people
want; if somebody is really ambitious they could make it optionally
work with davautocheck.sh.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 23 00:39:57 2005