-
Notifications
You must be signed in to change notification settings - Fork 35
Description
Checklist
- I have verified this is the correct repository for opening this issue.
- I have verified no other issues exist related to my request.
Is Your Feature Request Related To A Problem? Please describe.
I'm from the Ansible Community Steering Committee and try to keep the Ansible Community Package (ACP) healthy by trying to identify and remove unmaintained collections. This collection turns up on my list of possibly unmaintained collections in Ansible 13 because there hasn't been a new release since Oct 1, 2024.
However, I see that there have been a number of commits here since then. Honestly, I don't know what to do about this collection. You're working on it, so it's not unmaintained. On the other hand, there hasn't been a new release since 2024. And this doesn't look too good to me.
So my question is: What's the reason for not doing a new release? After all, the work you're doing here fixing bugs and implementing new features seems somewhat wasted if you don't make it available to your users by shipping a new release. So please consider doing a new release π
Describe The Solution. Why is it needed?
Well, I'd like to see a new release π€·
User Story
The user story is quite simple: We don't want to have outdated collections in ACP. And 2024 looks pretty outdated to me.
Additional Context
I've already asked about a new release here but never got an answer.
Acceptance Criteria
No response
Related Issues
No response