Software versioning

Software versioning is the process of assigning unique version names or unique version numbers to unique states of computer software.

Uses your system voice; voice and rate in settings.

≈ 19 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Software versioning is the process of assigning unique version names or unique version numbers to unique states of computer software. A commonly adopted scheme for version numbers is known as semantic versioning (SemVer), which comprises a three-part version number (Major.Minor.Patch), an optional prerelease tag (e.g. alpha, beta), and an optional build meta tag.

A fourth number may also be used to denote the software build, as was the case for Adobe Flash. Some companies also rely on the build date, in a system known as calendar versioning, and letters and other characters, such as Lotus 1-2-3 Release 1a.

Most free and open-source software packages, including MediaWiki, treat versions as a series of individual numbers, separated by periods, with a progression such as 1.8.1, 1.9.0. On the other hand, some software packages identify releases by decimal numbers: 1.8, 1.81, 1.82.

Developers may choose to jump multiple minor versions at a time to indicate that significant features have been added or for marketing purposes. Version numbers are often used to identify copies of a software product and compare them against another copy in a collaborative version control system.

Within software development teams, version control is used to keep track of incrementally-different versions of information in order to be able to roll any changes back. Modern computer software is often tracked using two different software versioning schemes: an internal version number, which may be incremented many times in a single day, and a release version, which typically changes far less often.

Historically, file numbers were especially used in public administration and corporations to uniquely identify files or cases. This practice was introduced to computer files for the first time with MIT's ITS file system, later the TENEX file system for the PDP-10 in 1972.

In the 21st century, more programmers started to use a standardized version policy, such as the semantic versioning policy, which is particularly useful when using software libraries, frameworks, and command-line applications.

History

File numbers were used especially in public administration, as well as companies, to uniquely identify files or cases. 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. Later lists of files including their versions were added, and dependencies amongst them.

Linux distributions like Debian, with its dpkg, early on created package management software which could resolve dependencies between their packages. Debian's first try was that a package knew other packages which depended on it. From 1994 on this idea was inverted, so a package that knew the packages it needed.

When installing a package, dependency resolution was used to automatically calculate the packages needed as well, and install them with the desired package. To facilitate upgrades, minimum package versions were introduced. Thus the numbering scheme needed to tell which version was newer than the required one.

Based on sequence identifiers

In sequence-based software versioning schemes, each software release is assigned a unique identifier that consists of one or more sequences of numbers or letters. This is the extent of the commonality; schemes vary widely in areas such as the number of sequences, the attribution of meaning to individual sequences, and the means of incrementing the sequences.

Based on date of release identifiers

showing release number in CalVer format: "961219 USA"]] Many projects use a date-based versioning scheme called Calendar Versioning (aka CalVer ). Ubuntu is one example of a project using calendar versioning; Ubuntu 18.04, for example, was released in April 20181. This has the advantage of being easily relatable to development schedules and support timelines.

Some video games also use date as versioning, for example the arcade game Street Fighter EX. At startup it displays the version number as a date plus a region code, for example 961219 ASIA. When using dates in versioning, for instance, file names, it is common to use the ISO 8601 scheme YYYY-MM-DD, as this is easily string-sorted in increasing or decreasing order.

The hyphens are sometimes omitted. The Wine project formerly used a date versioning scheme, which used the year followed by the month followed by the day of the release; for example, "Wine 20040505". The earliest development builds of Minecraft had a similar version formatting, but instead used DDHHMM, for example rd-131655 was created on the 13th (of May 2009) at 16:21.

Microsoft Office build numbers are an encoded date: the first two digits indicate the number of months that have passed from the January of the year in which the project started (with each major Office release being a different project), while the last two digits indicate the day of that month. So 3419 is the 19th day of the 34th month after the month of January of the year the project started.

Other examples that identify versions by year include Adobe Illustrator 88 and WordPerfect Office 2003. When a year is used to denote version, it is generally for marketing purposes, and an actual version number also exists. For example, Windows 95 is internally versioned as MS-DOS 7.00 and Windows 4.00; likewise, Windows 2000 is internally versioned as NT 5.0.

Prerelease versions

In conjunction with the various versioning schemes listed above, a system for denoting prerelease versions is generally used, as the program makes its way through the stages of the software release life cycle. Programs that are in an early stage are often called "alpha" software, after the first letter in the Greek alphabet.

