Proposal for extending `loop_control` will be
created. This will be implemented in Ansible 2.6 (at the
earliest)(gundalow,
16:07:36)
Aggregate will not change for 2.5(gundalow,
16:07:54)
Current thoughts are that a new option under
ths `loop_control` keyword will be created, which will tell Ansible
if that loop should be "optimised" or not(gundalow,
16:08:41)
No changes will be done in 2.5, we may add some
of the missing platform specific modules under the `net_` (platform
agnostic) versions, which will include DI, though again, we are not
going to change anything here(gundalow,
16:12:19)
there are various PRs that need reviewing on
https://github.com/ansible/community/issues/247 (I don't see any
specific questions) The core team will go though those
offline(gundalow,
16:37:28)
ACTION: gundalow will
review the other PRs on
https://github.com/ansible/community/issues/247 and update agenda as
needed(gundalow,
16:37:40)
Ansible 2.5 planning and update(gundalow, 16:38:34)
"roadmap" Networ items for Ansible 2.5 can be
found on https://github.com/ansible/ansible/projects/10(gundalow,
16:39:18)
This was done after feedback from Contributors
Summit SF to give you all better visibility(gundalow,
16:40:21)
if you think something that SHOULD be fixed in
2.5.0 isn't on either of those lists please let us know in this
channel (#ansible-network)(gundalow,
16:42:15)