The weekly community meeting has moved from
Wednesdays at 18:00 UTC to Wednesdays at 19:00 UTC so it stays at
2:00 p.m. EST / 8:00 p.m. CET now that DST / summer time is ending.
The meeting location – #ansible-community on IRC and
#community:ansible.com on Matrix – remains the same. As always, all
interested community members are welcome!(gotmax,
19:02:39)
Ansible 7.0.0b1 was released this week:
https://groups.google.com/g/ansible-devel/c/vmnxxW7gCco(gotmax[m],
19:04:14)
Ansible 6.6.0 was released this week:
https://groups.google.com/g/ansible-devel/c/Kr7YjUN33pM(gotmax[m],
19:04:33)
ansible-core 2.14.0 was released this week:
https://groups.google.com/g/ansible-devel/c/G5TB9zNKNDk(gotmax[m],
19:05:09)
ansible-core 2.13.6 was relased this week:
https://groups.google.com/g/ansible-devel/c/uDceTGqyXeE(gotmax[m],
19:05:22)
Ansible 7.0.0rc1 will happen next week, and
depending on the feedback Ansible 7.0.0 will either be released one
or two week afterwards, with a potential rc2 inbetween(felixfontein,
19:05:29)
We've merged the removal_from_ansible policy
[change](https://github.com/ansible-collections/overview/commit/4d5ab3277fc537f4fae084362b15e2422b2f8818).
Collections with unresolved Collection Requirements violations are
now subject to removal from the Ansible package.(gotmax[m],
19:08:20)
How to mark private plugins in a collection #154(gotmax[m], 19:08:46)
There's some agreement that there should be a
standardized way to mark content in a collection as private. If we
proceed, the next steps are to decide whether to use the `_` prefix
approach or a metadata based approach, discuss this with core, and
get the changes into ansible-core and antsibull-docs to hide private
plugins from `ansible-doc -l` and the docsite.(gotmax[m],
19:40:22)