Pavel Korovin <p@tristero.se> writes:
> Dear all,
>
> Ansible project was significantly restructured after v2.9.
> Starting with ansible-2.10, the project was split into the core engine
> (called ansible-base in v2.10, and renamed to ansible-core in v2.11),
> which contains essential code needed to run collections and
> ansible collections, e.g. community.aws, community.vmware etc.
>
> Since v2.10 what is called ansible is a python package which contains selected
> list of ansible collections and depends on ansible-core package:
> https://pypi.org/project/ansible-core/
> https://pypi.org/project/ansible/
> The core enginge and collections have different versioning schemes:
> ansible v3 depends on ansible-core v2.10 and ansible v4 depends on
> ansible-core v2.11.
>
> More on ansible project restructurization:
> https://www.ansible.com/blog/ansible-3.0.0-qa
>
> Ansible Collections Overview:
> https://github.com/ansible-collections/overview
>
> [...]
Has it become vital to move off of Ansible 2.9.x? Currently in Linux
land, specifically when looking at Fedora/CentOS and Ubuntu, they are
all still providing Ansible 2.9.x and I would assume Fedora would be the
first to move off of 2.9.x if there was a pressing need to do so.
In my humble opinion, I think it might be reasonable to continue with
the Ansible 2.9.x branch as users who rely on a newer version can do so
using virtualenv and other such mechanisms.
No comments:
Post a Comment