[Starlingx-discuss] Milestone 2018.07.0 is available.
In our first steps toward creating a release process I created a branch last night named 'm/2018.07' that forms the basis for our first monthly milestone. See the new wiki page[0] for a WIP overview of the process. As a reminder, the milestones are created in order to provide a stable source for extended testing and a way to fix issues specifically for that build (backported from master). [Between the time I started this email and actually sent it we had our first backport!] I submitted a review[2] that contains an updated default.xml manifest that will pull the branch rather than master, you can try it with: repo init -u https://git.starlingx.io/stx-manifest.git -b refs/changes/48/584348/1 -m default.xml It pulls the right branches, however there are a couple of things I am still investigating: * the remote branchess are all prefixed with 'm/', so the remote branch for the milestone is shown in a git branch -r as 'm/m/2018.07' * the repos from Gerrit are detatched HEAD although it is at the right sha I am certain these are due to my still becoming familiar with the intricacies of the repo tool and configuring the manifest properly. Manual git clones from the upstream repos show the branch names as expected. dt [0] https://wiki.openstack.org/wiki/StarlingX/Release_Process [1] https://review.openstack.org/#/c/584430/ [2] https://review.openstack.org/#/c/584348/ -- Dean Troyer dtroyer@gmail.com
As a second step in our release process, can someone please do a build against the branch? And send the ISO to the Test team? brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Friday, July 20, 2018 9:06 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In our first steps toward creating a release process I created a branch last night named 'm/2018.07' that forms the basis for our first monthly milestone. See the new wiki page[0] for a WIP overview of the process. As a reminder, the milestones are created in order to provide a stable source for extended testing and a way to fix issues specifically for that build (backported from master). [Between the time I started this email and actually sent it we had our first backport!] I submitted a review[2] that contains an updated default.xml manifest that will pull the branch rather than master, you can try it with: repo init -u https://git.starlingx.io/stx-manifest.git -b refs/changes/48/584348/1 -m default.xml It pulls the right branches, however there are a couple of things I am still investigating: * the remote branchess are all prefixed with 'm/', so the remote branch for the milestone is shown in a git branch -r as 'm/m/2018.07' * the repos from Gerrit are detatched HEAD although it is at the right sha I am certain these are due to my still becoming familiar with the intricacies of the repo tool and configuring the manifest properly. Manual git clones from the upstream repos show the branch names as expected. dt [0] https://wiki.openstack.org/wiki/StarlingX/Release_Process [1] https://review.openstack.org/#/c/584430/ [2] https://review.openstack.org/#/c/584348/ -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
As a second step in our release process, can someone please do a build against the branch? And send the ISO to the Test team?
@Hayde is taking care of this step, will provide the update as soon as possible. If someone has already built it please let us know so we can cross reference steps and update the Getting Started Developer Guide [0] now based on our stable branch. Does anyone see any benefit in having another Developer Guide based on master? The challenge will be to keep up to date with all changes happening, is it worth the effort? [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On Mon, Jul 23, 2018 at 10:39 AM, Arce Moreno, Abraham <abraham.arce.moreno@intel.com> wrote:
Does anyone see any benefit in having another Developer Guide based on master? The challenge will be to keep up to date with all changes happening, is it worth the effort?
[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
I expect the divergence between master and the recent monthly milestone is not going to be huge (after the upcoming restructuring) most of the time, it may not be worth it to maintain two versions, making notes as required in the existing guide should be sufficient. dt -- Dean Troyer dtroyer@gmail.com
At some point we should start putting our docs into the actual stx-docs repo and published using the OpenStack documentation framework. Then they will be versioned and in sync when we branch. brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, July 23, 2018 8:48 AM To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com> Cc: Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Milestone 2018.07.0 is available. On Mon, Jul 23, 2018 at 10:39 AM, Arce Moreno, Abraham <abraham.arce.moreno@intel.com> wrote:
Does anyone see any benefit in having another Developer Guide based on master? The challenge will be to keep up to date with all changes happening, is it worth the effort?
[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
I expect the divergence between master and the recent monthly milestone is not going to be huge (after the upcoming restructuring) most of the time, it may not be worth it to maintain two versions, making notes as required in the existing guide should be sufficient. dt -- Dean Troyer dtroyer@gmail.com
As a second step in our release process, can someone please do a build against the branch? And send the ISO to the Test team?
@Hayde is taking care of this step, will provide the update as soon as possible.
I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues. [0] https://review.openstack.org/#/c/585043/ [1] https://review.openstack.org/#/c/585046/
On Mon, Jul 23, 2018 at 5:35 PM, Martinez Landa, Hayde <hayde.martinez.landa@intel.com> wrote:
I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues.
\o/ The patches look good, we'll merge the one for master first, and make any adjustments needed before merging the backport (I don't expect any in this case). We should get some reviews on https://review.openstack.org/#/c/584348/ to merge the m/2018.07 manifest... dt -- Dean Troyer dtroyer@gmail.com
Awesome! Ada please have tests run against this build and report the results, thanks! brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, July 23, 2018 3:54 PM To: Martinez Landa, Hayde <hayde.martinez.landa@intel.com> Cc: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Milestone 2018.07.0 is available. On Mon, Jul 23, 2018 at 5:35 PM, Martinez Landa, Hayde <hayde.martinez.landa@intel.com> wrote:
I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues.
\o/ The patches look good, we'll merge the one for master first, and make any adjustments needed before merging the backport (I don't expect any in this case). We should get some reviews on https://review.openstack.org/#/c/584348/ to merge the m/2018.07 manifest... dt -- Dean Troyer dtroyer@gmail.com
I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues.
\o/
The patches look good, we'll merge the one for master first, and make any adjustments needed before merging the backport (I don't expect any in this case).
We should get some reviews on https://review.openstack.org/#/c/584348/ to merge the m/2018.07 manifest...
dt
Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
Working on it
-----Original Message----- From: Jones, Bruce E Sent: Monday, July 23, 2018 6:53 PM To: Dean Troyer <dtroyer@gmail.com>; Martinez Landa, Hayde <hayde.martinez.landa@intel.com>; Cabrales, Ada <ada.cabrales@intel.com> Cc: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx- discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Milestone 2018.07.0 is available.
Awesome! Ada please have tests run against this build and report the results, thanks!
brucej
-----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, July 23, 2018 3:54 PM To: Martinez Landa, Hayde <hayde.martinez.landa@intel.com> Cc: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Milestone 2018.07.0 is available.
I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that applies for both, master [0] and branch M/2018.07 [1]
On Mon, Jul 23, 2018 at 5:35 PM, Martinez Landa, Hayde <hayde.martinez.landa@intel.com> wrote: that solves the package dependency issues.
\o/
The patches look good, we'll merge the one for master first, and make any adjustments needed before merging the backport (I don't expect any in this case).
We should get some reviews on https://review.openstack.org/#/c/584348/ to merge the m/2018.07 manifest...
dt
--
Dean Troyer dtroyer@gmail.com
participants (5)
-
Arce Moreno, Abraham
-
Cabrales, Ada
-
Dean Troyer
-
Jones, Bruce E
-
Martinez Landa, Hayde