<br><br><div class="gmail_quote">On Fri, Mar 8, 2013 at 2:01 PM, Szilárd Páll <span dir="ltr"><<a href="mailto:szilard.pall@cbr.su.se" target="_blank">szilard.pall@cbr.su.se</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>Hi,<br><br>I suggest that we allow and encourage code verification/testing by users/developers to complement the Jenkins verification.<br><br>Why?<br></div>- there is only +1 verify, no +2<br></div>
- hence regular registered users can't vote for verify;<br><div><div>- we should be able to distinguish between the Jenkins verification and user verification (=testing), but allow submission only with +2 Verify or more;<br>
<br>I suggest:<br>- allowing any developer to give +1 verified;<br>- bumping the Jenkins verification to +2;<br>- requiring Verified +2 for submit;<br>- allowing core-dev to give +2? (Not sure about this, it would only be useful to override the failed jenkins verification).<br>
<br></div><div>Let me know what you all think!</div></div></div></blockquote><div><br></div><div>Sounds great.</div><div><br></div><div>Mark </div></div>