> I like this idea. One tweak I'd make is to introduce the idea of > Verified+1 for smoke and Verified+2 for regressions. Why? Because it > seems like a lot of people won't even review a patch until they can > see that it has been sanity-checked. If we formally require review > before verification, and informally need verification before review, > we're stuck. I should have made this clearer in the steps I listed. Under the 2nd step (I should have numbered as well), I've mentioned that Zuul will report back the status of smoke/pre-review tests. This is the Verified+1. Though I was thinking of using different flags, we can use Verified it self to serve both pre and post review checks. _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
