overview VS community.postgresql

As mentioned in last week's Bullhorn issue, cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. A week has passed since the community-topics issue was filed and other SC members confirmed the violation, so a vote has been started (vote ends on 2022-12-16).

cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. Please see community-topics#168 for more information.

The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.

The Ansible Community Steering Committee has approved a change to the Collection Requirements re. SCM and release requirements. Collections were always required to tag releases, but we have clarified what tagging actually means. We have also explicitly stated that "collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release." Please see the full change for more information.

We are happy to announce that the ibm.spectrum_virtualize collection has been included in the ansible community package. Thanks to everyone who helped review the collection and thanks to the maintainers for submitting the collection and making it satisfy the Collection requirements!

How? Copy the Review checklist into a discussion and go through it. See the complete example.

We've recently signed off on that process, which you can review here.

Your votes needed! Proposal: merge and adopt the procedures defined in Describe how collections can be removed from the Ansible package. Please vote in this issue (and not in the PR). The vote will close on 2022-04-27.

Pros: - Motivation for developers to create new collections which can become a part of Ansible package ("so popular and important in IT world", etc). - Motivation to create content satisfying the collection requirements. - Motivation to maintain included collections to avoid kicking them out from the package "I can't show off with my collection any more..:(" - ...(suggest yours)

We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details

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!