Software release life cycle

A software release life cycle is the sum of the stages of development and maturity for a piece of computer. Cycles range from its initial development to its eventual release, and include updated versions of the released version to help improve software or fix s still present in the software.

Computer users are most likely to be familiar with the beta phase, as software products are sometimes publicly advertised as being beta in order to reduce users' expectations of their reliability.

History
Usage of the "alpha/beta" test terminology originated at IBM. Similar terminologies for IBM's software development were used by people involved with IBM from at least the 1950s (and probably earlier). "A" test was the of a new product before the public announcement. "B" test was the verification before releasing the product to be manufactured. "C" test was the final test before the general availability of the product. As software became a significant part of IBM's offerings, the alpha test terminology was used to denote the pre-announcement test and the beta test was used to show product readiness for general availability. Martin Belsky, a manager on some of IBM's earlier software projects claimed to have invented the terminology. IBM dropped the alpha/beta terminology during the 1960s, but by then it had received fairly wide notice. The usage of "beta test" to refer to testing done by customers was not done in IBM. Rather, IBM used the term "field test".

Pre-alpha
Pre-alpha refers to all activities performed during the software project before formal testing. These activities can include, , , and. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the feature is complete.

Alpha
The alpha phase of the release life cycle is the first phase of (named after the  of the, used as the number 1). In this phase, developers generally test the software using. Additional validation is then performed using or  techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.

Alpha software is not thoroughly tested by the developer before it is released to customers. Alpha software may contain serious errors, and any resulting instability could cause crashes or data loss. Alpha software may not contain all of the features that are planned for the final version. In general, external availability of alpha software is uncommon in proprietary software, while open source software often has publicly available alpha versions. The alpha phase usually ends with a, indicating that no more features will be added to the software. At this time, the software is said to be. A beta test is carried out following at the supplier's site (alpha test) and immediately prior to general release of the software as a product.

Beta
Beta, named after the of the, is the software development phase following alpha. Software in the beta stage is also known as betaware. A Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. Software beta releases can either be public or private, depending on whether they are openly available or only available to a limited audience. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, preview release, prototype, technical preview / technology preview (TP), or early access. Since the introduction of Windows 8, Microsoft has called pre-release software a preview rather than beta. All pre-release builds released through the launched in 2014 are termed "Insider Preview builds". "beta" may also indicate something more like a release candidate, or as a form of time-limited demo, or marketing technique.

Beta testers are people who actively report issues of beta software. They are usually customers or representatives of prospective customers of the organization that develops the software. Beta testers tend to volunteer their services free of charge but often receive versions of the product they test, discounts on the release version, or other incentives.

Perpetual beta
Some software is kept in so-called perpetual beta, where new features are continually added to the software without establishing a final "stable" release. As the Internet has facilitated rapid and inexpensive distribution of software, companies have begun to take a looser approach to use of the word "beta". In February 2005, published an article about the phenomenon of a beta version often staying for years and being used as if it were in production level. It noted that Gmail and, for example, had been in beta for a long time although widely used; Google News did leave beta in January 2006, followed by , including Gmail, in July 2009. This technique may allow a developer to delay offering full support and responsibility for remaining issues.

Open and closed beta
Developers may release either a closed beta also called private beta, or an open beta also called public beta; closed beta versions are released to a restricted group of individuals for a user test by invitation, while open beta testers are from a larger group, or anyone interested. Private beta could be suitable for the software that is capable of delivering value, but is not ready to be used by everyone either due to scaling issues, lack of documentation or still missing vital features. The testers report any bugs that they find, and sometimes suggest additional features they think should be available in the final version. Examples of a major public beta test include the following:
 * Early customers purchased a "pioneer edition" of the WordVision word processor for the IBM PC for $49.95. In 1984, wrote that "in a brilliant marketing coup, Bruce and James Program Publishers managed to get people to pay for the privilege of testing the product."
 * In September 2000 a boxed version of Apple's Mac OS X Public Beta operating system was released.
 * Microsoft's release of community technology previews (CTPs) for Windows Vista, between September 2005 and May 2006.
 * From 2009 to 2011, Minecraft was in public beta.

