** limited merges are still in effect **

Update:

The following sanity issues have fixes merged in stx master:

- https://bugs.launchpad.net/starlingx/+bug/1829260

- https://bugs.launchpad.net/starlingx/+bug/1829060

- https://bugs.launchpad.net/starlingx/+bug/1828896

- https://bugs.launchpad.net/starlingx/+bug/1828877

- https://bugs.launchpad.net/starlingx/+bug/1827521

- https://bugs.launchpad.net/starlingx/+bug/1828059 (dup)

- https://bugs.launchpad.net/starlingx/+bug/1828899 (dup)

A build has been triggered on cengn.

** Test team, please start sanity on the new build **

Regards,

Ghada

From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com]
Sent: Wednesday, May 15, 2019 11:09 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Limited code merges until sanity results improve
Importance: High

Hello all,

As discussed in the community meeting today, effective immediately, we ask the core reviewers to only merge code for sanity gating issues and critical/high priority bugs only.

This is in an effort to get some stability in the load and address the sanity issues recently reported.

A new label, stx.sanity, will be introduced to easily help the community identify issues affecting sanity moving forward.

https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.sanity

(tagging of the current issues is in progress)

For more details on the current issues, see today’s meeting minutes on the community etherpad:

https://etherpad.openstack.org/p/stx-status

Another email will be sent once the limited merge is lifted.

We appreciate your patience as we work together to get stable loads.

Regards,

Ghada

PS: Developers can continue to post reviews as per the normal process. Core reviewers can continue to review code as well, but not to merge them unless they meet the criteria stated above.