After they mature but are not yet ready for release, they may be called "beta" software, after the second letter in the Greek alphabet. Generally alpha software is tested by developers only, while beta software is distributed for community testing. Some systems use numerical versions less than 1 (such as 0.9), to suggest their approach toward a final "1.0" release.

This is a common convention in open source software. However, if the prerelease version is for an existing software package (e.g. version 2.5), then an "a" or "alpha" may be appended to the version number.

So the alpha version of the 2.5 release might be identified as 2.5a or 2.5.a. An alternative is to refer to prerelease versions as "release candidates", so that software packages which are soon to be released as a particular version may carry that version tag followed by "rc-#", indicating the number of the release candidate; when the final version is released, the "rc" tag is removed.

Release train

A software release train is a form of software release schedule in which a number of distinct series of versioned software releases for multiple products are released as a number of different "trains" on a regular schedule. Generally, for each product line, a number of different release trains are running at a given time, with each train moving from initial release to eventual maturity and retirement on a planned schedule.

Users may experiment with a newer release train before adopting it for production, allowing them to experiment with newer, "raw", releases early, while continuing to follow the previous train's point releases for their production systems prior to moving to the new release train as it becomes mature. Cisco's IOS software platform used a release train schedule with many distinct trains for many years.

More recently, a number of other platforms including Firefox and Fenix for Android, Eclipse, LibreOffice, Ubuntu, Fedora, Python, digiKam and VMware have adopted the release train model.

Internal version numbers

Software may have an "internal" version number which differs from the version number shown in the product name (and which typically follows version numbering rules more consistently). Java SE 5.0, for example, has the internal version number of 1.5.0, and versions of Windows from NT 4 on have continued the standard numerical versions internally: Windows 2000 is NT 5.0, XP is Windows NT 5.1, Windows Server 2003 and Windows XP Professional x64 Edition are NT 5.2, Windows Server 2008 and Vista are NT 6.0, Windows Server 2008 R2 and Windows 7 are NT 6.1, Windows Server 2012 and Windows 8 are NT 6.2, and Windows Server 2012 R2 and Windows 8.1 are NT 6.3.

Windows 10 was initially intended to be NT 6.4, as the earliest Technical Preview build shared to the public is numbered 6.4.9841. However, that did not last as the version of Windows 10 was quickly artificially increased to 10.0 to align with the commercial name, resulting in the first released version of the operating system being numbered 10.0.10240.

Note, however, that Windows NT is only on its fifth major revision, as its first release was numbered 3.1 (to match the then-current Windows release number) and the Windows 10 launching made a version leap from 6.3 to 10.0.

Marketing

A relatively common practice is to make major jumps in version numbers for marketing reasons. Sometimes software vendors just bypass the 1.0 release or quickly release a release with a subsequent version number because 1.0 software is considered by many customers too immature to trust with production deployments.

For example, as in the case of dBase II, a product is launched with a version number that implies that it is more mature than it is. Other times version numbers are increased to match those of competitors. This can be seen in many examples of product version numbering by Microsoft, America Online, Sun Solaris, Java Virtual Machine, SCO Unix, WordPerfect.

Microsoft Access jumped from version 2.0 to version 7.0, to match the version number of Microsoft Word. Microsoft has also been the target of "catch-up" versioning, with the Netscape browsers skipping version 5 to 6, in line with Microsoft's Internet Explorer, but also because the Mozilla application suite inherited version 5 in its user agent string during pre-1.0 development and Netscape 6.x was built upon Mozilla's code base.

Another example of keeping up with competitors is when Slackware Linux jumped from version 4 to version 7 in 1999. This approach, panned by many because it breaks the semantic significance of the sections of the version number, has been adopted by an increasing number of vendors including Mozilla (for Firefox) and Google (for Google Chrome).

Promoting minor as major

Sun's Java has at times had a hybrid system, where the internal version number has always been 1.x but has been marketed by reference only to the x: JDK 1.0.3 JDK 1.1.2 through 1.1.8 J2SE 1.2.0 ("Java 2") through 1.4.2 Java 1.5.0, 1.6.0, 1.7.0, 1.8.0 ("Java 5, 6, 7, 8") Sun also dropped the first digit for Solaris, where Solaris 2.8 (or 2.9) is referred to as Solaris 8 (or 9) in marketing materials. A similar jump took place with the Asterisk open-source PBX construction kit in the early 2010s, whose project leads announced that the current version 1.8.x would soon be followed by version 10.

Version 1.0 as a milestone

