[vtk-developers] VTK code review / testing / integration workflow

[Bill Lorensen]

BTW the new gerrit UI is a bit prettier:
https://android-review.googlesource.com/#/q/status:open

I'm a little concerned that we spend too much time on process and not
enough time on improving VTK. But, I'll go with the consensus of the
people who still work for a living. If the new process is too
difficult for an old guy like me, I'll just spend my extra time with
ITK.

Bill


On Mon, Aug 25, 2014 at 4:45 PM, Sean McBride <sean at rogue-research.com> wrote:
> On Mon, 25 Aug 2014 15:50:59 -0400, David Cole via vtk-developers said:
>
>>A fantasy feature for me would be that the system injects a step
>>1.5/2.5 in the developer workflow, and automatically chooses 3-5
>>reviewers for you based on reviewers "signing up" for reviewing certain
>>modules, or perhaps based on recent-ish commits in the same files...
>
> That would be a great addition.  I often don't know who to add as a reviewer, and I've been tinkering with VTK for years.  Imagine a newbie!  A person can use 'git log' and 'git blame' to get some guesses, and that could be automated.  Of course, sometimes that results in suggesting someone no longer involved with VTK or the infamous 'VTK developers', but still it would help to automate it.
>
> Cheers,
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 sean at rogue-research.com
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec, Canada
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/vtk-developers
>



-- 
Unpaid intern in BillsBasement at noware dot com