Hi folks -
With Ansible modules and other plugins moving to collections, we need to decide how to handle changelogs and porting guides. In prior releases, changelogs and porting guides were handled directly in PRs, because all content lived in, and was released in the ansible/ansible GitHub repo. In 2.10, content has moved to separate collections that can update more frequently than the base Ansible code will. Ansible will provide an Ansible Community Distribution (ACD) - a set of collections that gives users the “batteries included” experience they had in Ansible 2.9. Each version of ACD will contain the most up-to-date version of each component collection. We would like to include a consolidated changelog for each ACD release. So we have a couple of problems to solve: - what approach should collection owners follow to provide changelog and porting guide information for end users? - What should ACD provide for end users so they can understand what has changed in the collections within the ACD? So we'd like you to consider these problems, and vote/comment on the issue tracking this discussion: https://github.com/ansible-collections/overview/issues/18#issuecomment-608473331 Thanks for your help! -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/379dca14-8de4-44ce-90ef-e8d72883d0d3%40googlegroups.com.
