No, the plan is to have additional maintenance releases when stx.2.0 gating bug fixes and CVE fixes are available. Nominal cadence is every 4-6wks, assuming there are fixes to warrant a build. That being said, the domain PL can review with the TL and they can decide to re-gate bugs from stx.2.0 to stx.3.0 depending on some rationale (risk, frequency, etc). This needs to be done on an individual bug basis. There is no plan for a general re-gate. Hope this clarifies things. Ghada -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, October 03, 2019 5:45 PM To: Khalil, Ghada Cc: Little, Scott; Cabrales, Ada; starlingx-discuss@lists.starlingx.io Subject: RE: stx.2.0.1 maintenance RC build Requested I might have missed this today since I was late to the release meeting. There are still bugs open against stx.2.0. Is the plan to move those to 3.0? Thanks! brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Thursday, October 3, 2019 8:29 AM To: Little, Scott <Scott.Little@windriver.com>; Cabrales, Ada <ada.cabrales@intel.com>; starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Importance: High Hi Scott, All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. Core reviewers, Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. References: - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 Thanks, Ghada On behalf of the StarlingX release team _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss