Software release life cycle

 

A software release life cycle refers to the phases of development and maturity for a piece of computer software—ranging from its initial development, to its eventual release, and updated versions of the released version to help improve software or fix bugs still present in the software.

Stages of development

Pre-alpha

Pre-alpha refers to all activities performed during the software project prior to testing. These activities can include requirements analysis, software design, software development and unit testing.

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 functionality is complete.

Alpha

The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the ancient Greek alphabet, used as the number 1). In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release.^[1]

Alpha software can be unstable and could cause crashes or data loss. The exception to this is when the alpha is available publicly (such as a pre-order bonus), in which developers normally push for stability so that their testers can test properly. External availability of alpha software is uncommon in proprietary software. However, open source software, in particular, often have publicly available alpha versions, often distributed as the raw source code of the software.

The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete.

Beta

Beta (named after the second letter of the Greek alphabet) is the software development phase following alpha. It generally begins when the software is feature complete. 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 this is typically the first time that the software is available outside of the organization that developed it.

The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software, willing to test the software without charge, often receiving the final software free of charge or for a reduced price.

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, prototype, technical preview (TP), or early access.

Some software is kept in perpetual beta—where new features and functionality is continually added to the software without establishing a firm "final" release.

Open and closed beta

Developers release either a closed beta or an open beta; closed beta versions are released to a select group of individuals for a user test and are invitation only, while open betas are from a larger group to the general public and anyone interested. 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 are:

• In September 2000 a boxed version of Apple's Mac OS X Public Beta operating system was released.^[2]
• Microsoft's release of community technology previews (CTPs) for "Longhorn" in January 2005.^[3]

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 may not find.

Release candidate

The term release candidate (RC) refers to a version with potential to be a final product, which is ready to release unless fatal 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 bug.

A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There may still be source code changes to fix defects. There may still be changes to documentation and data files, and to the code for test cases or utilities. New code may be added in a future release.

Release

RTM

The term "release to manufacturing" or "release to marketing" (both abbreviated RTM, initials also commonly used for the quite different "return to manufacturer" of faulty goods)—also known as "going gold"—is a term used when software is ready for or has been delivered or provided to the customer. 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 gold master CD used for duplication or to produce the image for the web.

RTM precedes general availability (GA) when the product is released to the public.

General availability (GA)

General availability or general acceptance (GA) is the point where all necessary commercialization activities have been completed and the software has been made available to the general market either via the web or physical media. Another term with a meaning almost identical to GA is first customer shipment (FCS). Some companies (such as Sun Microsystems and Cisco) use FCS to describe a software version that has been shipped for revenue.

Commercialization activities could include but are not limited to the availability of media world wide via dispersed distribution centers, marketing collateral is completed and available in as many languages as deemed necessary for the target market, the finishing of security and compliance tests, etc. 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.

It is also at this stage that the software is considered to have "gone live". The production, live version is the final version of a particular product. A live release is considered to be very stable and relatively bug-free with a quality suitable for wide distribution and use by end users. In commercial software releases, this version may also be signed (used to allow end-users to verify that code has not been modified since the release). The expression that a software product "has gone live" means that the code has been completed and is ready for distribution. Other terms for the live version include live master, live release, and live build.

In some areas of software development it is at this stage that the release is referred to as a gold release; this seems to be confined mainly to game software though Apple also refer to GM (gold master) releases.

Some release versions might be classified as a long term support (LTS) release, which should guarantee the ability to upgrade to the next LTS release and will be supported/updated/patched for a longer time than a non-LTS release.

Support

During its supported lifetime, software is sometimes subjected to service releases, or service packs, sometimes also called “interim releases”. As a well used example, Microsoft's Windows XP has currently had three major Service Packs, and Windows 7 was at service pack 1 as of April 2011.

Such service releases contain a collection of updates, fixes and/or enhancements, delivered in the form of a single installable package. They may also contain entirely new features.

Certain software is released with the expectation of regular support. Classes of software that generally involve protracted support as the norm include anti-virus suites and massively multiplayer online games.

End-of-life

See also: End-of-life (product)

When software is no longer sold or supported, the product is said to have end-of-life, to be discontinued 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 Commodore’s Amiga.

Impact of the World Wide Web

As the Internet has allowed for rapid and inexpensive distribution of software, companies have begun to take a more loose approach to use of the word "beta".^[4] Netscape Communications was infamous for releasing alpha level versions of its Netscape web browser to the public and calling them "beta" releases.^{[citation needed]} In February 2005, ZDNet published an article about the recent phenomenon of a beta version often staying for years and being used as if it were in production level, disparagingly called “perpetual beta”. It noted that Gmail and Google News, for example, had been in beta for a long period of time and were not expected to drop the beta status despite the fact that they were widely used; however, Google News did leave beta in January 2006, followed by Google Apps, including Gmail, in July 2009.^[5] This technique may also allow a developer to delay offering full support and/or responsibility for remaining issues. In the context of Web 2.0, people even talk of perpetual betas to signify that some software is meant to stay in beta state. Also, "beta" is sometimes used to indicate something more like a release candidate, or as a form of time limited demo, or marketing technique.^[6]

Some users disparagingly refer to release candidates and even final "point oh" releases as "gamma test" software, suggesting that the developer has chosen to use its customers to test software that is not truly ready for general release. Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product.

Web release

A 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. This is sometimes also referred to as release to web (RTW). Web releases seem to be more common nowadays due to the fact that you can get the software out to the consumer much more quickly. An individual can buy the software online and download it from the website, vice having to go out to a store to buy it or ordering it and having it delivered to one’s home.

See also

• Paper launch
• Release engineering
• Release management
• Rolling release
• Software maintenance
• Software testing
• Software versioning
• Software deployment
• Vaporware

References

1. ^ "Encyclopedia definition of alpha version". PC Magazine. http://www.pcmag.com/encyclopedia_term/0,2542,t=alpha+version&i=37675,00.asp. Retrieved 12 January 2011. 
2. ^ "Apple Releases Mac OS X Public Beta" (Press release). Apple Inc.. 13 September 2000. http://www.apple.com/pr/library/2000/sep/13macosx.html. Retrieved 22 February 2011. 
3. ^ "Microsoft Windows Vista October Community Technology Preview Fact Sheet" (Press release). Microsoft. October 2005. http://www.microsoft.com/presspass/newsroom/winxp/WinVistaCTPFS.mspx. Retrieved 22 February 2011. 
4. ^ "Waiting with Beta'd Breath TidBITS #328 (May 13, 1996)". Archived from the original on 2006-05-15. http://web.archive.org/web/20060515093203/http://www.tidbits.com/tb-issues/TidBITS-328.html. 
5. ^ "Google Apps is out of beta (yes, really)". Google Blog. Google. 7 July 2009. http://googleblog.blogspot.com/2009/07/google-apps-is-out-of-beta-yes-really.html. Retrieved 12 January 2011. 
6. ^ The inconvenient truths behind betas

Further reading

• Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation by Jez Humble, David Farley; ISBN 0-321-60191-2

External links

• Free Software Project Management HOWTO
• Software Release Decisions
• A Methodology to Support Software Release Decisions
• Software Testing Life Cycle
• Semantic versioning