View source for Software release life cycle

{{short description|Sum of the phases of development and maturity for computer software}}
{{Multiple issues|
{{More footnotes|date=May 2012}}
{{Lead too short|date=November  2017}}
}}
{{Use dmy dates|date=February 2020|cs1-dates=y}}
[[File:Software dev2.svg|thumb|upright=1.1|Software release life cycle]]
A '''software release life cycle''' is the sum of the stages of development and maturity for a piece of computer [[software]]. Cycles range from its initial development to its eventual release, and include updated versions of the released version to help improve software or fix [[software bug]]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.<ref>{{cite web|title=Why Google kept Gmail in "beta" for so many years.|url=https://slate.com/news-and-politics/2009/07/why-google-kept-gmail-in-beta-for-so-many-years.html}}</ref>

== 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 [[software verification|verification]] 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".

== Stages of development ==
=== Pre-alpha ===
Pre-alpha refers to all activities performed during the software project before formal testing. These activities can include [[requirements analysis]], [[software design]], [[software development]], and [[unit testing]]. In typical [[Open-source software|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.

=== {{anchor|Alpha}}Alpha ===
The alpha phase of the release life cycle is the first phase of [[software testing]] (alpha is the first letter of the [[Greek alphabet]], used as the number 1). In this phase, developers generally test the software using [[white-box testing|white-box techniques]]. Additional validation is then performed using [[black-box testing|black-box]] or [[Grey box testing#Grey box testing|gray-box]] techniques, by another testing team. Moving to black-box testing inside the organization is known as ''alpha release''.<ref name=alphadef>{{cite web|url=https://www.pcmag.com/encyclopedia_term/0,2542,t=alpha+version&i=37675,00.asp |title=Encyclopedia definition of alpha version |work=[[PC Magazine]] |access-date=2011-01-12 |url-status=live |archive-url=https://web.archive.org/web/20110427065905/http://www.pcmag.com/encyclopedia_term/0%2C2542%2Ct%3Dalpha%20version%26i%3D37675%2C00.asp |archive-date=2011-04-27 }}</ref>{{better source needed|date=March 2019}}

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.<ref>{{cite book |editor1-last=Ince |editor1-first=Darrel |title=A Dictionary of the Internet (3 ed.) |year=2013 |publisher=Oxford University Press |isbn=9780191744150 |url=https://www.oxfordreference.com/abstract/10.1093/acref/9780191744150.001.0001/acref-9780191744150-e-95?rskey=VLB7Gk&result=2 |access-date=15 July 2019}}</ref> Alpha software may not contain all of the features that are planned for the final version.<ref>{{cite magazine|title=The Next Generation 1996 Lexicon A to Z|magazine=[[Next Generation (magazine)|Next Generation]]|issue=15 |publisher=[[Imagine Media]]|date=March 1996|page=29|quote=Alpha software generally barely runs and is missing major features like gameplay and complete levels.}}</ref> In general, external availability of alpha software is uncommon in [[proprietary software]], while [[Free and open-source software|open source software]] often has publicly available alpha versions. The alpha phase usually ends with a [[Freeze (software engineering)|feature freeze]], indicating that no more features will be added to the software. At this time, the software is said to be [[feature complete]]. A beta test is carried out following [[acceptance testing]] at the supplier's site (alpha test) and immediately prior to general release of the software as a product.<ref>{{cite book |title=A Dictionary of Computer Science |year=2016 |publisher=Oxford University Press |isbn=9780199688975 |pages=44 |edition=7th}}</ref>

=== {{Anchor|BETA}}Beta ===
{{Redirect|Beta test|the film|Beta Test (film)}}

Beta, named after [[Beta|the second letter of the Greek alphabet]], is the software development phase following alpha. Software in the beta stage is also known as ''betaware''.<ref>{{cite web
 | url = http://encyclopedia2.thefreedictionary.com/betaware
 | title = Definition of betaware in the Free Online Encyclopedia
 | access-date = 2015-04-06
 | website = thefreedictionary.com
}}</ref> A beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs.<ref>{{cite magazine|title=The Next Generation 1996 Lexicon A to Z|magazine=[[Next Generation (magazine)|Next Generation]]|issue=15 |publisher=[[Imagine Media]]|date=March 1996|page=30}}</ref> Software in the beta phase will generally have many more bugs in it than completed software and speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating [[usability testing]]. The process of delivering a beta version to the users is called ''beta release'' and is typically the first time that the software is available outside of the organization that developed it. Software beta releases can be either 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'' or ''technology preview'' (''TP''),<ref>{{cite web
 | url = https://access.redhat.com/support/offerings/techpreview
 | title = Technology Preview Features Support Scope
 | access-date = 2015-03-18
 | publisher = [[Red Hat]]
}}</ref> 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 [[Windows Insider Program]] launched in 2014 are termed "Insider Preview builds". "Beta" may also indicate something more like a [[#Release candidate|release candidate]], or as a form of time-limited demo, or marketing technique.<ref>[http://www.gamesradar.com/f/the-inconvenient-truths-behind-betas/a-2010051712402686048 The inconvenient truths behind betas] {{webarchive|url=https://web.archive.org/web/20110430173029/http://www.gamesradar.com/f/the-inconvenient-truths-behind-betas/a-2010051712402686048 |date=2011-04-30 }}</ref>

''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.{{cn|date=February 2021}}

==== Perpetual beta ====
{{main article|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''.<ref>{{cite web|url=http://www.tidbits.com/tb-issues/TidBITS-328.html |title=Waiting with Beta'd Breath ''TidBITS'' #328 (May 13, 1996) |archive-url = https://web.archive.org/web/20060515093203/http://www.tidbits.com/tb-issues/TidBITS-328.html |archive-date = 2006-05-15}}</ref> In February 2005, [[ZDNet]] published an article about the phenomenon of a beta version often staying for years and being used as if it were in production level.<ref>{{Cite web|url=http://news.zdnet.com/2100-9588-5571590.html|archive-url=https://web.archive.org/web/20050214062749/http://news.zdnet.com/2100-9588-5571590.html|url-status=dead|archive-date=2005-02-14|title=A long winding road out of beta {{!}} Tech News on ZDNet|date=2005-02-14|access-date=2019-04-28}}</ref> It noted that [[Gmail]] and [[Google News]], for example, had been in beta for a long time although widely used; Google News left beta in January 2006, followed by [[G Suite|Google Apps]], including Gmail, in July 2009.<ref>{{cite web|url=http://googleblog.blogspot.com/2009/07/google-apps-is-out-of-beta-yes-really.html |title=Google Apps is out of beta (yes, really) |work=Google Blog |date=7 July 2009 |access-date=2011-01-12 |url-status=live |archive-url=https://web.archive.org/web/20110121002635/http://googleblog.blogspot.com/2009/07/google-apps-is-out-of-beta-yes-really.html |archive-date=21 January 2011 }}</ref> This technique may allow a developer to delay offering full support and responsibility for remaining issues.

==== Open and closed beta ====
<!-- Closed beta test redirects here -->
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, [[Stephen Manes]] 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."<ref name="manes19840403"/>
* In September 2000 a ''boxed version'' of [[Apple Inc.|Apple]]'s [[Mac OS X Public Beta]] operating system was released.<ref>{{cite press release|title=Apple Releases Mac OS X Public Beta |publisher=Apple Inc. |url=https://www.apple.com/pr/library/2000/sep/13macosx.html |access-date=2011-02-22 |date=13 September 2000 |url-status=live |archive-url=https://web.archive.org/web/20110501091431/http://www.apple.com/pr/library/2000/sep/13macosx.html |archive-date=1 May 2011 }}</ref>
* Microsoft's release of ''community technology preview''s (''CTP''s) for [[Windows Vista]], between September 2005 and May 2006.<ref>{{cite press release|url=http://www.microsoft.com/presspass/newsroom/winxp/WinVistaCTPFS.mspx |title=Microsoft Windows Vista October Community Technology Preview Fact Sheet |date=October 2005 |access-date=2011-02-22 |publisher=Microsoft |url-status=live |archive-url=https://web.archive.org/web/20110430145018/http://www.microsoft.com/presspass/newsroom/winxp/WinVistaCTPFS.mspx |archive-date=2011-04-30 }}</ref>
* 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.{{cn|date=February 2021}}

=== 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 [[software bug|bugs]] 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 distribution]]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.

== {{Anchor|STABLE-RELEASE}}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.

=== {{Anchor|RTM|Release to manufacturing|Release to marketing|RTM or RTW}}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 [[Code signing|digitally signed]], allowing the end user to verify the integrity and authenticity of the software purchase. A copy of the RTM build known as the "[[mastering (audio)|gold master]]" or GM<ref>{{cite web |title=What is Golden Master (GM)? - Definition from Techopedia |url=https://www.techopedia.com/definition/5434/golden-master-gm |website=Techopedia.com |language=en}}</ref><ref>{{cite web |title=Mac OS X "Gold Master" Released To Manufacturing |url=https://www.apple.com/newsroom/2001/03/07Mac-OS-X-Gold-Master-Released-To-Manufacturing/ |website=Apple Newsroom}}</ref> is sent for mass duplication or disc replication if applicable.  This terminology is taken from the audio record making industry, specifically the process of [[mastering (audio)|mastering]]. 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.

=== {{Anchor|GA|General availability}}General availability (GA) ===
[[File:ProductEndOfLifeCycle.png|thumb|Milestones in a product life cycle: general availability (GA), [[end of life announcement]] (EOLA), [[last order date]] (LOD), and [[End-of-life (product)|end-of-life]] (EOL)]]
'''General availability''' ('''GA''') is the marketing stage at which all necessary [[commercialization]] activities have been completed and a software product is available for purchase, depending, however, on language, region, electronic vs. media availability.<ref>{{cite document|first=Yvan Philippe |last=Luxembourg |title=Top 200 SAM Terms – A Glossary Of Software Asset Management Terms |url=http://omtco.eu/references/sam/top-200-sam-terms-a-glossary-of-software-asset-management-terms/ |publisher=OMTCO |date=20 May 2013 |access-date=21 May 2013 |url-status=live |archive-url=https://web.archive.org/web/20130810111112/http://omtco.eu/references/sam/top-200-sam-terms-a-glossary-of-software-asset-management-terms/ |archive-date=10 August 2013 }}</ref> 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".

=== {{Anchor|Web release}}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, [[patch (computing)|patches]] or [[service pack]]s, sometimes also called "interim releases" or "maintenance release" (MR). For example, Microsoft released three major service packs for the [[Microsoft Windows|32-bit]] editions of [[Windows XP]] and two service packs for the [[64-bit computing|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 [[Antivirus software|anti-virus suites]] and [[massively multiplayer online game]]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 {{Anchor|EOL|End of life}} ===
{{See also|End-of-life product|abandonware}}

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 [[Atari ST]] and Sinclair [[ZX Spectrum]].

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 wishes, they may release the source code, so the platform will live again, and be maintained by volunteers.

== See also ==
{{Portal|Computer programming}}
* [[Application retirement]]
* [[Merge window]]
* [[Application-release automation|Release automation]]
* [[Release engineering]]
* [[Release management]]
* [[Rolling release]]
* [[Software deployment]]
* [[Software versioning]]
* [[Application lifecycle management|Lifecycle management]]

== References ==
{{Reflist|refs=
<ref name="manes19840403">{{cite magazine |title=Taking A Gamble With Word Vision |author-last=Manes |author-first=Stephen |author-link=Stephen Manes |magazine=[[PC Magazine]] - The Independent Guide To IBM Personal Computers |publisher=[[PC Communications Corp.]] |issn=0745-2500 |date=1984-04-03 |volume=3 |number=6 |pages=211–221 |url=https://books.google.com/books?id=e-gI2W-3JwkC&pg=PA211 |access-date=2015-02-15 |url-status=live |archive-url=https://web.archive.org/web/20150317045015/https://books.google.com/books?id=e-gI2W-3JwkC&lpg=PA212&pg=PA211 |archive-date=2015-03-17}}</ref>
}}

== Bibliography ==
* ''Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation'' by Jez Humble, David Farley; {{ISBN|0-321-60191-2}}

{{Software distribution}}

[[Category:Software release| ]]