Sandra McCann

@Andersson007 - can you evaluate this to see if https://github.com/ansible/ansible-documentation/issues/676#issuecomment-1771605945 matches your understanding and perhaps recommend where we can clarify this in the docs?

@Andersson007 Thanks and sorry folks it took me so long to get back to this one. I like your approach. Can you open the two topics on the forum and...

Thanks @Andersson007 - I opened the following topics on the forum. Folks- please review and comment there so we can get the docs in the right place for these two...

PRs welcome @jorhett :-) Ansible documentation is community created and community maintained so every bit helps us become more accurate.

What's the next step here? We have ...2.5 weeks before this becomes another manual tagging effort for the next core release...

on the porting guide - frequently, the porting guide PRs get merged AFTER a release has happened. Historically, we haven't held up any release to pypi because a porting guide...

@gotmax23 thanks for doing this manually... @mattclay 's https://github.com/ansible/ansible-documentation/issues/66#issuecomment-1633284160 makes it sounds like we can automate this somehow? Or is the only automation option for these tags have to be...

This should be in the antsibull-docs repo. I can't 'transfer' across github orgs so closing this in favor of https://github.com/ansible-community/antsibull-docs/issues/235

ah sorry about the close/duplication.

So looking at the table, my personal opinion is no change is needed. The support is clear (and even color-coded). I don't find it confusing.