search

o3de / sig-release

8 stars 20 forks source link

O3DE Release 23.10.0 (scheduled for Oct 9, 2023) - Key Information #246

Open Ulrick28 opened 10 months ago

Ulrick28 commented 10 months ago

This issue is a single destination for all things related to the O3DE 23.10.0 Release. This issue will be updated as information changes. We will use this issue to surface questions and answer them so the entire community is aware of what to expect for the release.

O3DE 23.10.0 About this Release O3DE 23.10.0 will be the second major release of O3DE in 2023. The previous release was the 23.05.0 major release (May 2023). The 23.10 release will contain all of the features in the dev branch as of (stabilization date) Pacific time. Per our release naming standards, when referencing the release in technical documentation, the release should be referred to as "23.10.0". For marketing and general discussion, it is acceptable to refer to the release as "23.10".

Release Managers: @RoddieKieley @Ulrick28 @Naomi-Wash Release Manager: TBD Co-Release Manager: TBD Documentation Project Manager: TBD

Release Project Board https://github.com/orgs/o3de/projects/52/views/1

Feature List Coming soon

Release Notes Coming soon

Stabilization Branch https://github.com/o3de/o3de/tree/stabilization/2310 https://github.com/o3de/o3de-multiplayersample/tree/stabilization/2310 https://github.com/o3de/o3de-multiplayersample-assets/tree/stabilization/2310 https://github.com/o3de/o3de-netsoaktest/tree/stabilization/2310 https://github.com/o3de/o3de.org/tree/stabilization/2310

Stabilization Bug Reporting In the stabilization branch, any bugs found should get the "Release/2310" milestone applied.

Bug Tracking O3DE main repo - Bugs are being tracked with the [Release/2310 Milestone.] (milestone link) Atom Sample Viewer repo - TBD

Release Schedule with Exception Process for Submitting Code to the Stabilization Branch As documented in the below table, submissions to the stabilization branch will be subject to an Exception Process, (link to exception process)

Stabilization/2310 - Exception Requests You can access the board here

Date Description Bug Fixes Allowed in Stabilization Branch New Features Allowed in Stabilization Branch
Aug 21 Feedback period closed. No SIGs raised any concerns with release schedule N/A N/A
Aug 21 Release managers posted, empty project board set up. N/A N/A
Aug 21, 10:30 am Pacific Stabilization Branches created for the following repositories: o3de, o3de-multiplayersample, o3de-netsoaktest, o3de-extras . N/A N/A
Aug 21, 10:30 am Pacific (Docs) Stabilization branch created N/A N/A
Aug 21 through Sep 22, 2023 Stabilization Period Yes Yes, exception process is not required.
Sep 22, 2023 (Docs) Versioned API reference generation. A PR will be created by this date. Two approvals are needed from the o3de.org's standard reviewer pool. The PR should be merged by Oct 9. We will continue to accept changes until Oct 6. N/A N/A
Sep 23, 2023 Code Freeze on Major Bugs and below Beginning this date, Blocker and Critical bugs are allowed without the exception process. Major bugs or below requires an exception. No
Sep 29 Release Notes Finalized (features + known issues. A PR will be created by this date. A reviewer from sig-docs community or marketing committee, as well as sig-release are needed to approve the PR. The PR should be merged by Oct 9. We will continue to accept changes until Oct 6. N/A N/A
Oct 2 through Oct 6 QA Final Smoke Test Blocker bugs are still allowed via the exception process, with risk of delaying the release. No
Oct 6 Release considered "stable", all blocker/critical issues are resolved. No No
Oct 9, 2023 Release tasks are done. Binaries posted, code merged. The following repositories will be tagged:o3de, o3de-multiplayersample, o3de-netsoaktest, o3de-extras . No No
TBD 23.10.0 Release Marketing Announcement No No
Ulrick28 commented 9 months ago

Note the schedule is a little tight as we have condensed from 8-10 weeks to 6 weeks. We also do not have many available QA resources, so we will do a final smoke test rather than a full pass during the last week of stabilization. The smoke test will target issues resolved throughout stabilization, installation, basic run through the editor, rather than an overall thorough pass.