The core team has mostly only released packages to pypi, the Ansible
site and a PPA, never to the downstream distributions. We stopped
adding packages to our site as they were not really used and most of
the distributions had their own packages already. It made more sense
when we were still a new project that most distros didn't know about,
much less included in their repos, that is not the case anymore.
Especially now that it is almost trivial to create your own package if
needed with existing tools, just point at pypi or github for the
sources.

I'm not sure where you get your numbers about 2.9 being the 'current'
used by most, it's not even the 'current' available in many distros:

Gentoo: ansible-base 2.11.6 (this is really ansible-core but i think
packager didn't want to deal with name changes every version)
Arch: ansilbe 4.7.0-1 (community package, which includes ansbile-core 2.11.6.)
ubuntu (20.04 focal: 2.9.6
ubuntu (21.04)  hirsute: 2.10.7 (which is ansible-base)
ubuntu (21.10) impish:  2.10.7
debian bullseye: 2.10.7
freebsd 13: 2.9.23  (14 is due soon, not sure what they are using yet)

Those are just the ones I have at hand, I'm pretty sure you'll find
others with 2.9, 2.10 and 2.11 just depending on how aggressive the
distros are at updating versions and their own release schedules. As
for @sivel, he responded mostly with RH/fedora/Centos as that is what
he mostly deals with daily, I deal with the ones above, so that is
what I can respond to easily.

In the end the decision about not updating 2.9 comes to a policy,
which was created due to limited core resources, we cannot maintain X
versions forever, specially since the value of X changes depending on
who is asking, I still get requests to update 1.7 and 1.9.  We also
cannot revise it any time a distro chooses to stay on a specific
version (for example,Debian was pinning a version due to licensing in
some files not passing their tests), it just does not scale.

This policy has been clearly stated and in place for many years (you
can check the versioned documentation, it is in git after all) and I'm
confident that our record would speak against any perceived bias, as
long as you are willing to examine all the facts.


----------
Brian Coca

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/CACVha7e%2BTQ48YVNHt_5u3DU8sD9oGYpwf4mG7a29NMXWR1rXRQ%40mail.gmail.com.

Reply via email to