Documentation checklist - ansible-core 2.20

[samccann]

Documentation checklist to prepare for and deliver the ansible-core 2.20 release. See follow-on comment for the full checklist.

[samccann]

Tasks include:

• Review ansible-core porting guide to ensure the 2.20 porting guide is added to the index and ensure it links to core 2.20 changelogs.

• include 2.20 in the ansible-core support matrix and ensure maintenance/eol releases listed accurately. Include links to changelogs.

• Merge, then Backport any PRs for the above items to stable-2.20 branch.

• In stable-2.20 branch - Update ansible-core branch indicator file in docs/ansible-core-branch.txt in the stable-2.20 branch from devel to stable-2.20. See [stable-2.16] Update ansible-core branch indicator file #424

• Publish 2.20 docs to test after 2.20 beta.

• Update conf.py (DO NOT MERGE UNTIL RELEASE DAY)

  • Set '2.20' if tags.has('core_lang') or tags.has('core') else, under 'html_context' 'latest_version'
  • Set ('2.20', '2.19', '2.18', 'devel',) if tags.has('core') else, under ‘html_context’ 'available_versions'

• In stable-2.20 branch - change VERSION (capitalized) from devel to 2.20 as follows:
  '2.20' if tags.has('core_lang') or tags.has('core') else

On release day:

• Merge conf.py PR to devel
• Backport to stable-2.20, stable-2.19, and stable-2.18
• publish to all three releases to prod

Post release:

• Update the backport instructions to target the new “latest” branch, see update backport instructions to match 2.16 #799
• End-of-life the 2.17 docs
  • update the release/maintenance table to add EOL label to 2.17 row.
  • In the EOL branch (stable-2.17), update page banner to EOL to the release no longer supported. See eol 2.12 docs ansible#80957 note we should extend this banner to say this is the upstream EOL date and not reflective of Red Hat product EOL dates.