Change sets versus change packages: Comparing implementations of change-based SCM
Tracking logical software changes rather than individual file changes is an emerging technology in SCM systems today. Such a tight coupling of SCM and change management has the potential to evolutionize software configuration management as we know it. Two different styles of change-based SCM have emerged, known as “change sets” and “change packages.” The goal of both types of systems is the same: to help software teams manage their software and related artifacts in order to ship quality products on time. However, it is interesting to consider which type of system is more effective at helping software teams manage their configurations.
KeywordsCommon Ancestor Logical Change Code Change Binary File Individual File
Unable to display preview. Download preview PDF.
- Martin Cagan and Darcy Wiborg-Weber. Task-Based Software Configuration Management: Support for “Change Sets” in Continuus/CM, 1996.Google Scholar
- Continuus Software Corporation. Task-Based CM, 1996.Google Scholar
- Continuus Software Corporation. Command Reference, 1996.Google Scholar
- Ovum Ltd. Ovum Evaluates: Configuration Management, 1996.Google Scholar
- Ovum Ltd. Ovum Evaluates: Configuration Management, 1995.Google Scholar
- Software Maintenance & Development Systems, Inc. Aide-de-Camp Product Overview, 1995.Google Scholar
- Peter H. Feiler. Configuration management models in commercial environments. Technical Report SEI-91-TR-7, Software Engineering Institute, Carnegie Mellon University, 1991.Google Scholar
- Richard Harter. News discussion of change sets, Aide-de-Camp internals, and binary file handling entitled “Re: Aide-de-Camp: Info needed” in comp.software.config-mgmt newsgroup. January 22, 1995.Google Scholar