Versioning
Versioning Scheme
Versions used in AME follow the Semantic Versioning 2.0.0 principles. Versions are structured as MAJOR.MINOR.PATCH
, where:
- MAJOR version increments indicate incompatible API changes, changes in the default behavior of AME, and removal of features
- MINOR version increments indicate the addition of new features in a backward-compatible manner and changes to data structures that do not break existing functionality, or can be migrated automatically
- PATCH version increments indicate backward-compatible bug fixes and minor improvements
Deprecation Policy
Features and functionality are only removed in major releases. Deprecation notices are typically published at least one MINOR release before removal. All deprecations are communicated in advance, either in-software, by mentioning it in the release notes of a minor release, or both.
warning
Users are strongly encouraged to review the release notes and the "Before You Upgrade" article for each version before upgrading, to understand the impact of changes, including feature removals or default behaviour modifications.