[Starlingx-discuss] Release Plan - stx.2.0

Zvonar, Bill Bill.Zvonar at windriver.com
Wed Aug 28 11:25:38 UTC 2019


Excellent, thanks for the update Elio, good news.

-----Original Message-----
From: Martinez Monroy, Elio <elio.martinez.monroy at intel.com> 
Sent: Tuesday, August 27, 2019 9:59 PM
To: Zvonar, Bill <Bill.Zvonar at windriver.com>; 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

Hello guys!

Just to let you know that we just finished our "additional testing".

Objective: Verify the latest changes included in today's release in order to check that those changes are not going to affect other features.

Testplan and results location:

		https://docs.google.com/spreadsheets/d/1qq4CuoWuKZcHbau84YKKcpckzFpzgci9anj1Ey18B3k/edit?usp=sharing

Configuration:
		a) Iso http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190826T233000Z/outputs/iso/
		b) Bare metal configuration according with patches and/or bugs related patches.

Results Overview:

		Total Test Cases included according with patches:
			25 Test Cases

		Passed: 	18 	All related bugs to each TC is updated as well
		Failed:		1	" Use ntpq refid to tell if peer controller reaches reliable time source" . Related bug: https://launchpad.net/bugs/1834071 Priority: Medium, Alarm Related.
		Deferred:	1	"Rework Ansible Docker Registry Structure" Reason: we need to modify our docker registry host in order to request user and password. 
		Not executed: 	5	Reasons: 2 not merged, 1 related to ipv6 (no infra ready), Ironic is tested separately , and one abandoned patch.

Conclusions:
		According with these results, we don't consider that the patches included during last week can compromise or affect Stx 2.0  release.
		Even the failed TC has some progress showing a different result better than the original failure.




BR

Elio Martinez
QA Engineer



-----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: [Starlingx-discuss] 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




_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


More information about the Starlingx-discuss mailing list