We track upcoming work on Azure Service Operator (ASO) using GitHub Issues.
We target a new release of ASO approximately every two months, though this may vary depending on the amount of work we have planned as well as external factors.
Our current release plan:
| Version | Estimated Release |
|---|---|
| 2.8.0 | Mid June 2024 |
| 2.9.0 | Mid August 2024 |
| 2.10.0 | Mid October 2024 |
Where linked, versions go to a list of feature and bugs that are planned to be included in that release.
Any items note completed in time for one release will be carried over to the next, and may result in us pushing other items to a later release.
Partway through eacha release cycle, we'll review the list of issues assigned to upcoming releases and redistribute issues as needed. This usually involves some issues being moved to later releases.
If you're waiting on a particular resource or feature to be released, please comment on the relevant issue (or create a new issue if there isn't already one tracking the request) to let us know. We'll do our best to keep you updated on progress.
We publish an experimental release on a regular basis, suitable for testing and other non-production use cases. Such releases may not be stable and should not be used in production.
Prior GA releases of ASO v2:
| Version | Release Date | |
|---|---|---|
| 2.7.0 | 25 April 2024 | |
| 2.6.0 | 23 February 2024 | |
| 2.5.0 | 7 December 2023 | (1) |
| 2.4.0 | 14 November 2023 | |
| 2.3.0 | 5 September 2023 | |
| 2.2.0 | 21 July 2023 | |
| 2.1.0 | 2 June 2023 | |
| 2.0.0 | 15 April 2023 |
(1) v2.5.0 had an abbreviated release cycle to get key items out before the 2023/2024 holiday season
We triage new issues weekly and assign most of them to an upcoming release milestone, based on our understanding of priority, complexity, and available resourcing.
Azure Service Operator v1 is no longer under active development and we do not recommend it for new users. Bug and security fixes are still made when necessary to support existing users who are yet to migrate to v2. We do not plan releases of ASO v1 in advance, they are done on an ad-hoc basis as needed.