[vtk-developers] Starting out

[Dean Inglis]

Prabhu,

Thanks for your help...

> AFAIK one can simply make changes on the checked out CVS tree, build
> everything, test them and then commit the changes to CVS.

According to today's dashboard it appears I did this right yesterday.  

>  Finally
> make an announcement about the changes that were made.  If necessary
> add a new test for the new class or feature.  Once you commit the
> changes take a look at the dashboard and make sure that your changes
> did not trigger an error somewhere.  Sometimes errors might not show
> up on the OS where you build and develop and another platform/OS can
> have trouble.  Checking out the dashboard helps with this.
> 
> If someone else is also likely to make changes it makes sense to
> announce what you plan to do on the devel list in order to prevent
> conflicts.
> 

In future will do.

> If the changes you are about to make are very extensive it might help
> to keep a backup of the older files.  You could use CVS to retrieve
> older versions but I find that it helps having a local copy of
> unmodified files.
> 
> Hope this helps.
> prabhu