One more thing. Once we get the green light from Dean, we need builds created from the branch so testing can begin. We'll need a reference build from within both Intel and Wind River to support the test teams there. Resolving build issues on the branch and Critical/test blocking bugs found in testing should be everyone's highest priority. brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Friday, September 28, 2018 10:19 AM To: Khalil, Ghada <Ghada.Khalil@windriver.com>; starlingx-discuss@lists.starlingx.io; Dean Troyer <dtroyer@gmail.com> Subject: [Starlingx-discuss] stx.2018.10 code freeze status -- Branch creation in progress Hello all, Dean is in the process of starting the branch creation for the stx.2018.10 release. Please do not W+1 any commits to master until the branches are created. Dean will send an email once merges can resume on master. Note: There are a few documentation updates which did not make it. Those will need to be cherry-picked to the release branches by their respective authors. Once the release branches are created, any commits tagged for stx.2018.10 need to be merged in master first and then cherry-picked to the release branch by the developer. All other commits (tagged for stx.2019.03 or untagged) should be merged in master only. Launch pads tagged for stx.2018.10: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 Stories tagged for stx.2018.10: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2018.10 * only the doc story is expected to have additional commits that require cherrypicking. Thank you everyone for working extra hard to get in the required content for the branch creation. Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss