Greetings all, in preparation for the beta1 release on the first of
September, the ansible package is now feature frozen.
What does that mean exactly?
The main goal of the 2.10.x package is to give end users a smooth
transition from the monolitihic approach to content in ansible-2.9 to
the ecosystem of of content approach in ansible-2.10. We do that by
pulling together a set of ansible collections which contain all of the
plugins which were a part of ansible-2.9 into a single tarball and
distribute that on pypi.
When we construct the ansible-2.10 package, we place specific versions
of the collections into the ansible tarball. Since collections are
supposed to use semantic versioning to describe what sorts of changes
are in the new version, what we've done is record the latest versions
of the collections we're pulling in as of today. As we build
ansible-2.10.0beta1, rc1, and final, we will update the collection
that is included if its semantic version states that it is compatible
and contains no new features.
An example:
Today we checked galaxy.ansible.com and found that
community-crypto-1.1.0 is the latest version of that collection. So
when we ship ansible-2.10.0beta1 and ansible-2.10.0rc1, we will take
the latest version number greater than or equal to 1.1.0 and less than
1.2.0.
The feature freeze will last until 2.10.0 final has been released.
After that, the ansible package will allow new features as long as
they're backwards compatible. Backwards incompatible changes would
have to wait until ansible-2.11.0. So if community.crypto updated to
1.2.0, that would ship with ansible-2.10.1. If it updated to 2.0.0,
that would wait until ansible-2.11.0 shipped.
Thanks for all the hard work you all have done to get us this far!
-Toshio