[vtk-developers] Developer guidlines required

[Will Schroeder]

Hi Prabhu-

1) Communication is an exceptionally good thing. Communication is to be 
encouraged. There's not enough as it is.

2) ENH: enhancement; ERR: error. Some people use :BUG: for error. The idea 
is to keep track of bugs versus enhancements. As far as the log goes: 
again, more information is better, especially if the changes are more 
complex and not just a simple fix or addition. It hels those not involved 
with the change keep track of what's going on.

3) I normally have 2-3 different vtk builds going. In each build I'm 
working on something else. I check the files in from the build when I'm 
ready. You've got to keep track of what not to check in.

4) Which OS and graphics hardware? I'm thinking about 1-2 hours.

5) I use the RTest.tcl script in vtk/examplesTcl for smaller changes. It 
has a facility to run all examples with a particular class name. If you 
change a core API (like vtkDataSet or vtkDataArray), I run all the tests.

6) When I'm testing multiple versions I set my LD_LIBRARY_PATH as appropriate.

7) It's extra work to version the libraries. No one has volunteered 
;-)  Also, is it really useful?

Will