On 4/7/22 21:30, 'Felix Fontein' via Ansible Project wrote:
On 4/7/22 07:40, 'Felix Fontein' via Ansible Project wrote:
The *product/distribution* Ansible consists of both `ansible` and
the `ansible-core` PyPi packages. The *docsite*
(https://docs.ansible.com/ansible/latest/) describes both. The
*changelog* describes both. The *porting guide* also describes both.
That is why our announcement is written as it is. We are talking
about the product/distribution.
The PyPi package `ansible` does indeed depend on `ansible-core` and
does not contain it. But that it is split up into two PyPi packages
is an **implementation detail** to Ansible users.
...I have to agree with Nico that the wording and the versioning also
confused me in the beginning.
Ansible users like me are interested to know whether they should
update or not, especially in the case of security fixes.
Doing pip upgrade on PyPI package 'ansible' is easy because it might
have a dependency on a newer version of 'ansible-core' which gets
pulled in automatically. That's fine.
But if there's an important security fix only in ansible-core Ansible
users have to be aware to explicitly invoke
pip install --upgrade ansible-core
to get the updates. So this "implementation detail" is indeed quite
relevant to Ansible users who want to properly maintain their
controller.
That's indeed a problem (especially since `pip install --upgrade
ansible` will not upgrade dependencies when `ansible` is already at the
latest version). One way to (partially) fix this would be to make sure
that Ansible is always released at most a day after ansible-core has
been released. Right now, the delay can be up to two weeks, which is
definitely too long.
Also I don't mind to update the release template by adding more
information on how ansible-core is 'contained' in ansible. I'm mainly
against completely rewriting it with different language which is more
technically correct, but less helpful and doesn't work together with
the other things (changelog, porting guide, docsite).
I guess that Ansible users are normally system admins I'd expect to be
used to dealing with multiple packages with interdependent version
numbers. So technically correct language is probably the most useful
form for this audience.
Ciao, Michael.
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/3b52157e-b98e-838c-8718-351329f7af46%40stroeder.com.