The free-software and open source communities tend to release software early and often. Initial versions are numbers less than 1, with these 0.x version used to convey that the software is incomplete and not reliable enough for general release or usable in its current state. Backward-incompatible changes are common with 0.x versions.

Version 1.0 is used as a major milestone, indicating that the software has at least all major features plus functions the developers wanted to get into that version, and is considered reliable enough for general release. A good example of this is the Linux kernel, which was first released as version 0.01 in 19911, and took until 1994 to reach version 1.0.0.

The developers of the arcade game emulator MAME do not ever intend to release a version 1.0 of the program because there will always be more arcade games to emulate and thus the project can never be truly completed. Accordingly, version 0.99 was followed by version 0.100.

Superstition

The Office 2007 release of Microsoft Office had an internal version number of 12. The next version, Office 2010, has an internal version of 14, due to superstitions surrounding the number 13. Visual Studio 2013 is Version number 12.0 of the product, and the new version, Visual Studio 2015 has the Version number 14.0 for the same reasons.

Roxio Toast went from version 12 to version 14, likely in an effort to skip the superstitions surrounding the number 13. Corel's WordPerfect Office, version 13 is marketed as "X3" (Roman number 10 and "3"). The procedure has continued into the next version, X4.

The same has happened with Corel's Graphic Suite (i.e. CorelDRAW, Corel Photo-Paint) as well as its video editing software "Video Studio". Sybase skipped major versions 13 and 14 in its Adaptive Server Enterprise relational database product, moving from 12.5 to 15.0. ABBYY Lingvo Dictionary uses numbering 12, x3 (14), x5 (15).

SUSE Linux Enterprise skipped version 13 and 14 after version 12 and directly released SLES 15 in July 2018. In the mid-1990s, the rapidly growing CMMS, Maximo, moved from Maximo Series 3 directly to Series 5, skipping Series 4 due to that number's perceived marketing difficulties in the Chinese market, where the number 4 is associated with "death" (see tetraphobia).

