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 2^nd week of each month.

And now it’s the 2^nd 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