[Starlingx-discuss] Community Call (April 3, 2019)

[Zvonar, Bill]

Notes from the April 3rd call.

Bill...

Performance Footprint Metrics Demo (Victor)
    - Code: https://github.com/starlingx-staging/tools-contrib/tree/master/stx-metrics/footprint
    - Example Output: https://gist.github.com/VictorRodriguez/b9260ad223b176c323363ac06d0afdde
    - 3 phase plan, Victor starting on phase 0 now

Release Naming (Ghada)
    - For tagging, move from a naming convention that includes a date given the discussion around content-based releases
    - stx.2018.10   >> stx.R1  / stx.Rel1 / stx.rel1 / stx.1.0
    - stx.2019.05   >> stx.R2 / stx.Rel2 / stx.rel2 / stx.2.0
    - Leave internal SW_VERSION in software as is - currently: 19.01
    - Branch naming: ??  (we can decide this later at the time of RC1)
    - If agreed, bulk update StoryBoard, Launchpad and wiki references
    - we converged on this...
       - Release Name:  1.0, 2.0 >> 2.1 (First stable release after Intial Release)    -  
       - Launchpad/StoryBoard Tags: stx.1.0 (was stx.2018.10), stx.2.0 (was stx.2019.05), stx.2.0.rc1, stx.2.1
       - SW_VERSION: it'll remain in the same format as now

Reminder of repo renaming for OpenDev on 19 Apr 2019 (Dean)
    - https://etherpad.openstack.org/p/stx-opendev
    - expecting the downtime to be small, Dean expects they'll publish the timing next week

Bugs for Openstack core components (Ghada)
    - Propose to use the same stx launchpad and add the affected openstack component
          (ex: nova, neutron) as "Affects Project". 
    - This will make the bug visible in StarlingX as well as the affected openstack project.
    - Allows us to track progress of the bugs directly in our own queries without the need to have 2 bugs 
          (one in STX and one in the openstack project)
    - Example: https://bugs.launchpad.net/starlingx/+bug/1821938

Bug Tagging (Ghada)
    - Problem Description: Launchpad does not have a distinction between "Fix Resolved" and "Fix Verified". 
    - Once code merges in master, the bug is automatically updated to "Fix Released" and considered Closed. 
    - This doesn't provide a way to query bugs that need to be explicitly retested by the reporter
    - Proposal: 
       - New optional tag: stx.retestNeeded which is added by the screener at the time the bug is screened 
       - (or the reporter at the time the bug is created)
       - To find bugs that need verification, query: Status = "Fix Released" AND labels has "stx.retestNeeded"
       - Once the bug is verified by the reporter/test team, a note is added to the bug and the label is removed by the tester.

We didn't get to the sub-project updates, will start with those next week.

-------------------------------------------------------------------------------------------------------------------------------------

From: Zvonar, Bill 
Sent: Tuesday, April 2, 2019 7:44 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: Community Call (April 3, 2019)

Reminder of tomorrow's Community call - please feel free to add to the agenda at [0].

Bill... 

[0] etherpad: https://etherpad.openstack.org/p/stx-status
[1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call
[2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190403T1400