The inclusion request: New collection: ravendb.ravendb · ansible-collections/ansible-inclusion · Discussion #80 · GitHub
It’s been reviewed and approved by two SC members.
The default inclusion date is 2025-08-04.
The inclusion request: New collection: ravendb.ravendb · ansible-collections/ansible-inclusion · Discussion #80 · GitHub
It’s been reviewed and approved by two SC members.
The default inclusion date is 2025-08-04.
I approve the inclusion.
The Maintainer was very responsive to suggestion to add docs_fragment + module_utils for common args
I don’t have any general objection against including this collection. But 12.0.0b1 has already been released, and our roadmap states that this means a feature freeze. And:
This includes adding new collections to Ansible 12.0.0; from now on new collections have to wait for 12.1.0 or later.
So I suggest to postpone adding the collection a bit until we’ve released 12.0.0. Which, hopefully, will be only a day later.
@mariolenz Thank you for holding us accountable to the process.
Should we also include it into Ansible 11 now that we’ve extended its lifetime? Or do we only ship collections there that have been already included, but not new ones?
I can’t remember how we handled this for the last “LTS” release (9?) but I tend to not add new collections to 11.
+1 for waiting for 12.1.0 (which will likely be very shortly after 12.0.0 anyway), and +1 for adding it also to the next 11.x.0.