Open betas serve the dual purpose of demonstrating a product to potential consumers, and testing among an extremely wide user base likely to bring to light obscure errors that a much smaller testing team might not find.

Release candidate
A release candidate (RC), also known as "going silver", is a beta version with potential to be a stable product, which is ready to release unless significant emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bugs. A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities. Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product. Beta testing is conducted in a client's or customer's location and to test the software from a user's perspective.

Stable release
Also called production release, the stable release is the last release candidate (RC) which has passed all verifications / tests. The remaining bugs are considered as acceptable. This release goes to production. Some domains (for example, Linux s), have two types of stable releases: normal, or stable releases and long-term support (LTS) releases which are maintained for a longer period of time.

Release
Once released, the software is generally known as a "stable release". The formal term often depends on the method of release: physical media, online release or a web application.

Release to manufacturing (RTM)
The term release to manufacturing (RTM), also known as "going gold", is a term used when a software product is ready to be delivered. This build may be, allowing the end user to verify the integrity and authenticity of the software purchase. A copy of the RTM build known as the "golden master" or GM is sent for mass duplication if applicable. This terminology is taken from the audio record making industry, specifically the process of. RTM precedes general availability (GA) when the product is released to the public. A golden master build (GM) is typically the final build of a piece of software in the beta stages for developers. Typically, for iOS, it is the final build before a major release, however, there have been a few exceptions.

It is typically used in certain retail mass-production software contexts—as opposed to a specialized software production or project in a commercial or government production and distribution—where the software is sold as part of a bundle in a related computer hardware sale and typically where the software and related hardware is ultimately to be available and sold on mass/public basis at retail stores to indicate that the software has met a defined quality level and is ready for mass retail distribution. RTM could also mean in other contexts that the software has been delivered or released to a client or customer for installation or distribution to the related hardware end user computers or machines. The term does not define the delivery mechanism or volume; it only states that the quality is sufficient for mass distribution. The deliverable from the engineering organization is frequently in the form of a golden master media used for duplication or to produce the image for the web.

General availability (GA)
General availability (GA) is the marketing stage at which all necessary activities have been completed and a software product is available for purchase, depending, however, on language, region, electronic vs. media availability. Commercialization activities could include security and compliance tests, as well as localization and worldwide availability. The time between RTM and GA can be from a week to months in some cases before a generally available release can be declared because of the time needed to complete all commercialization activities required by GA. At this stage, the software has "gone live".

Release to the Web (RTW)
Release to the Web (RTW) or Web release is a means of software delivery that utilizes the Internet for distribution. No physical media are produced in this type of release mechanism by the manufacturer. Web releases are becoming more common as Internet usage grows.

Support
During its supported lifetime, software is sometimes subjected to service releases, or s, sometimes also called "interim releases" or "maintenance release" (MR). For example, Microsoft released three major service packs for the 32-bit editions of Windows XP and two service packs for the 64-bit editions. Such service releases contain a collection of updates, fixes, and enhancements, delivered in the form of a single installable package. They may also implement new features. Some software is released with the expectation of regular support. Classes of software that generally involve protracted support as the norm include and s. Continuing with this Windows XP example, Microsoft did offer paid updates for five more years after the end of extended support. This means that support ended April 8, 2019.

End-of-life
When software is no longer sold or supported, the product is said to have reached end-of-life, to be discontinued, retired, deprecated, abandoned, or obsolete, but user loyalty may continue its existence for some time, even long after its platform is obsolete—e.g., the and Sinclair.

After the end-of-life date, the developer will usually not implement any new features, fix existing defects, bugs or vulnerabilities (whether known before that date or not) or provide any support for the product. If the developer is kind enough, they may release the source code, so the platform will live again, and be maintained by volunteers.