General Guidelines for committing code to SVN |
All of the below guidelines are just suggestions. They are not meant to create additional "red tape" during the normal development process. If you find they are getting in the way, let us know, we can always change them! Development processes and best practices change over time, and these guidelines should be no different. |
By "Trunk" we are not only referring to /dspace/trunk in SVN. We're also referring to the "Trunk" of any other production-quality, out-of-the-box modules within SVN. |
The SVN Trunk is one of the few places that needs to remain well managed. As many committers work out of it on an almost daily basis, it can be detrimental to us all if incomplete or extremely buggy code is committed. Obviously, mistakes happen (and we've all made them), so don't worry if you accidentally commit something you didn't mean to (just try to roll it back as soon as you notice it). Here are the few rules we try to follow when committing code to Trunk: