# Opening issues against all collections in Ansible for core-2.19 template testing

**URL:** <https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678>\
**Category:** Collection Development\
**Tags:** templating, community-wg\
**Created:** [April 11, 2025, 1:44pm UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678 "2025-04-11T13:44:07Z")\
**Posts on this page:** 4\
**Page:** 2

<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:** [April 23, 2025, 6:21pm UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678/21 "2025-04-23T18:21:26Z")

</div>

> [@samccann](#):
>
> You can choose to test against the `stable-2.19` branch, the `milestone` branch, or the pre-release/released versions of `ansible-core 2.19` available on [Pypi](https://pypi.org/project/ansible-core/#history).

Why not add `devel` here? In the end it doesn’t matter whether a collection uses `devel` (current), `stable-2.19` (up to a week old), or `milestone` (potentially way older - personally I would not use that one, since it won’t get bugfixes for some weeks).

> You can choose to test against the `stable-2.19` branch, the `devel` branch, the `milestone` branch, or the pre-release/released versions of `ansible-core 2.19` available on [Pypi](https://pypi.org/project/ansible-core/#history).

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [April 24, 2025, 2:39pm UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678/22 "2025-04-24T14:39:42Z")

</div>

updated the text with devel, thanks! Will run the script probably tomorrow.

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [April 25, 2025, 6:17pm UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678/23 "2025-04-25T18:17:31Z")

</div>

Opened the issues - tracking them all here. There are a handful that have no issues enabled, and a few archived ones that I’m not sure what to do about. Listed [here](https://github.com/ansible-community/ansible-build-data/issues/538#issuecomment-2831104094).

---

<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:** [April 26, 2025, 9:30am UTC](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678/24 "2025-04-26T09:30:59Z")

</div>

As @felixfontein pointed out, the [archived ones have been removed from The Ansible Community Package](https://github.com/ansible-community/ansible-build-data/issues/538#issuecomment-2831274973), anyway. So let’s ignore them.

[Previous page](https://forum.ansible.com/t/opening-issues-against-all-collections-in-ansible-for-core-2-19-template-testing/41678.md?page=1)