[vtk-developers] Commiting stuff

[Bill Lorensen]

Use VTK (vtknew is the same). vtk is pretty much frozen.

The old continuous is a shadow tree that links onto the new tree. Your changes should appear on the old continuous if they are changes to files that existed in the old vtk.

Bill

At 11:02 PM 8/29/01 +0100, John Biddiscombe wrote:
>I'm slightly behind speed on the changeover to VTK.
>
>I've just committed some changes to VTK (not vtk) and can't see anything on any dashboards or contuinuous build pages. Can anyone tell me
>
>a) where to look to check I've not buggered up the system. Continuous and nightly
>
>Nightly seems to be here...
>http://public.kitware.com/vtkhtml/Testing/HTML/TestingResults/Dashboard/MostRecentResults-Nightly/Dashboard.html
>
>is this continuous link any use?
>http://www.visualizationtoolkit.org/vtk/quality/ContinuousResults/solaris/ContinuousResults.html
>
>
>b) answer these quick questions, just to make sure I understand what's going on...
>
>vtknew is now VTK - are they identical. Can I simply edit all my cvs/repository files to have VTK now. (NB, I've done this and it seems to be working, subject to reservations above).
>
>When checking in stuff, should I avoid vtk altogether and use VTK only (or vtknew?)
>
>Thanks
>
>JB.
>PS. Is it too early for me to consider setting up DART to build with Borland continuously and also test some of my own classes?
>
>
>_______________________________________________
>vtk-developers mailing list
>vtk-developers at public.kitware.com
>http://public.kitware.com/mailman/listinfo/vtk-developers