Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - November 21 2019 General Need to add VM connectivity tests to sanity serious neutron issue with openstack train not found in sanity As per Elio, team have been working on this. Action: Ada to provide forecast date stx.3.0 - milestone-3 declared last week - Release Plan https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF... - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMf... - Completion Rate: 100% (up from 85%) - Re-test for GPU at 75% and QAT at 50%. Expect to complete by 11/22 - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuA... - Completion Rate: 52% (up from 49%) << excluding openstack? - Forecast: 11/29 - Clarification from Elio: By 11/29, the manual openstack test-cases and the automated test-cases (robot & pytest) will be run - Also want to re-run another 100 manual test-cases between 11/29 & 12/13 << Is this the final regression? - It will be too late to run test-cases up to 12/13 as that is the release date. Need to bring this in to 12/6 as per the initial plan - Need Elio, Ada & Yang to look at the minimal set to be run - Request an update on this by EOD 11/22 - RC1 Branch Creation - Current date to start 11/28 - No concerns doing this over Thanksgiving. Saul agreed to look at the manifest review. - Gating Bugs - Bill will follow up with the different PLs on their plans. Would like a view from all PLs by the next community call - 11/27 - Total critical/high/medium: 79 -- https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0 Critical / High: 20 - distro.openstack: 15 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distro.openstack - security: 14 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.security - per Ghada, 8 CVEs in progress and expected to be merged before end of next week - config: 11 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.config - containers: 24 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers - per Frank, looking to get forecasts from the assignees - containers/networking: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers+stx.networking - per Ghada, expect 1 bug to be fixed. The other will likely be re-gated to stx.4.0 - networking: 5 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.networking - per Huifeng, looking at the high priority bugs now - storage: 5 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.storage - distcloud: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distcloud - metal: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.metal - fault: 1 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.fault - update: 1 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.update stx.4.0 - Feature Candidate Etherpad: - https://etherpad.openstack.org/p/stx.4.0-feature-candidates - Release Plan: - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbr... - Next steps - Features marked as "Propose for stx.4.0" - Ghada to copy features to the release plan spreadsheet to start tracking progress and milestones. - Project/Feature Lead to confirm intent to work on feature and resourcing - Project/Feature Lead to start identifying repos and code areas the feature will impact with an approximate size impact (S / M / L) - This is intended to help the core reviewers plan their time - Test & CI/CD initiatives - Need to determine how best to track this at the release level. - Unit test & Functional (API) tests - Agreed that each subproject team/PL needs to drive these initiatives for their domain(s) - Would like to have every PL define their targets for improvement within the stx.4.0 time-frame; measureable milestones - Bill will bring this up in the next community meeting and set expectations with the PLs - Regression Test Automation - Ask Ada to prime this - Performance Test Automation - Ask Ada to prime this - Code scans using Bandit & Coverity - Ask security team to prime and determine if there are resources to take this on