Software release life cycle

The software release life cycle is the process of developing, testing, and distributing a software product, like an operating system. It has several stages before the final version is released to everyone.

Pre-alpha is the very early part of making the software, when it is still being designed and built. Alpha testing is the first formal testing step, where the software is tested inside the company. Beta testing is next, where more people outside the company try the software to help find problems.

After beta testing, the software might go through one or more release candidate steps, where it is improved and tested more before the final version comes out. Some software, especially online tools, stays in a perpetual beta state. This means it is always being updated and improved, and users can start using it even while it is still being worked on.

Stages of development

Pre-alpha

Pre-alpha is the first step in making software. During this time, developers plan and build the basic parts of the program. They decide what the software should do, design how it will look, and write the first bits of code.

Alpha

Next is the alpha stage. This is when developers test the software for the first time to see how well it works. They look for and fix problems. The software might still have big issues that could make it stop working or lose information. It also might not have all the features of the final version.

Beta

After alpha, the software enters the beta stage. Now, the software has most of its features but still has some problems. Beta testing focuses on making the software easier to use and fixing any remaining issues. People outside the company may try the software and tell the developers about any problems they find.

Release candidate

A release candidate is a version of the software that is almost ready to be the final product. It has been tested and fixed many times. If no major problems are found, this version will become the final release.

Stable release

The stable release is the final version of the software that is ready for everyone to use. It has passed all tests and any remaining issues are small enough that they won’t cause big problems. Some software also has special long-term support versions that only get updates to keep them safe.

Release

Once a software program is released, it is called a "stable release". The name for this stage depends on how the software is shared, whether on physical media, online, or as a web application.

Usually, the released software gets an official name or number. Before the final release, there might be special internal names or numbers used during development.

Release to manufacturing (RTM)

The term "release to manufacturing" (RTM), also known as "going gold", means the software is ready to be shared with everyone. This version may be digitally signed so people can check it is real. The RTM build is called the "gold master" or GM and is used for making many copies if needed. This term comes from how audio records are made. RTM happens before general availability (GA), when the product is shared with the public. For iOS, it is usually the last build before a big update.

RTM is often used when software is sold with computer hardware in stores. It means the software has passed certain checks and is ready to be sold to many people. RTM can also mean the software is given to a customer to put on their computers. It does not say how the software is shared, only that it is good enough for many people to use.

General availability (GA)

General availability (GA) is when a software product is ready to be sold. All the work to get it ready, like tests and making it available in different languages, is done. The time between RTM and GA can be days or months, depending on how much work is needed. At this point, the software has "gone live".

Release to the Web (RTW)

Release to the Web (RTW) or Web release is when software is shared online. No physical copies are made. Web releases have become more common as more people use the Internet.

Support

When people use software, it might get updates, fixes, or small improvements. These are called service releases, patches, or service packs. They are like bundles of updates that make the software better or fix problems. For example, Windows XP had service packs that added new features and fixed issues.

Some software, like anti-virus suites or massively multiplayer online games, is expected to keep getting updates for a long time. Even after regular support stops, some companies may still offer updates for a fee. For example, Microsoft offered paid updates for Windows XP for five years after regular support ended.

End-of-life

When a software product is no longer sold or supported, it is called end-of-life. This means the developer will not add new features, fix problems, or offer help for that software anymore. However, some people may still use the software even after it is old and no longer supported. Sometimes, the developer may share the software's code so volunteers can keep maintaining it.

History

The words "alpha" and "beta" for testing software began at IBM. People at IBM used similar words to talk about their software work as early as the 1950s. The "A" test checked a new product before telling people about it. The "B" test checked it before making it. The "C" test was the last check before the product was ready for everyone. As software grew more important to IBM, they used "alpha" for testing before the announcement and "beta" to show the product was ready for everyone.

Later, many famous products had public beta versions. For example, people could buy a special "pioneer edition" of a word processor for the IBM PC. In 2000, Apple released a public beta version of their Mac OS X operating system. Between 2005 and 2006, Microsoft shared early versions of Windows Vista with the public. From 2009 to 2011, the game Minecraft was in a public beta stage. Some beta versions, like Gmail and Google News, stayed in beta for many years even though many people used them. Since Windows 8, Microsoft has used the word "preview" instead of "beta" for early versions of their software.