| Version 3 (modified by jdalbey, 7 years ago) (diff) |
|---|
Always SVN Update before SVN Commit. Always.
Failure to do this will likely result in code conflicts that are very time consuming to resolve.
Don't hoard code. Update and commit often.
Write a thoughtful commit message
The message should begin with the file(s) being committed.
Describe what was changed, why it was changed, and a cross-reference to any relevant ticket number.
