<font color='black' size='2' face='arial'>You could consid<font size="2">er gerrit as a sort of next... even though it's not a <font size="2">single named/shared branch<font size="2">, it's a similar thing conceptually. </font></font>Stuff doesn't get merged to master till it passes the <font size="2">'next' g<font size="2">a<font size="2">untlet (gerrit code review and CDash@home dashboar<font size="2">ds for VTK)</font>. Passing that means convincing peers, and making dashboards gr<font size="2">een.</font></font></font></font></font><font color="black" face="arial" size="2">
<div> <br>
</div>
<div> <br>
</div>
<div> <br>
</div>
</font>
<div style="font-family:arial,helvetica;font-size:10pt;color:black"><font color="black" face="arial" size="2">-----Original Message-----<br>
From: Pat Marion <pat.marion@kitware.com><br>
To: David Cole <dlrdave@aol.com><br>
Cc: bill.lorensen <bill.lorensen@gmail.com>; vtk-developers <vtk-developers@vtk.org><br>
Sent: Mon, Feb 18, 2013 2:52 am<br>
Subject: Re: [vtk-developers] Continuous Build Defect Process<br>
<br>
</font>
<div id="AOLMsgPart_1_09be35ab-4dc0-4055-8bb9-320ae57ac96b"><font color="black" face="arial" size="2">
To clarify, I meant a next/master branch model *in addition* to code review, not as replacement.<br>
<br>
Pat<br>
<br>
</font>
<div class="gmail_quote"><font color="black" face="arial" size="2">On Mon, Feb 18, 2013 at 2:02 PM, David Cole <span dir="ltr"><<a href="mailto:dlrdave@aol.com">dlrdave@aol.com</a>></span> wrote:<br>
</font><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="black" face="arial" size="2"><font color="black" face="arial">Developer<font> diligence is always required regardless of y<font>our workflow or development model.<br>
<br>
<font>I would tend to lean more toward Bill's statement than Pat's.<br>
<br>
<font>With the CDash@home actually green (very soon, very soon) it should be <font>an automatic reason to reject a topic if it introduces warnings, errors or test failures on the CDash@home dashboards.</font></font><br>
</font></font></font></font></font><font color="black" face="arial">
<div> <br>
<font>Even after merging to master, dashboard observation is required to verify that it didn't break anything on an as-yet-untested combi<font>nation of platforms and options.<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
<font>D</font><br>
</font></span></font></font>
</div>
<div>
<div class="h5">
<div> <br>
</div>
<div> <br>
</div>
<div style="font-size:10pt;font-family:arial,helvetica">-----Original Message-----<br>
From: Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>><br>
To: Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>><br>
Cc: VTK Developers <<a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a>><br>
Sent: Sun, Feb 17, 2013 7:12 pm<br>
Subject: Re: [vtk-developers] Continuous Build Defect Process<br>
<br>
<div>
I do not see <span>how next/master is better than a good <span></span>gerrit review.</span>
<div><br>
On Sunday, February 17, 2013, Pat Marion wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is great, Bill. Thanks to everyone who helped out!<br>
<br>
The statement on the wiki "Once reduced to 0, developer diligence is needed to keep the defects to 0. The burden is on the Gerrit reviewers" I agree with the first statement, but not the second. I think that the best way to keep the number at 0 is to have a next & master branch model.<br>
<br>
Pat<br>
<br>
<div class="gmail_quote">On Sat, Feb 16, 2013 at 6:15 AM, Bill Lorensen <span dir="ltr"><<a>bill.lorensen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Folks,<br>
<br>
Some of you may be interested in the process we used to reduce the<br>
Continuous build defects to 0:<br>
<a target="_blank" href="http://itk.org/Wiki/VTK/SoftwareQuality/ContinuousBuildTestFailures">http://itk.org/Wiki/VTK/SoftwareQuality/ContinuousBuildTestFailures</a><br>
<br>
Thanks to all who contributed gerrit topics.<br>
<br>
Bill<br>
_______________________________________________<br>
Powered by <a target="_blank" href="http://www.kitware.com">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a target="_blank" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a target="_blank" href="http://www.vtk.org/mailman/listinfo/vtk-developers">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</blockquote></div>
<br>
</blockquote></div>
<br>
<br>
-- <br>
Unpaid intern in BillsBasement at noware dot com<br>
<br>
</div>
<div style="font-size:12px;font-family:Tahoma,Verdana,Arial,Sans-Serif;margin:0px">
<pre style="font-size:9pt"><tt>_______________________________________________
Powered by <a target="_blank" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a target="_blank" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Follow this link to subscribe/unsubscribe:
<a target="_blank" href="http://www.vtk.org/mailman/listinfo/vtk-developers">http://www.vtk.org/mailman/listinfo/vtk-developers</a>
</tt></pre>
</div>
</div>
</div>
</div>
</font></blockquote></div>
<br>
</div>
<!-- end of AOLMsgPart_1_09be35ab-4dc0-4055-8bb9-320ae57ac96b -->
</div>
</font>