Content deleted Content added
m Reverted edits by 2409:40E2:1E:5F3:C47:17FF:FEEA:8895 (talk) (HG) (3.4.12) |
Maxeto0910 (talk | contribs) m →Release to manufacturing (RTM): no sentence |
||
| (44 intermediate revisions by 35 users not shown) | |||
Line 1:
{{short description|Sum of the phases of development and maturity for computer software}}
{{More citations needed|date=April 2023}} {{Use dmy dates|date=February 2020|cs1-dates=y}}
The '''software release life cycle''' is the process of developing, testing, and distributing a software product (e.g., an [[operating system]]). It typically consists of several stages, such as pre-alpha, alpha, beta, and release candidate, before the final version, or "gold", is released to the public.
[[File:Software dev2.svg|thumb|upright=1.1|An example of a basic software release life cycle]]
Pre-alpha refers to the early stages of development, when the software is still being designed and built. Alpha testing is the first phase of formal testing, during which the software is tested internally using [[White-box testing|white-box techniques]]. Beta testing is the next phase, in which the software is tested by a larger group of users, typically outside of the organization that developed it. The beta phase is focused on reducing impacts on users and may include usability testing.
Line 15 ⟶ 16:
=== {{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
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.) |chapter=Alpha software |year=2013 |publisher=Oxford University Press |isbn=978-0-19-174415-0 |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 for [[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 '''feature-complete''' (FC) version of a piece of [[software]] has all of its planned or primary [[software feature|features]] implemented but is not yet final due to [[software bug|bugs]], [[software performance|performance]] or [[Software testing|stability]] issues.<ref>{{cite book |last=Cusumano |first=Michael |url=https://archive.org/details/microsoftsecrets00cusu |title=Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People |publisher=Free Press |year=1998 |isbn=978-0-684-85531-8 |pages=[https://archive.org/details/microsoftsecrets00cusu/page/202 202–203] |url-access=registration}}</ref> This occurs at the end of alpha testing in [[Software development|development]].
Usually, feature-complete software still has to undergo [[beta testing]] and [[Patch (computing)|bug fixing]], as well as performance or stability enhancement before it can go to [[
=== {{Anchor|BETA}}Beta ===
Line 36 ⟶ 35:
| access-date = 2015-04-06
| website = thefreedictionary.com
}}</ref> A beta phase generally begins when the software is feature-complete but likely to contain several 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|url=https://archive.org/details/nextgen-issue-015/page/n31/mode/2up}}</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 on 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 [[
| url = https://access.redhat.com/support/offerings/techpreview
| title = Technology Preview Features Support Scope
Line 63 ⟶ 62:
== {{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.<ref name="
=== {{Anchor|RTM|Release to manufacturing|Release to marketing|RTM or RTW}}Release to manufacturing (RTM) ===
[[File:Satya Nadella Gears of War 4 Gold Master.jpg|thumb|[[Satya Nadella]] of [[Microsoft]] with the gold master disc of ''[[Gears of War 4]]'']]
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 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 |date=19 August 2013 |language=en}}</ref> is sent for mass duplication or disc replication if applicable. The 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.
Line 78:
== Support ==
During its supported lifetime, the software is sometimes subjected to service releases, [[patch (computing)|patches]] or [[service pack]]s, sometimes also called "interim releases" or "maintenance releases" (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.<ref>{{Cite web |title=Microsoft Update Catalog |url=https://www.catalog.update.microsoft.com/Search.aspx?q=xp%20service%20pack%203 |access-date=2024-05-03 |website=www.catalog.update.microsoft.com}}</ref> 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 on April 8, 2019.<ref>{{Cite web |date=2012-07-20 |title=Microsoft Product Lifecycle Search |url=http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+XP |access-date=2024-05-03 |archive-url=https://web.archive.org/web/20120720010405/http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+XP |archive-date=20 July 2012 }}</ref>▼
▲During its supported lifetime, the software is sometimes subjected to service releases, [[patch (computing)|patches]] or [[service pack]]s, sometimes also called "interim releases" or "maintenance releases" (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 on 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 [[Common Desktop Environment]]<ref>{{Cite web |title=[cdesktopenv-devel] CDE 2.2.1 released {{!}} CDE - Common Desktop Environment |url=https://sourceforge.net/p/cdesktopenv/mailman/message/32043063/ |access-date=2024-05-03 |website=sourceforge.net}}</ref> and Sinclair [[ZX Spectrum]].<ref>{{Cite web |date=2018-01-05 |title=ZX-Uno [ZX Spectrum Computer Clone Based on FPGA] |url=http://zxuno.speccy.org/index_e.shtml |access-date=2024-05-03 |archive-url=https://web.archive.org/web/20180105191835/http://zxuno.speccy.org/index_e.shtml |archive-date=5 January 2018 }}</ref>
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, and if not, it may be reverse-engineered later when it becomes [[abandonware]].
== History ==
Usage of the "alpha/beta" test terminology originated at [[IBM]].{{cn|date=May 2024}} 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. The "B" test was the verification before releasing the product to be manufactured. The "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".
Major public betas developed afterward, with early customers having 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
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 at the 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|archive-date=2005-02-14|title=A long winding road out of beta |website= Tech News on ZDNet |first1= Paul |last1=Festa |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 Google Apps (now named [[Google Workspace]]), including Gmail, in July 2009.<ref name="
== See also ==
Line 100 ⟶ 99:
* [[Application-release automation]]
* [[Application retirement]]
* [[Release engineering]]
* [[Release management]]
| |||