[Starlingx-discuss] [Release] stx.2018.10 status & next steps

Khalil, Ghada Ghada.Khalil at windriver.com
Wed Sep 26 15:44:02 UTC 2018


Hello all,
This email captures the discussion related to the stx.2018.10 code freeze plan - discussed this morning at the StarlingX community meeting.

The code freeze will be in effect as of today (September 26, 2018) at midnight Eastern Time / 9pm Pacific Time
Gerrit reviews can continue, but we ask Core Reviewers NOT to Workflow+1 any commits after the cut-off above. 
Follow-up emails will be sent when merges can resume on master.

Review Priorities/Workflow+1 until the code freeze:
- Stories:
       - https://storyboard.openstack.org/#!/story/2003715 
       - https://storyboard.openstack.org/#!/story/2003396
       - https://storyboard.openstack.org/#!/story/2003339
       - https://storyboard.openstack.org/#!/story/2003115 
       - https://storyboard.openstack.org/#!/story/2002985 
       - https://storyboard.openstack.org/#!/story/2002946  (best effort)
- Documentation Updates: https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline 
- Updating the release version to 18.10:  https://storyboard.openstack.org/#!/story/2003085 
- Key Bugs
       - https://bugs.launchpad.net/starlingx/+bug/1794415 (more info to be sent to mailing list)
       - https://bugs.launchpad.net/starlingx/+bug/1794542 (assigned to Scott)
       - https://bugs.launchpad.net/starlingx/+bug/1793214 (assigned to Mitch)
- Other stx.2018.10 bugs
       - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 
       - Use your discretion depending on complexity, testing, churn, etc
       - There is no real urgency to get all these bugs into master before the code freeze as these can merge later and be cherry-picked by the developer to the release branch

If you have any questions, please respond to this email.

Regards,
Ghada





More information about the Starlingx-discuss mailing list