Version policy
Mia-Platform version numbers consists of three, dot separated, parts: MAJOR.MINOR.PATCH.
- MAJOR is increased for significant or disruptive Mia-Platform functionalities. A major update may bring backward-incompatible changes;
- MINOR is increased for new functionalities and significant improvements;
- PATCH is increased for small improvements, bug fixes or security updates.
Release history
This section lists all the Major versions released over time; for self-hosted installation read the Stable version release policy to find out which version are receiving official support.
Mia-Platform guarantees security patches for the two preceding versions to the current Major.
| Release | Release Date | End of Life Date |
|---|---|---|
| v13 (current) | May 2024 | End of 2025 |
| v12 | November 2023 | May 2025 |
| v11 | May 2023 | End of 2024 |
| v10 | October 2022 | May 2024 |
| v9 | April 2022 | November 2023 |
| v8 | October 2021 | May 2023 |
| v7 | February 2021 | October 2022 |
| v6 | September 2020 | April 2022 |
| v5 | January 2020 | April 2022 |
| v4 | July 2018 | January 2021 |
| v3 | September 2017 | September 2020 |
| v2 | November 2016 | December 2019 |
| v1 | December 2015 | July 2018 |
The current version of the Platform is visible in the Console info section.
Feature Preview and Beta
New Mia-Platform version may include features that are not yet considered stable; such features are highlighted with a special tag denoting the current feature state.
Preview and beta feature are usually disabled by default and can be enabled using the Feature Preview pages (depending whether the feature has impact on specific users or whole Projects).
The currently used feature states are the following:
- experimental: used for feature that are under heavy development;
- preview: generally representing the first iteration for a new feature; it means that the feature is available for use but it may not be completed yet or could be subject to undocumented breaking changes;
- beta: the feature implementation is completed and there will not be any undocumented breaking changes. However, for different reasons (e.g. lack of proper validation on certain use-cases), it may be yet considered unsuitable for use in production, hence it must be used carefully.