[Release Day] Execute Launch for O3DE 24.09.0

[Naomi-Wash]

On Release Day, confirm each of the following launch activities is completed as expected

Predecessor Tasks @Ulrick28 to confirm:

• [Planning] Prepare for Launch Call #278
• [Pre Release] Prepare Build - 2 Days Before Release [Monday - Oct. 7] #269
• Launch Preparation Call #295

Docs

@RoddieKieley @ShaunaGordon Confirm the following pre-requisites are complete:

• [Pre Release] O3DE 24.09.0 Release: Ensure PR is created for applying the generated API reference to the docs site o3de#17962
• [Pre Release] O3DE 24.09.0 Release: Ensure PR is created for bumping the version number in the Linux install instructions o3de#17961
• [Pre Release] O3DE 24.09.0 Release: Ensure final release notes are documented, and a PR is created #290
• [Pre Release] O3DE 24.09.0 Release: Ensure version number updates to docs.o3de.org are staged (Required for Major Releases Only) #287

Merges

Code Merges

• [@nick-l-o3de] Click the merge button on the PR from stabilization to main (via. GitHub) for all of the following repos:
  • o3de
  • o3de-extras
  • o3de-multiplayersample
  • o3de-multiplayersample-asets
  • o3de-netsoaktest

*Note: O3DE - ignore Test Impact Analysis

Docs Merges

• @RoddieKieley Merge [Pre Release] O3DE 24.09.0 Release: Ensure PR is created for applying the generated API reference to the docs site o3de#17962
• @RoddieKieley Merge [Pre Release] O3DE 24.09.0 Release: Ensure PR is created for bumping the version number in the Linux install instructions o3de#17961
• @RoddieKieley Merge PR for docs from stabilization to main (includes release notes and update to o3de.org download screen version number)
• @RoddieKieley Re-target open PRs against stabilization against development

Gem Merges

• @spham-amzn O3DE extra gem merge

Release Tag

• @RoddieKieley @ShaunaGordon Create the release tag 24.09.0, and apply it to the following repos:
• o3de
  • o3de
  • o3de-extras
  • o3de-multiplayersample
  • o3de-multiplayersample-asets
  • o3de-netsoaktest
• [@amzn-changml] Invalidate CDN Cache after the release tag creation
• [@amzn-changml ] Begin work to add LFS binary objects to the artifacts under the new release tag, per the steps documented in this issue:
  • [Post Release] O3DE 24.09.0 Release: Ensure LFS binary objects are added and tested #270

Website Update for binaries

o3debinaries.org

• @amzn-changml (cc @RoddieKieley) Confirm the following pre-requisite is complete: stage website update
• @amzn-changml Publish version number update to o3debinaries.org

Update Download page [O3de.org]

• @Naomi-Wash pull information from binaries page
• @Naomi-Wash include (3) software prerequisite summary

Update Youtube Banner

• @Naomi-Wash Update Youtube banner

Verification

• @Ulrick28 Confirm the main branch has the latest code on Github
• @amzn-changml Confirm the release tag is applied to main branch
• @Ulrick28 Confirm the mainline build has begun (it should auto-start)
• @amzn-changml Confirm the version number is updated on o3debinaries.org
• @Ulrick28 Confirm the Windows installer is the correct version by downloading it from o3debinaries.org
• @RoddieKieley Confirm the Linux debian package is the correct version by downloading it from o3debinaries.org
• @Ulrick28 Confirm the installed Windows editor shows the correct version on the splash screen
• @RoddieKieley Confirm the installed Linux editor shows the correct version on the splash screen
• @Naomi-Wash Confirm the version number is updated on o3de.org downloads page (Required for Major Releases only)
• @Ulrick28 Confirm the release notes are updated
• @spham-amzn Confirm download project templates in gems from Project Manager

[Naomi-Wash]

Task to add to future release tasks

• Add installer testing the day before release
• Merge canonical
• Once canoncial is merged, publish the history
• Wait until builds are fully complete before adding release tags