DRAFT: Project Plan

[gundalow]

Project Plan

Detail the remaining steps to get us to Ansible 2.10.

This is just a proposal, the order and contents of the milestones may change.

As a reminder ansible-base (gh/ansible/ansible) has it's own roadmap

How

1. Define the buckets
2. Ensure every thing in https://github.com/orgs/ansible-collections/projects/1 is an issue (not a note)
3. Create bucket labels in all repos
4. Assign buck labels
5. Issue titles to include [1d] ie [3d] Migrated Modules Messaging #48
6. Create filter links for Project Board for each bucket. Filter for no bucket labels

bucket1: Each Collection open for contributors

bucket2: Each collection published to Galaxy

AIM: Get the Collections into a state so people can test and give us feedback

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket2

• Foreach collection included in ansible
  • Automated Publishing on Git Tag for all community. collections
  • README
  • galaxy.yml (tags, dependencies, etc)

bucket3: Issues and PRs from a/a closed

AIM: Allow people to contribute

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket3

• Clear directions on what to do next
• Correctly direct people to their new location
  • Collections still to move: a10, AVI, Dell, Infoblox

bucket4: Versioning, deprecation

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket4

• What
• How
• Actions
• CI to enforce correct structure

ansible/ansible#66920

bucket5 pre-release ansible-2.10

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket5

AIM: A basic build of ansible-2.10 on PyPi to allow people to check that the new process works. Allows us to confirm that Ansible 2.9 playbooks work without modification

FIXME: Should this be split into multiple milestones

• collection redirection/tombstoning collection routing ansible/ansible#67684
• Collection loader loads and executes module code, causing problems with old libraries in path Collection loader loads and executes module code, causing problems with old libraries in path ansible/ansible#68701
• Collection loader: importing from module_utils/foo/init.py does not work Collection loader: importing from module_utils/foo/__init__.py does not work ansible/ansible#68872
• Requires ansible-base build on PyPi

bucket6: No more content shuffling

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket6

• No more moving content from community.general or community.network into dedicated collections
• Validate that ansible-base's routing and botmeta is correct
• validate acd.in
• Ensure deprecated content is in the right collection

bucket7: Developer & Contributor guides

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket7

bucket8: feature freeze for Collections

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket8

• No new modules or plugins in any collection
• No new features

...

bucket9: Docs for each collection

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket9

bucket10: ansible published to all Packagers

https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket10

Other bits

• CI improvements
• Governance
• Build questions
  • Single vs multiple packages
  • Launchpad PPA (need to find a contact: relrod has been talking to a Debian maintainer)

[gundalow]

Old, no longer needed.

For the plan see https://github.com/orgs/ansible-collections/projects/1 (which is currently being tidied up)