Collection migration tracking

[felixfontein]

Instead of always updating this comment, let's track content moving in this issue. I'll create one comment per collection, and that comment can be updated and eventually checked off or hidden.

When a collection is ready to be added to the current stable release, we have to add it to both ansible.in (just the collection name) and ansible-2.10.build (collection name and version range). Eventually we'll add code to antsibull to do this. In the meantime, here's a sample PR that shows what needs to be changed:

https://github.com/ansible-community/ansible-build-data/pull/39/files

[felixfontein]

• infoblox.nios_modules
  • Repository: https://github.com/infobloxopen/infoblox-ansible
  • Initial release
  • Released 1.0.0
  • Included in Ansible 2.10: tracking in Inclusion in Ansible 2.10.x infobloxopen/infoblox-ansible#24
  • Inclusion in Ansible 4.0.0 5.0.0: Infoblox.nios_modules inclusion ansible-inclusion#11
  • Removal announcement PR
  • Removal PR (instead: deprecation PR)

[felixfontein]

PR to update Ansible's routing table for ansible-core 2.11: ansible/ansible#73046

[felixfontein]

Since only infoblox.nios_modules is left, and it's not fully clear how that will progress, I think we can close this.

[gundalow]

Since only infoblox.nios_modules is left, and it's not fully clear how that will progress, I think we can close this.

Agreed we should close.

[felixfontein]

infoblox.nios_modules has been added to Ansible, and the migration process has been set into motion (ansible-collections/community.general#3592).