Greetings,
In an effort to provide more stability in our minor releases, the Ansible Core
team is planning to start publishing release-candidates for minor versions of
Ansible 2.8, Ansible 2.9, and ansible-base 2.10.
When we start publishing these, our release cycle will move to a 4-week cadence:
Every 4 weeks, an RC will be published, and will be followed one week later by a
stable release.
These RCs:
- Will be published every 4 weeks, as noted above
- Will appear on pypi
- Will appear as .tar.gz files on releases.ansible.com
- Will NOT be published as RPMs on releases.ansible.com
- Will NOT be available through our Launchpad PPA
Our hope is that these RCs will provide a short amount of time for users and
community members to test an impending release with their playbooks (or in their
CI setup) before the release becomes final, and to report any issues they have
found so that they may be fixed (or so that the breaking change may be
reverted as necessary). In the event that a regression is found, it will be
reviewed on a case-by-case basis, and fixed or reverted as necessary. We do not
plan to publish more than one RC per minor release at this time.
We plan to start the RC process with ansible-base 2.10.1, and will start it
shortly after for the Ansible 2.8 and 2.9 series. Thus, our timeline to start
these RCs looks like the following (subject to change):
- 31 August 2020:
ansible-base 2.10.1rc1
ansible 2.9.13
ansible 2.8.15
- 7 September 2020:
ansible-base 2.10.1
- 28 September 2020:
ansible-base 2.10.2rc1
ansible 2.9.14rc1
ansible 2.8.16rc1
- 5 October 2020:
ansible-base 2.10.2
ansible 2.9.14
ansible 2.8.16
We will announce the availability of these RCs to the devel mailing list.
We hope that this helps to improve the stability of Ansible and ansible-base
going forward. We welcome and encourage feedback from the community and are
always looking to refine our processes to make Ansible and ansible-base as solid
as possible.
Rick / Ansible Release Engineering