Source Control Etiquette :: Tip o' The Day

Some more quick best practices for using source control.

Simple Rule:  Check in often, build often, and keep updated as frequently as you have code that builds.  This prevents merge conflicts, overrides, and other goofy nonsense that no one wants to deal with.

I would say it is a good idea to update every time a new successful build occurs on the build server.

Commit (check in) every time new working code is completed.  This should be every 30 minutes to an hour.  If not, you’re probably working through tasks that are too big at one time and the tasks need to be broken down further.  This is also a sign that TDD is not being followed closely (or at all).  Even if test after is the process, tasks should be 30 minutes to an hour, and should be committed accordingly back to the repository.

Technorati Tags: , Tags: ,