Only Check In Your Code When You Are Ready to Share It

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

Only check your updated code into source control when it is fully unit-tested and ready to share with the rest of the team. Use shelvesets for intermediate work that is not yet complete.

When you check in your code, it will be used as part of your next scheduled build. Any incomplete code is likely to cause build instability. Also when you check in your code, any other developer who does a get latest operation will pick up your changes. If they are incomplete or inadequately tested, they will cause problems for your colleague.

Additional Resources

Last edited Jul 26, 2007 at 10:27 AM by prashantbansode, version 3

Comments

No comments yet.