Committing Code

From VCGR Wiki

Test your code thoroughly before checking in to the repository and be sure you are testing from a clean build.

A thorough check-in procedure follows. You should always do Steps A-F. If the changes you are making may have platform-based implications, don't forget Steps G and H.

       A)  Update with SVN to get all current files in the repository
       B)  Do a complete build from scratch INCLUDING doing a clean and then a build.
       C)  Start up a new system including bootstrap (with security)
       D)  Run any tests you feel like you should run (make sure commands like ls, cat, and cp still work) 
 (make sure to check logging in as well)
       E)  Repeat step A.  If anything was checked in while you were testing, start over
       F)  Once you can update with NO INCOMING CHANGES from the repository, you may commit
       G)  Immediately after committing, get a machine of the opposite architecture (if you did steps A through F on a windows box, test on a Linux box, if you did them on a Linux box, test them on a Windows box)
       H)  On the opposite architecture machine, repeat steps A through D.