Ansible project 3.0¶
This release schedule includes dates for the ansible package, with a few dates for the ansible-base package as well. All dates are subject to change. Ansible 3.x.x includes
ansible-base 2.10. See Ansible-base 2.10 for the most recent updates on
Ansible is switching from its traditional versioning scheme to semantic versioning starting with this release. So this version is 3.0.0 instead of 2.11.0.
Finalize rules for net-new collections submitted for the ansible release.
Final day for new collections to be reviewed and approved. They MUST be submitted prior to this to give reviewers a chance to look them over and for collection owners to fix any problems.
Ansible-3.0.0-beta1 – feature freeze 1
Release of Ansible-3.0.0
Release of Ansible-3.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-3.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 may be introduced in Ansible 3.0.0, although we encourage collection owners to use deprecation periods that will show up in at least one Ansible release before the breaking change happens.
Ansible 3.x.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-base-2.10.x. Ansible 3.x.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-3.0.0 ships with community-crypto-2.1.0; Ansible-3.1.0 may ship with community-crypto-2.2.0 but would not ship with community-crypto-3.0.0).
For more information, reach out on a mailing list or an IRC channel - see Communicating for more details.