VTK/Commit Guidelines: Difference between revisions
From KitwarePublic
< VTK
Jump to navigationJump to search
David.cole (talk | contribs) mNo edit summary |
David.cole (talk | contribs) |
||
| Line 1: | Line 1: | ||
* Follow the [[VTK Coding Standards]] when writing new code or modifying existing code | * Follow the [[VTK Coding Standards]] when writing new code or modifying existing code | ||
| Line 6: | Line 4: | ||
* Run ctest in your binary directory and make sure all the VTK tests pass before committing your code | * 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 | |||
Revision as of 16:58, 9 October 2006
- 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
