Hi everyone, just getting caught up on forum posts. Thanks for starting the discussion, @samccann. Here are some suggestions about the proposed text:
the draft porting guide.
Ideally, we could have this merged before creating these issues now that the Core change has been merged so we don’t need to link to draft PRs in the announcement,
You can find advice from your peers at Making a collection compatible with data tagging.
Maybe “fellow maintainers” instead of “peers”? “Peers” seems a bit formal to me.
This issue is focused on ensuring you have verified your collection works with ansible-core devel in order to remain included in Ansible 12 community package.
This (and other text) implies that this is a requirement to remain included in the package, but I think we need to be more up-front and explicit (but obviously not overly harsh or rude), as it’s one of the most fundamental inclusion requirements that the collections included in an Ansible version are actually functional and compatible with its associated Core version.