Ansible has three doc sets it tracks:

• Ansible-core releases: see ansible-core 2.14 for an example GitHub tracking issue for the core release. This publishes to https://docs.ansible.com/ansible-core/devel/index.html
• Ansible package releases: see Ansible 6 for an example for an example GitHub tracking issue for the Ansible package release. https://docs.ansible.com/ansible/latest/index.html
• Core Japanese - that is embedded in the core release checklist for now. This publishes to https://docs.ansible.com/ansible-core/2.13_ja/index.html

They release in the order listed above. When ansible-core and Ansible release, there is an older version that goes End-of-life, and we need to also take steps to EOL the docs for that release.

Release cadence - Ansible package

The Ansible package release depends on the ansible-core release and tends to publish 3-4 weeks after the core releases. For major releases, we:

• Track the checklist steps listed above.

For minor releases, we:

• Merge the autogenerated porting guide PR created by the release team and republish devel docs with the appropriate Jenkins job (internal to Red Hat at this point).
• Backport that PR to the stable release branch and republish the latest job.

Mapping core to Ansible releases

After Ansible 4, we tracked one Ansible release per core release. The release numbers are as follows:

ansible-core	Ansible
stable-2.11	4
stable-2.12	5
stable-2.13	6
stable-2.14	7