README: clarify what the issue tracker covers #322
Conversation
There was a problem hiding this comment.
We also use issues to track the removal of collections in future major releases. Should we mention this explicitly?
|
Good point! There's also adding of collections (if it can't be done directly with a PR, for example due to feature freezes for new major releases) and renaming of collections. I've added all three. |
|
I added https://pypi.org/project/ansible/#reporting-issues earlier this year to make it clearer where to report issues, but I definitely like the idea of defining the scope of this repo's issue tracker specifically. |
Co-authored-by: Maxwell G <maxwell@gtmx.me>
I think we should also mention this repo's issue tracker in that paragraph. |
I added a short blurb about the ansible-build-data tracker to the README in ansible-community/antsibull-build#554. |
Co-authored-by: Maxwell G <maxwell@gtmx.me>
|
Is there anything open or can we merge? Or should wait for more feedback? |
|
It's probably a good idea to see whether @oraNod and/or @samccann have any feedback on this tomorrow. It's probably a good idea to get this merged soon (similar to ansible-community/antsibull-build#554). |
|
@mariolenz @gotmax23 @samccann thanks for your reviews and improvements! |
* ansible-readme.rst: mention the ansible-build-data issue tracker Ref: ansible-community/ansible-build-data#322 (comment) * ansible-readme.rst: change link to ansible-build-data tracker
In the forum, it was was remarked that it is not clear what kind of issues can and should be created in this repository's issue tracker. This PR adds a section at the top of the README with some details on what can (and what should not be) handled here.
Ref: https://forum.ansible.com/t/trying-to-get-a-message-to-the-right-team-about-a-8-6-release-issue/2274/3