[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
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
We will be creating the 4.0.0 tag toady. We won't forget docs. On another thread I saw a plea for more doc reviews. Was there anything that requires us to delay tagging docs? We could tag everything else and delay tagging docs for a day or two. Scott On 2020-07-29 8:33 p.m., Camp, MaryX wrote:
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
The plea for docs is to review the R4 release notes. There is no need to delay tagging the docs. Please see: https://review.opendev.org/#/c/742989 and https://review.opendev.org/#/c/744061 for the docs changes for the R4 release. Reviews and comments welcome! brucej -----Original Message----- From: Scott Little <scott.little@windriver.com> Sent: Tuesday, August 4, 2020 7:44 AM To: Camp, MaryX <maryx.camp@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Miller, Frank <Frank.Miller@windriver.com>; Panech, Davlet <Davlet.Panech@windriver.com> Subject: Re: [Starlingx-discuss] Tagging for stx.4.0 release We will be creating the 4.0.0 tag toady. We won't forget docs. On another thread I saw a plea for more doc reviews. Was there anything that requires us to delay tagging docs? We could tag everything else and delay tagging docs for a day or two. Scott On 2020-07-29 8:33 p.m., Camp, MaryX wrote:
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
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 8/4/20 8:20 AM, Jones, Bruce E wrote:
The plea for docs is to review the R4 release notes. There is no need to delay tagging the docs.
I gave my comment, we can tag everything else and wait for this to merge before tagging the docs. Sau!
Please see: https://review.opendev.org/#/c/742989 and https://review.opendev.org/#/c/744061 for the docs changes for the R4 release. Reviews and comments welcome!
brucej
-----Original Message----- From: Scott Little <scott.little@windriver.com> Sent: Tuesday, August 4, 2020 7:44 AM To: Camp, MaryX <maryx.camp@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Miller, Frank <Frank.Miller@windriver.com>; Panech, Davlet <Davlet.Panech@windriver.com> Subject: Re: [Starlingx-discuss] Tagging for stx.4.0 release
We will be creating the 4.0.0 tag toady. We won't forget docs.
On another thread I saw a plea for more doc reviews. Was there anything that requires us to delay tagging docs? We could tag everything else and delay tagging docs for a day or two.
Scott
On 2020-07-29 8:33 p.m., Camp, MaryX wrote:
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
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Echoing Bruce, please don't delay tagging the docs for the RN. Thanks for asking, Mary C. -----Original Message----- From: Saul Wold <sgw@linux.intel.com> Sent: Tuesday, August 4, 2020 12:22 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Tagging for stx.4.0 release On 8/4/20 8:20 AM, Jones, Bruce E wrote:
The plea for docs is to review the R4 release notes. There is no need to delay tagging the docs.
I gave my comment, we can tag everything else and wait for this to merge before tagging the docs. Sau!
Please see: https://review.opendev.org/#/c/742989 and https://review.opendev.org/#/c/744061 for the docs changes for the R4 release. Reviews and comments welcome!
brucej
-----Original Message----- From: Scott Little <scott.little@windriver.com> Sent: Tuesday, August 4, 2020 7:44 AM To: Camp, MaryX <maryx.camp@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Miller, Frank <Frank.Miller@windriver.com>; Panech, Davlet <Davlet.Panech@windriver.com> Subject: Re: [Starlingx-discuss] Tagging for stx.4.0 release
We will be creating the 4.0.0 tag toady. We won't forget docs.
On another thread I saw a plea for more doc reviews. Was there anything that requires us to delay tagging docs? We could tag everything else and delay tagging docs for a day or two.
Scott
On 2020-07-29 8:33 p.m., Camp, MaryX wrote:
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
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (4)
-
Camp, MaryX
-
Jones, Bruce E
-
Saul Wold
-
Scott Little