-
Notifications
You must be signed in to change notification settings - Fork 9
Inclusion candidates for Ansible 5 #32
Comments
I've just reviewed |
I've just reviewd |
We voted on the inclusion of community.ciscosmb and community.dns in today's meeting (https://meetbot.fedoraproject.org/ansible-community/2021-09-15/ansible_community_meeting.2021-09-15-18.00.html) and accepted both for inclusion in Ansible 5. |
Just a minor status update before today's meeting. Inclusion candidates that have at least two positive reviews are:
I think we can vote about their inclusion today. I also went over all of the candidates and updated their statuses. Consult the summary at the top of the issue for more details. |
Today we voted on cisco.ise and approved it for inclusion. Unfortunately there was no other collection to vote on, since we were either missing reviews, or there were open issues that need to be addressed by the maintainers. |
Since we can incorporate collections "once they are done", I don't think we need this tracking issue anymore. @tadeboro thanks for your work on this! |
Summary
This issue contains high-level information about the inclusion process of each candidate. Feel free to edit as things progress.
Already accepted collections
1. cisco.dnac - no reviews yet
2. equnix.metal - unresolved issues
3. vmware.vmware_rest - unresolved issues
cloud.common
needs to make into Ansible 5).4. trendmicro.deepsec - unresolved issues
5. networktocode.nautobot - needs another review
6. cisco.ise - needs action from reviever
7. dellemc.unity - unresolved issues
8. dellemc.powerflex - unresolved issues
The text was updated successfully, but these errors were encountered: