[Vote ended on 2025/06/22] Possibly unmaintained collection: cisco.ise

Project Discussions
, ,
21

Just to clarify - this is also a RH-certified collection, and ansible-2.15 doesn’t EOL for I think another year or so at the product level.

1 Like
22

I prepared a PR to implement this: [WIP] Remove cisco.ise from Ansible 12 by felixfontein · Pull Request #559 · ansible-community/ansible-build-data · GitHub

While working on that, I noticed that Ansible Community Package Collections Removal Process — Ansible Community Documentation does not link to Ansible Collection Policies - Ansible Package Release Management. If someone has time, feel free to create a PR to update that page accordingly :slight_smile:

1 Like
23

I closed the vote [Vote ended on 2025/06/22] Possibly unmaintained collection: cisco.ise - #10 by felixfontein. The result is clear: there are 8 SC votes for removing cisco.ise, and 2 community votes for removing it. There were no votes against removing it.

So unless the collection is updated and sufficiently tested before in time before feature freeze, it will no longer be part of Ansible 12.

1 Like
24

I merged the removal PR, and created another PR that announces the removal from Ansible 12 in Ansible 11.8.0: [WIP] Announce removal of cisco.ise from Ansible 12 in Ansible 11 by felixfontein · Pull Request #560 · ansible-community/ansible-build-data · GitHub

My suggestion would be to merge it on the day of the Ansible 11.8.0 release in case nothing happened so far with cisco.ise. Since Ansible 12’s feature freeze is a week later, no activity until then is a good indication that nothing will happen in time and the collection will not be re-added to Ansible 12 in time for the feature freeze.

1 Like