[Starlingx-discuss] Minutes: StarlingX Release Meeting - August 22/2019
Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - August 22 2019 stx.2.0 - Test Status - Feature Test - Tracker: https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST... - Ironic >> Made good progress thi week. Fix submitted. Tested with a hot fix; able to deploy ironic. Having trouble launching VMs; test team is working with Mingyuan to investigate. - Final Regression - Tracker: https://docs.google.com/spreadsheets/d/1FxrwgivQCG3Ksvqm46zhKILJlZtucsNxGYG4... - Tracker needs updating - Only 7 TCs left to execute - Final Candidate Build - Final Candidate Build for r/stx.2.0 is planned for Monday August 26 pm ET - This will also include a docker image build - at or near 11:30 PM UTC https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190826T2330 - Sanity / Test Plan - Agreed to have one day of testing on August 27 - Run sanity on all configurations - Run some additional TCs based on the discretion of the test teams - Example looking at recent commits: https://review.opendev.org/#/q/branch:+r/stx.2.0 - Ada to send the go-ahead once testing is done - What would make us rebuild? - Load is broken / RED sanity - Bugs that fail re-test will be re-opened and handled in the upcoming mtce release (if high priority) -- they will not result in a rebuild - Tagging / Posting on CENGN / Announcement - The build will be posted at: /export/mirror/starlingx/release/2.0.0/ - This is the same build done on Monday pm -- just copied over to the release directory and labeled properly stx.2.0 Maintenance Release - Agreed that monthly maintenance releases make sense. - We will target the week of Sept 30 as a tentative target for now - There is no infrastructure in place to generate binary updates against the release ISO - This should be noted to users of maintenance releases. Action: Dean to discuss with Ildiko regarding marketing information. Bill to add as a topic on the community call. - r/stx.2.0 branch expected to re-open for cherrypicks on Sept 3 - Builds will be on demand. Would like to target a weekly build on Monday -- assuming there is new content. - Sanity Schedule: Next day after the build - every Tuesday - Regression Schedule: Ada/Numan to work on proposal stx.3.0 - Milestone-2 -- wk of Sept 2 - Milestone-2 Criteria: - Spec freeze - Specs are in good shape. - Performance Framework spec is posted. R2 >> R3 spec will continue to be an exception. - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables - Documentation plan defined - Test team is raising concerns about the scope of features for stx.3.0 and the release timeline - Regression is supposed to start on Sept 23. - Only 5 weeks for feature testing - Given the tight timeline, we need PLs to provide a risk indicator for landing their feature content. Ideally, a rough plan would help the test team plan accordingly. - If a feature is too big to land in stx.3.0, knowing this now helps the test team focus their efforts on the features that will make it. - Agreed that storyboard will have the list of features being worked for the release. - Bill will follow up with the PLs to ensure any missing story boards are created.
participants (1)
-
Khalil, Ghada