[Planning] Ensure Docs-Community SIG requirements are identified

[Naomi-Wash]

Work with the Docs-Community SIG to define requirements, and determine if any of the requirements will block the release if not completed prior to the release.

These requirements could include, for example,

• Generate the C++ API reference for O3DE’s source code.
• Finalize release notes.
• Update Documentation versioning.
• Update the website to display the correct version number.

A complete description of requirements can be found in the Docs Release Process Runbook.

• Successor Task: (placeholder - confirm all launch blocking ...)
• Successor Task: (placeholder - confirm all non-launch blocking ...)

Discord: #sig-docs-community SIG Docs-Community meetings: O3DE Calendar SIG Docs-Community agendas: GHI

[Naomi-Wash]

@RoddieKieley Can you please review this GHI and update as you see fit given your experience updating docs during the last release? I want to make sure this is still an accurate release step. Thank you.

[Naomi-Wash]

Include:

• No Code Project documentation
• Robotec.ai