Skip to main content

Glossary S

Glossary · E-commerce

Software release

Area
E-commerce

A software release is a published, deployable version of a piece of software, made available under a fixed version number for download and installation.

A release carries a version number, which under the Semantic Versioning specification takes the form MAJOR.MINOR.PATCH. The first part goes up with incompatible changes. The second goes up with new backwards-compatible functionality, the third with backwards-compatible bug fixes only. Once a version has been released, its contents must not be modified, and any change has to go out as a new version. A pre-release such as an alpha version has lower precedence than the normal version with the same number.

For us, a section in a changelog is not yet a release, even if it already carries a new version number. Only what has actually been published counts. The security releases of PHP and Symfony show us whether the patch level of the server and the shop is up to date.

PHP shows what a release cycle can look like. The PHP project states that each release branch is fully supported for two years from its first stable release, with bug and security fixes in regular point releases. Two further years follow in which only critical security issues are fixed. The release a shop runs on therefore determines whether it still receives security fixes or whether its branch has reached end of life (EOL).

Where the term appears

Sources

  1. About releases (opens in a new tab)

    GitHub Docs (docs.github.com) accessed

  2. Semantic Versioning 2.0.0, deutsche Fassung (opens in a new tab)

    Semantic Versioning (semver.org) accessed

  3. Supported Versions (opens in a new tab)

    The PHP Group (php.net) accessed

Share on LinkedIn

Let's talk about your project.

If this term is on your desk right now, a conversation usually helps faster than any definition.

Search the website

Popular topics

All results