1 year ago

In today’s fast moving world, schedule driven, incremental releases may not be what customers are looking for. After gathering input from both external and internal customers, there is a definite appetite for more content driven releases.

When a new version was needed for ansible-core, ansible-runner or receptor or any other components (Ansible Automation Platform comes with close to 200 packages), should we release now and trigger a new z-stream release, wait for the next product z-stream release, release nonetheless and not worry about the “point in time” perspective?

Since the Ansible Automation Platform 2.3 release, in less than two months, the Ansible engineering team has released more than 10 updates across different components to ensure we are meeting our customers' needs even faster than ever.

As a customer, it means there is no Ansible Automation Platform 2.3.0 and there will be no Ansible Automation Platform 2.3.1, there is only Ansible Automation Platform 2.3.