Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Sanity - Last Update - Community Call on July 6 - Expect to have a sanity report (w/o stx-openstack) - by July 8 - Plan is to work on sanity w/ stx-openstack once fixes are available for: - https://bugs.launchpad.net/starlingx/+bug/1978409 - merged July 12 - https://bugs.launchpad.net/starlingx/+bug/1980397 - still open - Sanity w/o stx-openstack - WR team was able to run an AIO-SX sanity. - Hit some issues w/ AIO-DX that are under investigation; TBD whether it's a procedural or software issue - Action: Rob to ensure sanity reports start getting sent this week. - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 stx.7.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbIS... - Release Verification: - Folder: https://drive.google.com/drive/folders/1szAP-xVZq7ebSyGJ-EHTVebMmsupSY7w - Feature Testing: https://docs.google.com/spreadsheets/d/1hXJJ4LvxhWwLIF_PHpCyxlGpfKdXtcPjlycl... - Regression Testing: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiK... - From TSC / Community Call on July 6 - Agreed that getting stx-openstack running on stx.7.0 is a release blocker - Plans in place to address the identified issues and re-enable stx-openstack - Two key fixes required which are forecast for ~July 12 - https://bugs.launchpad.net/starlingx/+bug/1978409 - merged July 12 - https://bugs.launchpad.net/starlingx/+bug/1980397 - still open - Some WIP reviews posted. Need an update from the openstack team; expected in the community call - Upcoming Milestones - Revised - Based on discussion in Community Call on July 13 - RC1 (Branch Creation): week of July 4 >> week of July 18 (based on above sanity plans) - Final Regression: week of July 18 >> week of July 25 - Release: week of July 25 >> week of Aug 1 - Branch Creation - Option 1: Go ahead and branch the r/stx.7.0 branch - suggested by Frank - PRO: Avoid pollution from content unrelated to stx.7.0 (ex: prep for stx.8.0 features / Debian / etc) - CON: If we branch w/o a sanity, we don't have a known state of the load - Option 2: Institute a freeze on the stx main branch - suggested by Ildiko - PRO: Nothing goes in, so no pollution from unrelated content - CON: Impact to more community members who are already looking at stx.8.0 or bugs - Decision - Agreed a sanity w/o stx-openstack is sufficient for branch creation as the required stx-openstack changes are understood and in progress. - If it's not red, we can proceed with branch creation next week as per the plan discussed last week. - Bug status - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - In good shape. Only 3 LPs open. 2 are actively being worked and 1 is pending a sanity re-reun. - Docs - Majority of doc updates have merged. - Release notes in progress. Juanita expects to send draft this week. - Blogs - Release Announcement - Prime: Ildiko - In progress - Debian OS Migration - Prime: Frank Miller - PTP Enhancements - Dual NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Subcloud Local Install - Prime: RamS - Action: Each prime to provide forecast for draft info for the next planning meeting: July 27 stx.8.0 - Release folder and planning spreadsheet created: - Release Folder: https://drive.google.com/drive/folders/1qbnm3Zz5JzM16Drhw4locVQhn4uk7HI1?usp... - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ru... - Milestones (based on typical durations) are proposed - Milestone-1 8/29/2022 - Milestone-2 - 4wks after MS-1 9/26/2022 - Milestone-3 - 10wks after MS-2 12/5/2022 - Feature Test Complete - 4wks after MS-3 1/2/2023 - Regression Test Start - 1wk after MS-3 (in parallel w/ feature test) 12/12/2022 - Regression Test Complete - 3wks after Regression Start 1/2/2023 - RC1 - 1wk after Regression Test Complete 1/9/2023 - Final Regression Complete - 2wks after RC1 1/23/2023 - Release - 1wk after Final Regression 1/30/2023 - Dates are currently aligned with the typical release cadence - one release in Jan and one in July. - Action: Release team to review; we'll discuss again in the next - Next steps: Populate with candidate features - Action: Community / PLs to update the planning spreadsheet