History of software configuration management

The history of software configuration management (SCM) in computing can be traced back as early as the 1950s, when CM (for Configuration Management), originally for hardware development and production control, was being applied to software development. The first software configuration management was most likely done manually. Eventually, software tools were written to manage software changes. History records tend to be based on tools and companies, and lend concepts to a secondary plane.

Timeline
  • Early 1960s or even late 1950s: CDC UPDATE and IBM IEB_UPDATE.[1]
  • Late 1960s, early 1970s: Professor Leon Pressor at the University of California, Santa Barbara produced a thesis on change and configuration control. This concept was a response to a contract he was working on with a defense contractor who made aircraft engines for the US Navy.
  • Early 1970s: Unix make.
  • By 1970 CDC update was an advanced product.
  • Circa 1972: Bell Labs paper describing the original diff algorithm.
  • 1972, with an IEEE paper in 1975: source code control system, SCCS, Marc Rochkind Bell Labs. Originally programmed in SNOBOL for OS/360; subsequently rewritten in C for Unix (used diff for comparing files).
  • 1970s: Lisle, Illinois-based Pansophic Systems offered PANVALET, which was an early source code control system for the mainframe market.[2]
  • 1975: Professor Pressor's work eventually grew into a commercially available product called Change and Configuration Control (CCC) which was sold by the SoftTool corporation.
  • Revision Control System (RCS, Walter Tichy).
  • Early 1980s: patch (around 1985, Larry Wall).
  • 1984: Aide-de-Camp
  • 1986: Concurrent Version System (CVS).
  • 2000: Subversion initiated by CollabNet.
  • Early 2000s (decade): distributed revision control systems like BitKeeper and GNU arch become viable.

Background

Until the 1980s, SCM could only be understood as CM applied to software development.[3] Some basic concepts such as identification and baseline (well-defined point in the evolution of a project) were already clear, but what was at stake was a set of techniques oriented towards the control of the activity, and using formal processes, documents, request forms, control boards etc.

It is only after this date that the use of software tools applying directly to software artefacts representing the actual resources, has allowed SCM to grow as an autonomous entity (from traditional CM).

The use of different tools has actually led to very distinct emphases.

  • traditional CM for Software, typically around Change Management (examples: Continuus, CVS or ClearCase UCM)
  • line oriented management, based on patches or Change Sets
  • focused on Derived Objects and Build Management (example: Base ClearCase/clearmake)
gollark: hd!jsk py builtins()["sorted"] = lambda x: x
gollark: S
gollark: Ye
gollark: See, I was right as always.
gollark: hd!selfdestruct

See also
  • Revision control

References
  1. http://www.daveeaton.com/scm/CMFAQ.html
  2. Oral history interview with Joseph Piscopo, Charles Babbage Institute, University of Minnesota. Piscopo founded Pansophic Systems in 1969 and led it until his retirement in 1987. Interview discusses the development of Panvalet and the acquisition of Easytrieve.
  3. J.K. Buckle (1982). Software Configuration Management. ISBN 0-333-30719-4.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.