Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmaintained collection: Removal from the Ansible Community Package #24

Closed
mariolenz opened this issue Jun 16, 2024 · 6 comments
Closed

Comments

@mariolenz
Copy link

It looks like this collection is effectively unmaintained. According to the current Ansible Community Package Collections Removal Process, we will consider removing it in a future version of the Ansible Community Package. Please see Unmaintained collection: netapp_eseries.santricity for more information.

At least one month after this announcement appears here and on Bullhorn, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 12. Please note that people can still manually install the collection with ansible-galaxy collection install netapp_eseries.santricity even when it has been removed from the Ansible Community Package.

@gundalow
Copy link

@ndswartz Are you still involved with the NetApp collection?

@mcwhiteside
Copy link

mcwhiteside commented Aug 13, 2024

@gundalow - @VuTran007 and I are currently involved with maintaining the NetApp collection.

@gundalow
Copy link

@gundalow - @VuTran007 and I are currently involved with maintaining the NetApp collection.

Thanks folks
Can you please take a look at #23 and get that resolved. If you need help please reply to that GitHub issue

@VuTran007
Copy link
Collaborator

@gundalow - @VuTran007 and I are currently involved with maintaining the NetApp collection.

Thanks folks Can you please take a look at #23 and get that resolved. If you need help please reply to that GitHub issue

Thanks @gundalow. We are looking into it.

@VuTran007
Copy link
Collaborator

@mariolenz and @gundalow

Can we close this issue since Release 1.4.1 resolved the issue in #23?

@mariolenz
Copy link
Author

Closing because I see there has been a new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants