[Release Day] Execute Launch for O3DE 23.10.1

[Ulrick28]

• [ ] Confirm the following pre-requisites are complete:

• [x] @AMZN-alexpete Ensure PRs are created for branch merge for 5 Repos and AR validated

  • [x] o3de: (https://github.com/o3de/o3de/pull/17182)
  • [x] o3de-extras: (https://github.com/o3de/o3de-extras/pull/629)
  • [x] o3de-multiplayersample: (no changes)
  • [x] o3de-multiplayersample-assets: (no changes)
  • [x] o3de-netsoaktest: (no changes)

• [x] @Ulrick28 Confirm release branch is stable

• [x] @AMZN-alexpete Click the merge button on the PR (via. GitHub) for all of the following repos:

  • [x] o3de
  • [x] o3de-extras
  • [x] o3de-multiplayersample (no changes)
  • [x] o3de-multiplayersample-asets (no changes)
  • [x] o3de-netsoaktest (no changes)

Release Tag

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

Installers

• [x] @Ulrick28 Confirm the following pre-requisites are complete
  • [x] Ensure installers are uploaded to S3 and the engine is set to 2.2.0 (confirm version with @AMZN-alexpete)

Docs Update

@RoddieKieley Confirm the following pre-requisites are complete:

• [ ] Ensure PR is created for applying the generated API reference to the docs site
• [x] Ensure PR is created for bumping the version number in the Linux install instructions
• [x] @Ulrick28 Ensure final release notes are documented, and a PR is created
• [x] (N/A for point release) Ensure version number updates to o3de.org are staged (Required for Major Releases Only)

  Merges

• [ ] @RoddieKieley Merge PR for applying the generated API reference to the docs site
• [ ] @RoddieKieley Merge PR for bumping the version number in the Linux install instructions
• [ ] @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

Website Update for binaries

o3debinaries.org

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

Update Download page O3de.org

• [x] @Naomi-Wash pull information from binaries page

Verification

• [x] @Ulrick28 Confirm the main branch has the latest code on Github
• [x] @amzn-changml Confirm the release tag is applied to main branch
• [x] @Ulrick28 Confirm the mainline build has begun (it should auto-start)
• [x] @amzn-changml Confirm the version number is updated on o3debinaries.org
• [x] @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
• [x] @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
• [x] @Naomi-Wash Confirm the version number is updated on o3de.org downloads page (Required for Major Releases only)
• [x] @Ulrick28 Confirm the release notes are updated
• [ ] @amzn-changml Confirm the 20.0.4 and 22.0.4 Snap packages are downloaded and have the correct versions. https://snapcraft.io/o3de/

[jhanca-robotecai]

Release Tag

• [ ] @RoddieKieley Create the release tag 23.10.1, and apply it to the following repos:

I believe there is a typo in the tag: 2310.1.

Btw. I see there no tags on o3de.org other than 1.0. Is this correct?

[Ulrick28]

@jhanca-robotecai Looks like the 2310.1 is the title of the integration PR, not the tag.

[jhanca-robotecai]

Thanks for the clarification. I saw it in the text, this is why I wanted to be sure the correct name is applied to the repos.