Commit One Change At A Time

Each check-in should represent a single logical change: either a single bug fix or feature enhancement. Developers who routinely check-in once an hour, day, or week should be put out to pasture or moved to the “research” department where they can't hurt you.

Conversely, if a change takes a week or a month to complete, don't check it in mid-way; that's likely to break the trunk and you don't want to do that. Wait till the change is complete, and then check it in. If that makes you nervous, make sure your backups are working.

---

Social Bookmark this page: