It is necessary to be able to save intermediate steps in a change in case a coding step results in an error. The mechanism for specifying that a version is ready for integration is primitive, and another developer has access to a version as soon as it is checked it. It is important to make sure that developers using Private Versioning remember to migrate changes to the shared version control system at reasonable intervals. The revision control mechanism could also provide a means for restricting access to checked-in versions that are not yet ready for use by others, and could also provide a mechanism for filtering log messages to eliminate trivial changes. The project repository using CVS for version control.
Some organizations have infrequent integrations which reflect large changes.
For iterative development to work well, it is necessary to make sure that components work together. Subsystems get developed at different rates. Developers work with Independent Development . We need to find a way to make it possible to integrate without surprises. Developers should also be able to build against any of the Named Stable Bases, or the newest checked in software, at will.