[Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 17/2019

[Khalil, Ghada]

Agenda/Minutes are posted at:
https://etherpad.openstack.org/p/stx-releases 

Release Team Meeting - October 17 2019
Election
- Agreed that the Release team does not need a TL. Bruce to make recommendation to the TSC.

stx.2.0 - maintenance release: stx.2.0.1
- Regression completed as of 2019-10-05
        - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006515.html
        - No new issues found
        - Need to discuss two reported issues which are currently not gating for stx.2.0
              - https://bugs.launchpad.net/starlingx/+bug/1836378 
                       - [[GK]] This was initially reported as a very intermittent issue and is currently not gating for stx.2.0. What's the frequency of occurrence? Does another lock/unlock attempt recover the issue? We need to decide if we should make this stx.2.0 gating and target a fix for a subsequent maintenance release.
                       - As per Elio, this was seen by Yosief in WR lab. Elio is not able to reproduce it as of yet. 
                       - Keep as is for now ...until it becomes a bigger problem
              - https://bugs.launchpad.net/starlingx/+bug/1841660 
                       - [[GK]] Same as above. Is this an intermittent issue? What's the frequency of occurrence? Previously this was reported once and therefore is not currently marked as gating for stx.2.0. We need to decide if we should make this stx.2.0 gating and target a fix for a subsequent maintenance release.
                       - Also seen in WR lab.
                       - Keep as is for now ...until it becomes a bigger problem
- Branch Labelling/CENGN Release Update
        - Forecast: 2019-10-18  >> COMPLETE
- Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 
        - Count: 7
        - Action: ping PLs to see if issues are actively being worked and if they should continue to be gating for stx.2.0

stx.3.0
- Milestone-3 was scheduled for Oct 18. Based on current status, this will be delayed by one week
- Feature Status
        - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 
        - Done: 5
        - Dev In Progress: 6 (1 prep expected to complete by 10.30)
        - Test In Progress: 3
        - Deferred/Continuing in stx.4.0: 3  (excluding others that were deferred earlier)
        - Most features have reasonable dates for code merge/feature testing.
        - Feature-specific Risks:
               - Upversion to Train: No projected dates provided. Some items are still unresourced. Unclear whether this can land.
- Regression Test
        - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 
        - Completion Rate: 24%
        - Making good progress / no concerns
- Feature Test
        - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 
        - Completion Rate: 39%

stx.4.0
- Tentative Dates (based on current formula to lag openstack by ~6 weeks)
        - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 
- Discussed if 6wks LAG from openstack is still the right duration
        - At this time, we feel it is. However, we just need to start the openstack rebase earlier in the cycle than was done for stx.3.0