Proposed SIG-Release meeting agenda for April-11-23

[vincent6767]

Meeting Details

• Date/Time: April 11th, 2023 @ 5:00pm UTC / 10:00am PDT
• Location: Discord SIG-Release Voice Room
• Moderator:: @tonybalandiuk
• Note Taker : @vincent6767

The SIG-Release Meetings repo contains the historical past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

Roadmap Progress Updates: https://github.com/o3de/sig-release/issues/79

• https://github.com/o3de/sig-release/issues/137
  • SIG Docs community merged the PR, ready to be released on the 23.05
• https://github.com/o3de/sig-release/issues/146
  • https://github.com/o3de/sig-release/issues/146#issuecomment-1496243200

Release updates: https://github.com/o3de/sig-release/issues/133

• Naomi will help as 23.05 RM for the time being.
• Initial feature list created: https://github.com/o3de/sig-release/pull/156
• o3de-extra will be released on the next release 23.05. When we release we merge everything that is tested to the main. So the release will only contain things from O3DE Extras that have been tested. Based on this conversation, tested gems are XR and OpenXRVk

Meeting Agenda

1. @tonybalandiuk 23.05 RM and release updates and next steps. https://github.com/o3de/sig-release/issues/1333.
   1. Including the release tasks distribution between Tony, Naomi, and Vincent.
2. o3de-extras next steps.
3. Discuss Naomi's request for the O3DF board meeting: identify feature/capability gaps, how they are being addressed/closed, and the overall timeline for completion. Here is the sheet.

Discuss agenda from proposed topics

[tonybalandiuk]

+Agenda Item Raised here https://github.com/o3de/o3de/issues/15375# Question - for this release, for exception requests should we still require SIG UI UX approvals? Ideally we have a chair or co-chair from that SIG here to discuss

[Ulrick28]

I am proposing we remove the sig-ui-ux approvals. The exception process is to help protect against destabilization of the release. Sig-UI-UX was primarily concerned with anything affecting RTE, which is no longer an initiative for the 2305 release.

[vincent6767]

Meeting notes

1. https://github.com/o3de/sig-release/pull/175

[tonybalandiuk]

from the meeting notes: Action Items

• [x] @tony @naomi @vincent to discuss about the release tasks distribution - DONE we met after the meeting.
• [x] @naomi to schedule a release check-in meeting next week the same day at 9 AM PDT. DONE - see https://lists.o3de.org/g/o3de-calendar/viewevent?eventid=1895476&calstart=2023-04-18
• [x] @danilo to help check whether O3DE-extras follow the Gitflow.
• [x] @vincent to follow up with Brian and Alex whether we have any issues with just bringing only some of the gems.
• [x] @tony reaches out to SIG UI/UX about whether they want to be in an approval process. Here https://discord.com/channels/805939474655346758/816043761687068712/1097624855123337279
• [x] @tony will open a discussion about this: SIG release to consider the exception time limit for the next release. Here https://github.com/o3de/sig-release/discussions/176

[tonybalandiuk]

@AMZN-daimini @vincent6767 please see above action items. Thanks!

[AMZN-daimini]

@tonybalandiuk Apparently we plan to include o3de-extras in the release, but it will likely skip the gitflow process and be merged just before the release; also, we may only include content that has been tested and we will not hold up the release due to the state of extras. There are definitely more considerations to be made for future releases, especially regarding testing and what standards we hold that repo to.

FYI @Ulrick28 @AMZN-alexpete

[vincent6767]

https://discord.com/channels/805939474655346758/1095140837383479357/1095146336438984814 My updates about o3de-extras.