[Starlingx-discuss] [r/2018.10] StarlingX Release 2018.10 RC1 branch is complete
I have completed branching all 44 repos for release 2018.10. This is tagged as 2018.10.rc1 for release candidate 1. We have not defined a formal release candidate process but I used the name for the branch tag as most people will know what that means: this branch will become the release when final. The final release tag will be 2018.10.0. Release branch: r/2018.10 Current tag: 2018.10.rc1 The usual list of .gitreview updates are the first reviews on the release branch in Gerrit and should be the first things approved on the branch. This list also includes an update for the manifest file. https://review.openstack.org/#/q/topic:create-r/2018.10+status:open All master branches are again open for merging ongoing work. Remember that any fixes to the release branch first get merged to master and then backported. Currently there are two reviews that were not merged before the branching (https://review.openstack.org/#/c/605254 did merge in time). They have topic set to release-backport: https://review.openstack.org/#/q/status:open+branch:master+topic:release-bac... There are currently two reviews on that list (https://review.openstack.org/606123 and https://review.openstack.org/605275), they are stacked and will merge in that order once approved. Thank you for your patience and please let me or anyone on the release team know if you find any problems. dt -- Dean Troyer dtroyer@gmail.com
On Oct 2, 2018, at 5:08 PM, Jones, Bruce E <bruce.e.jones@intel.com> wrote:
Is defining the formal process something that the Release team will do?
If we want one, yes. I’m not sure we need one right now, but adding it will be straightforward as I do tag the branch point as rc1 (maybe it should be rc0?) even though it isn’t release-ready. Effectively our RC cycle is currently a single tag and nothing else. In OpenStack-land the release is tagged off the last rc, per project. dt — Dean Troyer
participants (2)
-
Dean Troyer
-
Jones, Bruce E