ansible-build-data VS community-topics

IBM -> RedHat -> Ansible (https://docs.ansible.com/platform.html)

I think the new ansible docs are opaque, and the new "everything is an ansible collection" scheme makes troubleshooting any issues reported by users hundreds of times harder than "the old days"

I keep this (https://github.com/ansible-community/ansible-build-data/blob...) bookmarked because it's the only way to match up what "ansible 8.1.0" (https://pypi.org/project/ansible/8.1.0/) even means since it for damn sure not any of this: https://github.com/ansible/ansible/releases (they used to have a 'release' pinned on that releases tab saying "these are not the droids you are looking for"). I believe I tried asking for them to update the completely erroneous pypi "source code" link to point to that repo and ... well, one can see how well that turned out

➡️ Check Release Notes📦️🗒️ and Ansible 8 Porting Guide for more details.

💽You can install it by running the following command or download the release tarball directly from pypi: pip install ansible==8.0.0a1 --user ➡️Check Release Notes 📦️🗒️ and Ansible 8 Porting Guide for more details!

You can find the current list for Ansible 7 here: https://github.com/ansible-community/ansible-build-data/blob/main/7/ansible-7.build

Check Release Notes📦️🗒️ and Ansible 6 Porting Guide for more details on changes, improvements, new and deprecated features!!

You can find the release announcement on ansible-announce and the changelog on GitHub. Happy automating!

The vmware.vmware_rest collection has been included in Ansible 5. Thanks to everyone involved!

As https://github.com/ansible-community/ansible-build-data/issues/114 showed we should really check the existing collections included in the Ansible package. Some ideas:

Ansible 5.7.0 has been released with updates to 19 of the included Ansible collections! Read the announcement or check out the update changelog to learn more about this new version.

Debian package "ansible" -> called "ansible" on PyPI -> is called "ansible collections" through most of the documentation -> upstream PyPI packages are generated through https://github.com/ansible-community/ansible-build-data

There is a community vote on a new policy for community.general on which ansible-core versions will be supported in new major releases. Basically support for ansible-core versions will be dropped if they were EOL at least a few weeks before the major release. For the upcoming community.general 8.0.0, that means that it will drop support for ansible-core 2.11 and 2.12 and require at least ansible-core 2.13. Details can be found in the associated issue.

As mentioned in The Bullhorn #113, we've opened a community / steering committee vote on declaring ngine_io.exoscale an effectively unmaintained collection and remove it from the Ansible 10 community package. Since then, there has been a new release. As a result, the vote ended with the decision to keep the collection in the community package.

2023-07-12: Community WG meeting, 18:00 UTC (propose topics here)

Hi everyone. We're working on making Ansible community documentation a separate project to ansible/ansible. The purpose is to benefit the Ansible community by decoupling community doc initiatives from core release cycles. This change also removes the Ansible Core team as the gate for other doc related efforts that will meet community needs, such as putting source content for docs.ansible.com under the direct control of the Steering Committee. Overall this change is a first step towards providing greater access and ownership of docs.ansible.com to the Ansible community.

Looking for your feedback on making community docs a separate github project to ansible/ansible, starting with moving /docs from ansible/ansible to ansible/ansible-documentation. See this issue for details.

It looks like the netapp.elementsw collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.elementsw for more information or to announce that you're interested in taking over the maintenance of (a fork of) netapp.elementsw.

The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works.

As mentioned in The Bullhorn #98, we consider netapp.aws an effectively unmaintained collection. Therefore, we've opened a community / steering committee vote on removing it from the Ansible 10 community package.

2023-05-10: Community WG meeting, 18:00 UTC (propose topics here)

Work continues combining several pytest plugins for ansible.