[Starlingx-discuss] Release Plan - stx.2.0

Cabrales, Ada ada.cabrales at intel.com
Tue Aug 27 15:17:55 UTC 2019


Work in Progress

A.

> -----Original Message-----
> From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com]
> Sent: Tuesday, August 27, 2019 8:47 AM
> To: starlingx-discuss at lists.starlingx.io; Cabrales, Ada
> <ada.cabrales at intel.com>
> Cc: Khalil, Ghada <Ghada.Khalil at windriver.com>
> Subject: RE: Release Plan - stx.2.0
> 
> Quick update - the build went fine last night, so we can unleash the test team
> on sanity + additional testing.
> 
> Ada - unleash!
> 
> -----Original Message-----
> From: Khalil, Ghada <Ghada.Khalil at windriver.com>
> Sent: Friday, August 23, 2019 3:31 PM
> To: starlingx-discuss at lists.starlingx.io
> Cc: Zvonar, Bill <Bill.Zvonar at windriver.com>
> Subject: RE: Release Plan - stx.2.0
> 
> My apologies for the typo below...
> 
> The second last bullet should read:
> - All stx.2.0 unresolved high priority bugs remain gating stx.2.0 and will need
> to be resolved in an upcoming maintenance release.
> 
> -----Original Message-----
> From: Khalil, Ghada
> Sent: Friday, August 23, 2019 3:26 PM
> To: starlingx-discuss at lists.starlingx.io
> Cc: Zvonar, Bill
> Subject: Release Plan - stx.2.0
> 
> Hello all,
> The stx.2.0 final candidate build is scheduled on Monday August 26 at 11:30
> PM UTC.
> We are currently waiting for one commit to merge:
> https://review.opendev.org/#/c/678167/
> 
> Please do not cherry-pick any other commits to the r/stx.2.0 branch until
> further notice.
> 
> The logistics for next week are as follows:
> - Developer and core reviewers merge the remaining commit.
> - Final candidate build run on the r/stx.2.0 branch on Monday August 26
> - The test team executes one day of testing on the final candidate build --
> sanity + additional testing based on the discretion of the test teams
> - Ada will send a report by EOD Tuesday -- either with the go-ahead for the
> release OR identifying any RED sanity/blocking issues
>          - If there is a RED sanity, the bug will need to be resolved and the load
> will need to be re-built. And sanity will need to be re-executed.
> - If all is good, Scott and Dean will follow the steps to tag the branch and post
> the build artifacts in the release directory on CENGN.
> 
> Other things to note:
> - All stx.2.0 unresolved medium priority bugs have been moved to stx.3.0 as
> per community agreement
>          - This means fixes are only required in master from this point forward.
>          - PLs/TLs have the discretion to raise the priority of a medium bug and
> bring it back as a high priority in stx.2.0
> - All stx.3.0 unresolved high priority bugs remain gating stx.2.0 and will need
> to be resolved in an upcoming maintenance release.
>          - Developers are encouraged to continue working on those as a top
> priority and to post reviews on master
> - For more information on the stx.2.0 upcoming maintenance release, please
> read the minutes from the Release Meeting on 2019-08-22
> 
> If you have any questions/concerns, please reach out to Bill Zvonar as I am on
> vacation next week.
> 
> And, finally, a big thank you for all community members who have
> contributed to StarlingX 2.0.
> 
> 
> Best Regards,
> Ghada
> 
> 




More information about the Starlingx-discuss mailing list