# \[Vote ended on 2025-06-13\] Collection requirements: declare that Galaxy artifacts must not be deleted once they appear in Ansible releases

**URL:** <https://forum.ansible.com/t/vote-ended-on-2025-06-13-collection-requirements-declare-that-galaxy-artifacts-must-not-be-deleted-once-they-appear-in-ansible-releases/43132>\
**Category:** Project Discussions\
**Tags:** release-management, community-wg, galaxy-ng\
**Created:** [June 3, 2025, 1:34pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-06-13-collection-requirements-declare-that-galaxy-artifacts-must-not-be-deleted-once-they-appear-in-ansible-releases/43132 "2025-06-03T13:34:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [June 9, 2025, 1:45am UTC](https://forum.ansible.com/t/vote-ended-on-2025-06-13-collection-requirements-declare-that-galaxy-artifacts-must-not-be-deleted-once-they-appear-in-ansible-releases/43132/9 "2025-06-09T01:45:39Z")

</div>

I will abstain myself from this one - as mentioned in other discussions, I believe ~~herding the cats of~~ maintaining the ansible community package brings more hassle than benefits, but that’s my opinion, and to me this particular discussion illustrates the point.

Should we start adding the “no option” as an alternative to the polls? I feel compelled to write something to show that I have seen the poll and have taken action on it (even if my action is no action), but I sound like a broken record.

---

_[View the full topic](https://forum.ansible.com/t/vote-ended-on-2025-06-13-collection-requirements-declare-that-galaxy-artifacts-must-not-be-deleted-once-they-appear-in-ansible-releases/43132)._