XP Home

Integrate Often

Lessons Learned

 Developers should be integrating and releasing code into the code repository every few hours, when ever possible. In any case never hold onto changes for more than a day. Continuous integration often avoids diverging or fragmented development efforts, where developers are not communicating with each other about what can be re-used, or what could be shared. Everyone needs to work with the latest version. Changes should not be made to obsolete code causing integration head aches.
 Almost continuous integration avoids or detects compatibility problems early. Integration is a "pay me now or pay me more later" kind of activity. That is, if you integrate through out the project in small amounts you will not find your self


trying to integrate the system for weeks at the project's end while the deadline slips by. Always work in the context of the latest version of the system. Collective Ownership

Portland Pattern RepositoryXProgramming.comPortland Pattern Repository

ExtremeProgramming.org home | XP Rules | Collective Code Ownership | Email the webmaster

Copyright 1997, 1999 J. Donovan Wells all rights reserved.