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>
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