Talk:Software configuration management

message: There exists also another "SCM": source code management, which looks similar to this concept (at least, the examples like BitKeeper, Mercurial suggest that these two things are similar). Could someone explicitly state what difference is meant by these different terms?--Imz (talk) 16:41, 26 May 2008 (UTC)
replies: text: Added to the article. -- Beland (talk) 18:56, 3 April 2013 (UTC)
thread_title:  difference from "source code management" 

message: what means Free Open Source Software vendor? advisability to put license here (bsd-style, apache-style, gpl, etc..)  —Preceding unsigned comment added by 213.87.86.55 (talk) 15:16, 21 June 2008 (UTC)
thread_title:  vendors 

message: The introductory paragraph is misleading.  It implies that SCM is only about tracking changes over time (which is the province of revision control).  It is more about how to create different configurations of software - for example, for different client requirements.  Part of that is being able to create earlier versions but that is just one aspect.
AndrewWPhillips (talk) 02:18, 26 November 2010 (UTC)
thread_title:  Software Configuration Management is more than version control 

message: I agree with Andrew's direction and want to go deeper. This is about management of Configurable Items (Components) in Configurations. Initially it was for Hardware as in cars and airplanes. Then in Data Center IT Configurable Items. And finally in Software Components. Not all software is constructed to be configurable. Windows platform is a good example of configurable software. Configurable by Microsoft, not by the users. Configurable as in a production line. Tools to support Software-CM must be able to handle a structure of configurable (software) components and based on features, functions, requirements, specifications be able to render an executable configuration.
186.204.87.146 (talk) 02:24, 27 March 2012 (UTC)
thread_title:  This subject is about Configuration 

message: There is a move discussion in progress on Template talk:IEEE software documents which affects this page. Please participate on that page and not in this talk page section. Thank you.  —RMCD bot 22:02, 15 June 2020 (UTC)
thread_title:  Move discussion in progress 

message: There is a move discussion in progress on Template talk:IEEE software documents which affects this page. Please participate on that page and not in this talk page section. Thank you.  —RMCD bot 23:32, 15 June 2020 (UTC)
thread_title:  Move discussion in progress 

message: WRT current text: With the introduction of cloud computing and DevOps the purposes of SCM tools have become merged in some cases. The SCM tools themselves have become virtual appliances that can be instantiated as virtual machines and saved with state and version. The tools can model and manage cloud-based virtual resources, including virtual appliances, storage units, and software bundles. The roles and responsibilities of the actors have become merged as well with developers now being able to dynamically instantiate virtual servers and related resources
In short: huh? 
SCM tools have become merged: what tools?; merged with what? in some cases?
SCM tools themselves have become virtual appliances: what is a virtual appliance?
tools ... can be instantiated as virtual machines:? they can?
roles and responsibilities of the actors have become merged: what's an actor? what roles? what responsibilities?
developers now being able to dynamically instantiate virtual servers and related resources: what does this have to do with SCM????? Stevebroshar (talk) 19:01, 31 May 2024 (UTC)
thread_title:  Goals? purpose?