Ansible project 5.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 core_roadmap_2_12 for the most recent updates on
New Collections can be reviewed for inclusion in Ansible 5. Submit a request to include a new collection in this GitHub Discussion.
ansible-core feature freeze.
Start of ansible-core 2.12 betas (weekly, as needed).
Ansible-5.0.0 alpha1 (roughly biweekly
ansiblealphas timed to coincide with
Last day for new collections to be submitted for inclusion in Ansible-5. Collections MUST be reviewed and approved before being included. There is no guarantee that we will review every collection. The earlier your collection is submitted, the more likely it will be that your collection will be reviewed and the necessary feedback can be addressed in time for inclusion.
Community Meeting topic: List any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate.
First ansible-core release candidate, stable-2.12 branch created.
Last day for new collections to be reviewed and approved for inclusion in Ansible-5.
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-5.
Create the ansible-build-data directory and files for Ansible-6. New collection approvals will target this.
Ansible-5.0.0 beta1 – feature freeze 1 (weekly beta releases; collection owners and interested users should test for bugs).
Ansible-5.0.0 rc1 2 3 (weekly release candidates as needed; test and alert us to any blocker bugs). Blocker bugs will slip release.
Release of Ansible-5.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.1.0; Ansible-5.0.0 could ship with community.crypto 2.1.1. It would not ship with community.crypto 2.2.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 5.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 minor releases
Ansible 5.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.12.x. Ansible 5.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-5.0.0 ships with community.crypto 2.1.0; Ansible-5.1.0 may ship with community.crypto 2.2.0 but would not ship with community.crypto 3.0.0.
Minor releases will stop when Ansible-6 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 for more details.