VTK/Commit Guidelines

• Follow the VTK Coding Standards when writing new code or modifying existing code

• Build into a fresh empty binary directory after making your last code change

• Run ctest in your binary directory and make sure all the VTK tests pass before committing your code

• Commit your changes as early in the day as possible

• Commit the entire tree in one call to cvs commit

• Observe the continuous dashboards for the remainder of the day after your commit

• Observe the nightly dashboards the day following your commit

• Fix any warnings, errors or test failures related to your commit as soon as possible after becoming aware of them