This did not stop Maximo Series 5 version 4.0 from being released. (The "Series" versioning has since been dropped, effectively resetting version numbers after Series 5 version 1.0's release.)

Geek culture

The SUSE Linux distribution started at version 4.2, to reference 42, "the answer to the ultimate question of life, the universe and everything" mentioned in Douglas Adams' The Hitchhiker's Guide to the Galaxy. A Slackware Linux distribution was versioned 13.37, referencing leet.

Finnix skipped from version 93.0 to 100, partly to fulfill the assertion, "There Will Be No Finnix '95", a reference to Windows 95. The Tagged Image File Format specification has used 42 as internal version number since its inception, its designers not expecting to alter it anymore during their (or its) lifetime since it would conflict with its development directives.

Python

The Python Software Foundation has published PEP 440 – Version Identification and Dependency Specification, outlining their own flexible scheme, that defines an epoch segment, a release segment, prerelease and post-release segments and a development release segment.

TeX

TeX has an idiosyncratic version numbering system, an unusual feature invented by its developer Donald Knuth. Since version 3.1, updates have been indicated by adding an extra digit at the end, so that the version number asymptotically approaches the number , so 3.14 effectively means 3.2 in semantic versioning.

(This is a form of unary numbering; the version number is the number of digits.) Since 20211, the version number has been 3.141592653. This is a reflection of TeX being very stable, and only minor updates are anticipated.

TeX developer Donald Knuth has stated that the "absolutely final change (to be made after [his] death)" will be to change the version number to , at which point all remaining bugs will become permanent features. In a similar way, the version number of Metafont asymptotically approaches Euler's number, . As of February 2021, the version number is 2.71828182.

Metafont was also devised by Donald Knuth as a companion to his TeX typesetting system.

Apple

During the era of the classic Mac OS, minor version numbers rarely went beyond ".1". When they did, they usually jumped straight to ".5", suggesting the release was "more significant". Thus, "8.5" was marketed as its own release, representing "Mac OS 8 and a half", and 8.6 effectively meant "8.5.1".

Mac OS X departed from this trend, in large part because "X" (the Roman numeral for 10) was in the name of the product. As a result, all versions of OS X began with the number 10. The first major release of OS X was given the version number 10.0, but the next major release was not 11.0.

Instead, it was numbered 10.1, followed by 10.2, 10.3, and so on for each subsequent major release. Thus the 11th major version of OS X was labeled "10.10". Even though the "X" was dropped from the name as of macOS 10.12, this numbering scheme continued through macOS 10.15.

Under the "X"-based versioning scheme, the third number (instead of the second) denoted a minor release, and additional updates below this level, as well as updates to a given major version of OS X coming after the release of a new major version, were titled Supplemental Updates. The Roman numeral X was concurrently leveraged for marketing purposes across multiple product lines.

Both QuickTime and Final Cut Pro jumped from version 7 directly to version 10, QuickTime X and Final Cut Pro X. Like Mac OS X itself, the products were not upgrades to previous versions, but brand-new programs. As with OS X, major releases for these programs incremented the second digit and minor releases were denoted using a third digit.

The "X" was dropped from Final Cut's name with the release of macOS 11.0 (see below), and QuickTime's branding became moot when the framework was deprecated in favor of AVFoundation in 2011 (the program for playing QuickTime video was only named QuickTime Player from the start). Apple's next macOS release, provisionally numbered 10.16, was officially announced as macOS 11 at WWDC in June 20201, and released in November 2020.

The following macOS version, macOS Monterey, was released in October 2021 and bumped its major version number to 12. In June 20251, Apple announced an unified versioning scheme, using the year next to the release date, similar to model years in vehicles. The versions that were released in the fall of 2025 are iOS 26, macOS 26, iPadOS 26, tvOS 26, watchOS 26 and visionOS 26.

Microsoft Windows

The Microsoft Windows operating system was first labelled with standard version numbers for Windows 1.01 through Windows 3.2. After this Microsoft excluded the version number from the product name. For Windows 95 (version 4.0), Windows 98 (4.10) and Windows 2000 (5.0), year of the release was included in the product title.

After Windows 2000, Microsoft created the Windows Server family which continued the year-based style with a difference: For minor releases, Microsoft suffixed "R2" to the title, e.g., Windows Server 2008 R2 (version 6.1). This style had remained consistent to this date. The client versions of Windows however did not adopt a consistent style.

First, they received names with arbitrary alphanumeric suffixes as with Windows Me (4.90), Windows XP (5.1), and Windows Vista (6.0). Then, once again Microsoft adopted incremental numbers in the title, but this time, they were not versioning numbers; the version numbers of Windows 7, Windows 8 and Windows 8.1 are respectively 6.1, 6.2 and 6.3.

In Windows 10, the version number leaped to 10.0 and subsequent updates to the OS only incremented build number (which is date-based) and update build revision (UBR) number. The successor of Windows 10, Windows 11, was released on October 5, 2021. Despite being named "11", the new Windows release did not bump its major version number to 11.

Instead, it stayed at the same version number of 10.0, used by Windows 10.

Non-software use

Some computer file systems, such as the OpenVMS Filesystem, also keep versions for files. Versioning amongst documents is relatively similar to the routine used with computers and software engineering, where with each small change in the structure, contents, or conditions, the version number is incremented by 1, or a smaller or larger value, again depending on the personal preference of the author and the size or importance of changes made.

Technical drawing and CAD software files may also use some kind of primitive versioning number to keep track of changes.

See also

Continuous Data Protection Maintenance release Product life cycle management Release management Release notes Software engineering

Document Foundation release plan for LibreOffice, showing release trains

Text derived from https://en.wikipedia.org/w/index.php?oldid=1376666112 under CC BY-SA 4.0; modifications have been made.

Words in each sectionMarketingMarketingMarketing: 944 words944Prerelease versionsPrerelease versionsPrerelease versions: 644 words644AppleAppleApple: 456 words456Based on date of releas…Based on date of release identifiersBased on date of release identifiers: 317 words317Microsoft WindowsMicrosoft WindowsMicrosoft Windows: 251 words251TeXTeXTeX: 168 words168HistoryHistoryHistory: 156 words156Non-software useNon-software useNon-software use: 90 words90Based on sequence ident…Based on sequence identifiersBased on sequence identifiers: 56 words56PythonPythonPython: 35 words35See alsoSee alsoSee also: 15 words15
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

References

1 claim could not be tied to a specific sentence and is listed in the table below instead.

  1. ↩Wikipedia “Software versioning” revision 1376666112 · retrieved 2026-10-20 release date (×6) · confidence 0.95 revision URL

Provenance

snapshot enwiki-001376666112 · captured 2026-09-25 · ledger · version history

Cite this page as: encyclopegia.org, “Software versioning”, snapshot enwiki-001376666112. https://encyclopegia.org/a/software-versioning