[Starlingx-discuss] FIrst release branch
As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej
Apologies for the late response. I somehow missed this thread when I returned from vacation. With all the restructuring/churn that is currently going on branching at this time does not seem like the right thing to do. We should finish some of those activities first before branching. Even for a quarterly release why do we need to have a monthly branch. Shouldn't we just work on master and branch at some point before the release. Brent From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Tuesday, July 10, 2018 1:03 AM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej
On Tue, Jul 10, 2018 at 7:58 AM, Rowsell, Brent <Brent.Rowsell@windriver.com> wrote:
With all the restructuring/churn that is currently going on branching at this time does not seem like the right thing to do.
The primary reason for branching now is to use that to work on the release process and flesh out some of our policy, such as release branch backports, etc. It also provides a common point-in-time to reference the code for longer-term testing. There is a good bit of process for us to work out here[0] and I think we're going to learn a lot by the time we want to cut a release to show the world in Berlin.
We should finish some of those activities first before branching.
I agree that branching now may limit the ability to backport (cleanly) commits from master into the branch but I don't think this is a concern for the purposes of getting some experience with a brand-new release process.
Even for a quarterly release why do we need to have a monthly branch. Shouldn’t we just work on master and branch at some point before the release.
I don't expect the intermediate monthly branches to be around for a long time and if they turn out to not be useful we can always re-evaluate and stop doing it later. dt [0] In addition we actually need to write down our definition of a 'release'. We know it is source-only, I suspect it may not have any generated artifacts besides branches in git repos, at some point though it will include published documentation. I am making an assumption here that all of the "flock" repos are considered a single unit. Some of the sub-projects do appear to have versions and at some point we may want to start to treat those as distinct projects using a release model similar to OpenStack's cycle-with-intermediary [1] model (our default is closer to the cycle-with-milestone [2] model). [1] https://releases.openstack.org/reference/release_models.html#cycle-with-inte... [2] https://releases.openstack.org/reference/release_models.html#cycle-with-mile... -- Dean Troyer dtroyer@gmail.com
Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej
Did this branch get created today? From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, July 12, 2018 1:37 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] FIrst release branch Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com<mailto:erick.cardona.ruiz@intel.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej
Hi Bruce, Sure, I just need permissions in order to create the branches. I'll follow Dean's proposed process (based on some strategies of the openstack release process, specified here: https://docs.openstack.org/infra/manual/drivers.html). -Erick ________________________________ From: Jones, Bruce E Sent: Friday, July 13, 2018 5:29 PM To: Cardona Ruiz, Erick Cc: 'starlingx-discuss@lists.starlingx.io' Subject: RE: FIrst release branch Did this branch get created today? From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, July 12, 2018 1:37 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] FIrst release branch Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com<mailto:erick.cardona.ruiz@intel.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it’s the 2nd week of the month. It’s time to pull our first monthly branch. It should be called “stx.2018.07” and it should not be created until the latest kernel updates are complete. Unless those updates aren’t in by Thursday, because we’re going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can’t assign to you. Do you have an OpenStack ID? Thank you! brucej
@Dean how do we get Erick the right permissions? From: Cardona Ruiz, Erick Sent: Friday, July 13, 2018 3:47 PM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: FIrst release branch Hi Bruce, Sure, I just need permissions in order to create the branches. I'll follow Dean's proposed process (based on some strategies of the openstack release process, specified here: https://docs.openstack.org/infra/manual/drivers.html). -Erick ________________________________ From: Jones, Bruce E Sent: Friday, July 13, 2018 5:29 PM To: Cardona Ruiz, Erick Cc: 'starlingx-discuss@lists.starlingx.io' Subject: RE: FIrst release branch Did this branch get created today? From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, July 12, 2018 1:37 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com<mailto:erick.cardona.ruiz@intel.com>> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] FIrst release branch Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick <erick.cardona.ruiz@intel.com<mailto:erick.cardona.ruiz@intel.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej
participants (4)
-
Cardona Ruiz, Erick
-
Dean Troyer
-
Jones, Bruce E
-
Rowsell, Brent