[vtk-developers] Dashboard

[Will Schroeder]

I fully endorse Ken's efforts in cleaning up the dashboard, especially as 
we head towards a VTK 5.0 release. One strategy I've been using to check in 
new code (especially code that is likely to cause problems) is to call on a 
"dashboard buddy". The buddy's job is to help cover my butt in case I get 
distracted with administrivia, or there are problems that I need help with. 
For example, Dave Cole and Brad King helped me with the widgets check in 
and the modification to the CMakeLists.txt files. The key, besides the 
usual good protocol of checking in early to see what the continuous does, 
is to either 1) make sure you have the time to handle any problems the next 
day, or 2) find a buddy before check in with the expectation that you will 
work together once the check in occurs.

Will

At 09:26 AM 7/19/2005, Ken Martin wrote:
>The VTK Dashboard is a disaster. Please everyone take a look at the
>dashboard and fix your issues immediately. If I find that a VTK developer
>has created a dashboard problem (that is reasonably obvious it is their
>problem) and not fixed it within a couple days their write access will be
>removed. These problems prevent other VTK developers from being able to test
>their changes and effectively develop on VTK.
>
>Thanks
>Ken
>
>
>_______________________________________________
>vtk-developers mailing list
>vtk-developers at vtk.org
>http://www.vtk.org/mailman/listinfo/vtk-developers