To facilitate upgrades, minimum package versions were introduced. When installing a package, dependency resolution was used to automatically calculate the packages needed as well, and install them with the desired package. From 1994 on this idea was reverted, so a package that knew the packages it needed. Debian's first try was that a package knew other packages which depended on it. Linux distributions like Debian, with its dpkg, early on created package management software which could resolve dependencies between their packages. Later lists of files including their versions were added, and dependencies amongst them. For computer files this practice was introduced for the first time with MIT's ITS file system, later the TENEX filesystem for the PDP-10 in 1972. Modern computer software is often tracked using two different software versioning schemes: an internal version number that may be incremented many times in a single day, such as a revision control number, and a release version that typically changes far less often, such as semantic versioning or a project code name.įile numbers were used especially in public administration, as well as companies, to uniquely identify files or cases. At a fine-grained level, revision control is used for keeping track of incrementally-different versions of information, whether or not this information is computer software, in order to be able to roll any changes back. Within a given version number category (e.g., major or minor), these numbers are generally assigned in increasing order and correspond to new developments in the software.

Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software. For versioning of other products, see Mark (designation).

Free for ios instal OfficeRTool 8.7