[Starlingx-discuss] stx.2018.10 Status
Hello all, The code freeze for the StarlingX October release is scheduled for Wednesday Sept 26. During the community meeting on Wednesday 10am ET, we will have a final review of the status and a go/no-go call for the code freeze. Summary: There are 15 stories in Story Board and 13 bugs in Launchpad tagged against the release. See below for more details. Logistics: All features/enhancements need to be submitted for the code freeze. Bug fixes will continue to go in until the Once the code freeze is in effect, there will be no submissions to master until the release branch is created. Once the release branch is created, all bugs tagged for stx.2018.10 need to be submitted in master first and cherry-picked to the release branch. Story Board: 2003396/2003339: [Feature] Upgrade libvirt & libvirt-python to 4.7.0 Code is ready. Working through reviews and waiting for branch merge instructions 2003715: Move StarlingX OCF scripts out of stx-openstack-ras repo In progress. Expect status update Tuesday morning 2003115: [stx-cinder / stx-python-cinderclient] Remove proprietary cinder volume backup and restore Code ready to merge, but is dependent on 2003715. 2003087: [Feature] Generalized Interface and Network Configuration Code merged. Testing in progress and issues are reported in Launchpad. Will close. 2002985: [Bug] Backup and Restore: failed to create multiple cinder backups in parallel Covered by 2003115. See status above. 2002946: [Enhancement] OVS LLDP inventory Gerrit review in progress. Some follow-up required. Expect status update tomorrow to determine if this will make it before the code freeze. 2002835: [Feature][Build] StarlingX Build Optimization Code merged. The remaining item is the wiki; not gated by the code freeze 2002813: [Doc] Create initial template for documentation Several tasks under review. Will get an update on Wednesday 2002712: [Doc] Provide StarlingX API documentation Several tasks under review. Will get an update on Wednesday 2002708: [Doc]: Define/Document the initial documentation infrastructure, style and publishing process Several tasks under review. Will get an update on Wednesday 2002707: [Doc] Document the StarlingX CI/CD environment Not gated by code freeze; content goes on the wiki 2002706: [Doc] Document the basic project planning process and tooling Not gated by code freeze; content goes on the wiki 2002738: [Doc] Define and document the feature development process Not gated by code freeze; content goes on the wiki 2002700: [Doc] STX - Getting Started Not gated by code freeze; content goes on the wiki Launchpad: Tagged for stx.2018.10: 13 https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 All are assigned with the exception of one build issue: https://bugs.launchpad.net/starlingx/+bug/1792001 (Action: Cesar to follow up) Needs Triage: 1 https://bugs.launchpad.net/starlingx/+bug/1790514 (Hayde following up with the reporter) Regards, Ghada
On Mon, Sep 24, 2018 at 4:42 PM, Khalil, Ghada <Ghada.Khalil@windriver.com> wrote:
The code freeze for the StarlingX October release is scheduled for Wednesday Sept 26. During the community meeting on Wednesday 10am ET, we will have a final review of the status and a go/no-go call for the code freeze.
I would add that the Zuul pipelines have been running slowly the last week or so, partially due to a reduction in capacity from some of our cloud providers. We are waiting for test nodes up to 5+ hours today in the check pipeline. Things are running slower than usual so we will need to account for that in setting the actual freeze time. [...]
Once the code freeze is in effect, there will be no submissions to master until the release branch is created.
The requirement here is no merges until after the branches. We can continue to submit to Gerrit, and trust the core reviewers to not +W anything. That way the regular back-and-forth of the review process can continue. dt -- Dean Troyer dtroyer@gmail.com
Great clarification, Dean; we do want the review process to continue orthogonal to the release, even if merges are stopped. -- David C On 9/24/18, 5:23 PM, "Dean Troyer" <dtroyer@gmail.com> wrote: On Mon, Sep 24, 2018 at 4:42 PM, Khalil, Ghada <Ghada.Khalil@windriver.com> wrote: > The code freeze for the StarlingX October release is scheduled for Wednesday > Sept 26. During the community meeting on Wednesday 10am ET, we will have a > final review of the status and a go/no-go call for the code freeze. I would add that the Zuul pipelines have been running slowly the last week or so, partially due to a reduction in capacity from some of our cloud providers. We are waiting for test nodes up to 5+ hours today in the check pipeline. Things are running slower than usual so we will need to account for that in setting the actual freeze time. [...] > Once the code freeze is in effect, there will be no submissions to master > until the release branch is created. The requirement here is no merges until after the branches. We can continue to submit to Gerrit, and trust the core reviewers to not +W anything. That way the regular back-and-forth of the review process can continue. dt -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
The code freeze for the StarlingX October release is scheduled for Wednesday Sept 26. During the community meeting on Wednesday 10am ET, we will have a final review of the status and a go/no-go call for the code freeze.
From Documentation side, find in [0] the today's update on the documentation [docs / releasenotes / api-ref] for our StarlingX repos.
2002813: [Doc] Create initial template for documentation Several tasks under review. Will get an update on Wednesday
See [1] Documentation Tracking for the individual updates and links to stories and reviews. See [2] Release Tracking for the individual updates and links to stories and reviews.
2002712: [Doc] Provide StarlingX API documentation Several tasks under review. Will get an update on Wednesday
See [3] API Reference Tracking for the individual update and links to stories and reviews.
2002708: [Doc]: Define/Document the initial documentation infrastructure, style and publishing process Several tasks under review. Will get an update on Wednesday
See [4] ? [0] https://ethercalc.openstack.org/sifnpbvze9lb [1] https://wiki.openstack.org/wiki/StarlingX/Documentation#Tracking [2] https://wiki.openstack.org/wiki/StarlingX/Releases/Release_Notes#Tracking [3] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#... [4] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001167....
participants (4)
-
Arce Moreno, Abraham
-
Cobbley, David A
-
Dean Troyer
-
Khalil, Ghada