Release Naming

Introduction

This page outlines the approach Aeron takes to naming versions of the software and covers how releases can be categorised as either:

• Alpha builds
• Beta builds
• Stable builds

Alpha, Beta and Stable builds

In order to give earlier access to new products and features that are still in development, we publish alpha or beta builds.

Alpha or beta builds are intended to be used as a preview of new features and products, and to allow users to give us feedback on things that may need to be changed before a general release.

These builds will have an -alpha or -beta suffix in the version number. E.g. 0.2.0-alpha or 1.2.3-alpha.

We recommend adoption of these builds be done with engagement from the Aeron team.

Alpha build

Alpha builds will be incomplete versions of the features or products. I.e. early development builds. They should be considered to have an unstable API and come with limited documentation. We do not generally recommend the use of these components in a product environment, and as such issues will be treated as P3/P4 (development environments).

Beta build

Beta builds will be closer to a releasable version. They will be more stable than alpha, but should still be considered to have an unstable API. We do not generally recommend the use of these components in a product environment, and as such issues will be treated as P3/P4 (development environments).

Stable builds

Versions without an -alpha or -beta suffix should be considered supported, stable builds of the product.

How is this distinct from experimental features?

These builds may be for Open Source or Premium products and are distinct from Experimental Features, which are features that are experimental and can be included in an alpha, beta or stable release.