The process of controlling, maintaining, and documenting maintenance and updates to computer software programs.
Version control (typically implemented via a selected software package and IT management procedures) is a critical component of team software and Web site development, preventing users from accidental file loss, allowing access to previous versions, branching, merging and the managing of releases, and audit trail capabilities. (Also see SourceSafe).
Referred to as the VCRM installed on a Windows system for Windows and Linux Proliant systems, and Software Distributor on HP-UX operating systems. Provides an overview of the software status for all managed ProLiant or Integrity systems and can update system software and firmware on those systems programmatically using predetermined criteria. Version control identifies systems that are running out-of-date system software, indicates if an upgrade is available, and provides reasons for upgrading. For HP-UX systems, Software Distributor can be launched from an HP SIM CMS against one or more installed HP-UX systems.
The tracking of each revision and variant of every file managed by an SCM system
A process whereby a librarian keeps track of changes made to programs. This allows recovery of prior versions of the programs in the event that new versions cause unexpected problems.
When enabled, creates a new copy of an item in the database when the user updates the item and clicks the Add as New Version button in the Item Manager.
The COSA version control makes sure that you can always retrieve the number of existing versions, when objects were changed, what was changed, and so on.
The mechanism to ensure that changes to software are introduced in a controlled manner. A small company may have several PC's containing different versions of a particular piece of software. Version control needs to be adopted so that it is clear which version resides on each PC.
Version control is the process of storing and tracking the various changes (revisions) to one or more files. A version control system maintains the revision history generated as the files evolve into their final forms. The main advantage of using an automated version control system is a fast, easy recall of previous revisions. StarTeam also tracks revisions of change requests, tasks, and topics.
The process by which the contents of each revision of software, hardware, or documentation are accounted for.
Version control systems keep track of multiple versions of a source file. They provide a more powerful alternative to keeping backup files (q.v.). See section M.7 Version Control.
Version control combines procedures and tools to manage different versions of source documents, are created during the software development process. Version control is the process of managing source documents to ensure that previous revisions of source documents are available if required. It also ensures that all documents released as part of one publication, or all source files used to create an application are grouped together using a feature called labelling.
Version control allows you to manage the lifecycle of a document from conception to final copy, with the ability to roll back versions and track usage within all versions. Only one person at a time can check out a document or file from the library, although people can access the current version and get a copy of the latest version if required. Once this person updates the document and checks it back in, a new version is created.
A mechanism to help system engineers handle the problem of a system going into a production (live) state and then moving on to a second or subsequent development state. Version control is a facility that includes the capability of changing the state of a version of an application, archiving a version and creating new versions.
controlling access to computer files to make certain that all additions and edits are made on current files and that back-up files and historic copies made during the project are not confused with or mistaken for current files. There should be only one copy of each current file available for editing. Back-up copies should be kept separately and/or labeled in ways that prevent confusion.
Version control systems keep track of multiple versions of a document or record, tracking each variant or revision.