Hi Scott, For R4 we branched the starlingx/docs repo. This is a new process for starlingx/docs, so I'm sending a reminder to please be sure it is part of your tagging process. thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp@intel.com -----Original Message----- From: Saul Wold <sgw@linux.intel.com> Sent: Wednesday, July 22, 2020 11:31 AM To: starlingx-discuss@lists.starlingx.io; Scott Little <scott.little@windriver.com> Cc: Miller, Frank <Frank.Miller@windriver.com>; Panech, Davlet <Davlet.Panech@windriver.com> Subject: [Starlingx-discuss] Tagging for stx.4.0 release Scott, As you know I looked into both the root/build-tools/branching scripts and the tools/release scripts. I chose the tools/release scripts since they handled the branching better (it created the .gitreview). Both sets of scripts will probably work correctly for tagging, but neither handle the creation of the manifests correctly for the tag and now for layered build also, this would have to be done by hand initially. I do have a story[0] and folks assigned to fix the manifest issue, but that won't be fixed by next week. I think you are know the basics since you did this for the 3.0 release. You need to create the 4.0.0 tag for all repos and then create the stx.4.0.0-default.xml (which I guess is what you use for jenkins). I am thinking you will also need to create stx.4.0.0-*.xml for the layered build. All the release specific xml files will need a <default remote="starlingx" revision="refs/tags/4.0.0"/> line. There was some discussion about also tagging the ryu and stx-openstack-ras repos, but I am not sure who owns those, for the stx.4.0 branch, I added a git SHA. I might be up and around by Thursday, but with limited time. Sau! [0] https://storyboard.openstack.org/#!/story/2007926 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss