Dear all, just a quick reminder: if you haven't already done so, please use the unfreeze to add a **changelog** to your collection!
The preferred way is to use antsibull-changelog. You can read more about that at the following links: * https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html#generating-changelogs-for-a-collection * https://github.com/ansible-community/antsibull-changelog/blob/main/docs/changelogs.rst We prefer this because it allows us to integrate your collection's changelog in the combined Ansible 2.10 changelog and porting guide. The current combined changelog can be found at: https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst The current combined porting guide can be found at: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.10.html (All 2.10.0 alpha/beta/rc entries will be collapsed to a final 2.10.0 entry once that is released, same as for the Ansible-base changelog.) If you prefer to write a changelog manually, or use another software which does not allow to create changelogs/changelog.yaml in your collection, please create an issue in https://github.com/ansible-community/ansible-build-data/ and tell us the URL of your changelog. Thanks for your attention and best regards, Felix Fontein -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/20200827211256.639d2609%40rovaniemi.
