Definition “Software Market release” What is a software release?
The software release is perhaps the decisive step in the development stages of a software, because the development is terminated with the market release for the time being. Due to the digital distribution, however, there are new release models and development stages.
Company about the topic
In the era of optical media, the software release was still synonymous with the market launch of the main version of a software.
In German, every software version that is released for the end customer is actually the current release version. The software release is therefore basically equivalent to the start of sales.
Thanks to digital distribution models of the Software Release must not, however, a final version number mark, which is then functionalized by Patches and Hotfixes acute. The best way to understand the software release is to look at the different stages of development that are still relevant for modern digital storefronts.
From pre-alpha to release-the way to software release
A publishable software is a big piece of outstaffing work and requires not only long development work, but also rigorous testing. The path from the concept to the release version is anything but linear and leads to the software release via various builds. These builds are also a simple overview of which phase of development a software is in.
A pre-alpha version, for example, is a very early preview that is not yet intended for the public. This is a developer preview in which elementary errors can still be present. Only a rough framework of the software is available at this time, crashes and missing functions and interfaces are here rather the rule than the exception.
In the Alpha version there is a first summarized build, which is still heavily error-prone and only needs to be representative for the final software to a limited extent. Usually, alpha versions are only made available to very limited user groups (usually other software engineers). During the next big jumps to the beta version, the test groups will be successively expanded.
The beta version should then be much more functional and stable than an alpha, but can still be very incomplete and contain gross errors. It is often planned that software will go into a public beta and thus be tested by a large number of users before the release.
This model not only provides developers with plenty of data, but also valuable feedback to revise their software. The release model “Early Access” is also an option here, where users can purchase software before the software release (usually at a discounted price) and then gain access to a public beta.
Derived from the beta version, which is still being developed until the final release, is also the “Perpetual beta”. From web development, this term is an allusion to the continuous development and improvement of software such as websites. So they are never completely finished and are in an eternal beta.
Based on the beta version,” regular ” software is further developed in such a way that one or more release candidates are available. These development candidates are close to the required quality for a software release, here it only depends on the right level of quality assurance.
The software release in practice
If a release candidate is released for the software release, then this version 1.0 (even if it does not always have to be the software version 1.0) comes into the necessary distribution channels. Until the 2010s, this meant creating a master disc to burn the necessary DVDs and serve the end customers from the pressing plant.
With digital app stores this is no longer necessary, only the distribution channels still have to release the software or it is marketed through its own website. This means that the actual software release has lost its importance, because customers no longer need to be supplied with updates via physical media or laboriously search for patches and updates. Digitally, the latest version can always be purchased by customers and automatic updates allow customers to get to the latest version quickly and automatically.
In models such as Software as a Service (as practiced by Adobe with Creative Cloud, for example), customers use an subscription model and always receive the latest version number. Larger updates are also included in this subscription. When, for example, the last software release of a full version of Premiere or Photoshop was, de facto no longer matters.
Apple uses a similar model for creative software such as Final Cut Pro X or Logic and also provides major updates free of charge after a one-time purchase. Especially in the games industry, a public beta or early access is now common, real software releases can shift over years.
But the consequences of flowing distribution are not always positive. Day One Patches are a now common practice to publish software more or less unfinished and error-prone and to require customers to download large patches or completely new versions.