Issue: We don't have 100% confidence that each of those repos is ok for release. While they may build, we don't always have confirmation that the repos are functionally ok. For the 23.05 release we had to review the o3de-extras repo to ensure everything in there was good to go- see https://github.com/o3de/sig-release/issues/172
What to do:
1 month before stabilization, come to a consensus that these repos should be included. Come up with a plan to test anything that needs to be tested in advance of the release
Background: O3DE releases consist of multiple repositories (or "repos"): o3de o3de.org o3de-multiplayersample o3de-multiplayersample-assets o3de-netsoaktest o3de-extras
Issue: We don't have 100% confidence that each of those repos is ok for release. While they may build, we don't always have confirmation that the repos are functionally ok. For the 23.05 release we had to review the o3de-extras repo to ensure everything in there was good to go- see https://github.com/o3de/sig-release/issues/172
What to do: 1 month before stabilization, come to a consensus that these repos should be included. Come up with a plan to test anything that needs to be tested in advance of the release