From KitwarePublic
Revision as of 17:49, 30 July 2010 by Hjmjohnson (talk | contribs) (New page that helps describes best practices of how to identify, workon, and commit changes to ITK.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Best practices process for contributing to ITK.

Bugs/Feature enhancements best practices guide

  1. Determine if the contribution is already listed in the bug tracker:
  2. Add proposed contribution (if necessary) and assign it to yourself (NOTE THE BUG ID link i.e. 0011074)
  3. Create a new branch called "BUG0011074" from the updated git ITK master branch
  4. Make proposed changes on branch "BUG0011074", thoroughly test changes, submit dashboard indicating (NOTE THE DASHBOARD link )
  5. Merge BUG0011074 branch into master, commit changes with a comment that includes both the BUGID and link to dashboard indicating that the contribution introduces no new errors.
  6. Close the Mantis issue, and include the commit hash key as a comment when closing.


To update the ITK version number, the follow process could be followed:

Create a Mantis issue stating what you want to accomplish: [1] Assign issue to yourself.

git fetch origin
git checkout master
git branch BUG0011074
git checkout BUG0011074
vim CMakeLists.txt   # Edit to change the version number
git add CMakeLists.txt
git commit
git checkout master
git merge BUG0011074
git push origin
git branch -d BUG0011074

Close the Mantis issue with reference to the commit hash key.