Ansible project 6.0
This release schedule includes dates for the ansible package, with a few dates for the ansible-core package as well. All dates are subject to change. See the ansible-core 2.13 Roadmap for the most recent updates on
ansible-core feature freeze, stable-2.13 branch created.
Start of ansible-core 2.13 betas (biweekly, as needed).
Ansible-6.0.0 alpha1 (roughly biweekly
ansiblealphas timed to coincide with
Community Meeting topic: List any backwards incompatible collection releases that beta1 should try to accommodate.
First ansible-core release candidate.
Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline.
Last day for collections to make backwards incompatible releases that will be accepted into Ansible-6. This includes adding new collections to Ansible 6.0.0; from now on new collections have to wait for 6.1.0 or later.
Create the ansible-build-data directory and files for Ansible-7.
Ansible-6.0.0 beta1 – feature freeze 1 (weekly beta releases; collection owners and interested users should test for bugs).
Release of Ansible-6.1.0 (bugfix + compatible features: every three weeks.)
No new modules or major features accepted after this date. In practice, this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community.crypto 2.3.0; Ansible-6.0.0 could ship with community.crypto 2.3.1. It would not ship with community.crypto 2.4.0.
After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date.
Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the Community IRC meeting agenda.
Breaking changes will be introduced in Ansible 6.0.0, although we encourage the use of deprecation periods that will show up in at least one Ansible release before the breaking change happens, this is not guaranteed.
Ansible 6.x minor releases will occur approximately every three weeks if changes to collections have been made or if it is deemed necessary to force an upgrade to a later ansible-core-2.13.x. Ansible 6.x minor releases may contain new features but not backwards incompatibilities. In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-6.0.0 ships with community.crypto 2.3.0; Ansible-6.1.0 may ship with community.crypto 2.4.0 but would not ship with community.crypto 3.0.0.
Minor releases will stop when Ansible-7 is released. See the Release and Maintenance Page for more information.
For more information, reach out on a mailing list or a chat channel - see Communicating with the Ansible community for more details.
More details can be found in the community-topics planning issue.
Remove compatibility code which prevents parallel install of Ansible 6 with Ansible 2.9 or ansible-base 2.10
Stop installing files (such as tests and development artifacts like editor configs) we have no use for
Ship Python wheels (as ansible-core 2.13 will likely also do) to improve installation performance