[vtk-developers] Continuous Build Defect Process

Bill Lorensen bill.lorensen at gmail.com
Sun Feb 17 19:12:24 EST 2013


I do not see how next/master is better than a good gerrit review.

On Sunday, February 17, 2013, Pat Marion wrote:

> This is great, Bill.  Thanks to everyone who helped out!
>
> 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.
>
> Pat
>
> On Sat, Feb 16, 2013 at 6:15 AM, Bill Lorensen <bill.lorensen at gmail.com<javascript:_e({}, 'cvml', 'bill.lorensen at gmail.com');>
> > wrote:
>
>> Folks,
>>
>> Some of you may be interested in the process we used to reduce the
>> Continuous build defects to 0:
>> http://itk.org/Wiki/VTK/SoftwareQuality/ContinuousBuildTestFailures
>>
>> Thanks to all who contributed gerrit topics.
>>
>> Bill
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>>
>

-- 
Unpaid intern in BillsBasement at noware dot com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20130217/7918562c/attachment.html>


More information about the vtk-developers mailing list