community.postgresql VS community-topics

The community.postgresql collection released a new version: 3.2.0.

We are happy to announce that the community.mysql collection has found a new maintainer: Felix Hamme (betanummeric on GitHub/Matrix)! He's also already a maintainer of the community.postgresql collection and has a great history of contributions in both. Thanks, Felix, and welcome to the crew!:)

The community.postgresql collection has released two new version: 1.7.9 and 2.4.1. They revert the breaking change accidentally introduced in the previous version (which was intended for a later major release).

The community.postgresql collection version 2.3.1 has been released (changelog). Thanks to vonschultz and hunleyd!

The community.postgresql team has released 1.7.6 as a bugfix release.

We are also happy to announce a new maintainer of the community.postgresql collection - Felix Hamme (betanummeric on GitHub)! Our congratulations, Felix, and thank you for your great contribution in many collections and desire to help!

The community.postgresql maintainers need your feedback! A proposal for formalizing the supported PG versions has been filed here and needs your input. If adopted, the collection will issue major releases yearly and each major release will officially support the five major version of PG supported at that time. We think this will ultimately improve the collection and improve the end user's experience but we need your input. We look forward to hearing from everyone!

Recently, we opened https://github.com/ansible-collections/community.postgresql/issues/276 to discuss formalizing the supported PostgreSQL versions in the community.postgresql collection. This is a big change for the collection and we want to ensure the proposal makes sense for the collection's users. If you use the collection, please review the proposal and add your thumbs up/down, comment, etc. Thanks!

The community.postgresql collection has released 1.7.3 and 2.1.4 to fully deprecate Ansible 2.9/2.10. Thanks to our newest contributor jchancojr and everyone else involved!

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.