# \[Default date 2025-08-04\] Collection inclusion: include ravendb.ravendb in the Ansible community package

**URL:** <https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150>\
**Category:** Project Discussions\
**Tags:** resolved, community-wg\
**Created:** [July 28, 2025, 12:11pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150 "2025-07-28T12:11:08Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [July 28, 2025, 12:11pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/1 "2025-07-28T12:11:09Z")

</div>

The inclusion request: [New collection: ravendb.ravendb · ansible-collections/ansible-inclusion · Discussion #80 · GitHub](https://github.com/ansible-collections/ansible-inclusion/discussions/80)

It’s been reviewed and approved by two SC members.

The default inclusion date is 2025-08-04.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 28, 2025, 12:27pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/2 "2025-07-28T12:27:01Z")

</div>

I approve the inclusion.

The Maintainer was very responsive to [suggestion to add docs\_fragment + module\_utils for common args](https://github.com/ravendb/ansible-collection-ravendb/pull/10)

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [July 28, 2025, 3:18pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/3 "2025-07-28T15:18:38Z")

</div>

I don’t have any general objection against including this collection. But 12.0.0b1 has already been released, and our [roadmap](https://ansible.readthedocs.io/projects/ansible/devel/roadmap/COLLECTIONS_12.html) 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.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 28, 2025, 3:35pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/4 "2025-07-28T15:35:29Z")

</div>

> [@mariolenz](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [July 28, 2025, 5:23pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/5 "2025-07-28T17:23:19Z")

</div>

Should we also include it into Ansible 11 now that we’ve extended its [lifetime](https://forum.ansible.com/t/40851)? 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.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [July 28, 2025, 5:48pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/6 "2025-07-28T17:48:02Z")

</div>

+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.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 5, 2025, 4:09am UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/7 "2025-08-05T04:09:06Z")

</div>

When looking at the collection I saw that they’re running the sanity tests without `--docker`, but with `--python`, which is almost always a bad idea: [New collection: ravendb.ravendb · ansible-collections/ansible-inclusion · Discussion #80 · GitHub](https://github.com/ansible-collections/ansible-inclusion/discussions/80#discussioncomment-13998286).

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [August 5, 2025, 5:41am UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/8 "2025-08-05T05:41:24Z")

</div>

I also noticed a more severe issue — i.e., not testing against ansible-core 2.19 — with unit and integration tests that I pointed out in [New collection: ravendb.ravendb · ansible-collections/ansible-inclusion · Discussion #80 · GitHub](https://github.com/ansible-collections/ansible-inclusion/discussions/80#discussioncomment-13999063). I propose we block the inclusion until these testing issues are fixed.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [August 5, 2025, 2:48pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/9 "2025-08-05T14:48:45Z")

</div>

[RavenDB-24201: update CI](https://github.com/ravendb/ansible-collection-ravendb/pull/13) looks promising. But I agree, let’s wait until this PR is merged before adding the collection.

Maybe someone who is more into CI stuff than I am could have a look at this and give an opinion, though.

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [August 25, 2025, 8:31am UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/10 "2025-08-25T08:31:26Z")

</div>

It’s highly recommended, but I don’t think unit and integration testing is a requirement, so it imo shouldn’t be a blocker.  
Anyway, what is the status of the inclusion? Should we mark this issue as `resolved`?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 25, 2025, 10:07am UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/11 "2025-08-25T10:07:03Z")

</div>

> <https://github.com/ansible-community/ansible-build-data/pull/579#issuecomment-3207539945>
>
> Then my suggestion would be to wait until 12.0.0 is out before merging, unless 1…1.10.0 happens earlier, in which case we'd split this PR up into one for Ansible 11 and one for Ansible 12, so that ravendb.ravendb will definitely be included in Ansible 11.10.0, the next Ansible 11 release. Is that OK for everyone?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 27, 2025, 7:32pm UTC](https://forum.ansible.com/t/default-date-2025-08-04-collection-inclusion-include-ravendb-ravendb-in-the-ansible-community-package/44150/12 "2025-08-27T19:32:34Z")

</div>

I just merged the PR that adds it to the next Ansible 11 release. The PR for Ansible 12 will get merged once 12.0.0 is out.
