[Starlingx-discuss] stx-nova changes
In preparation for using the starlingx-staging/stx-nova repository for hosting our stable branch in the near future I am renaming the existing master branch (previously used for the build pre-container) to stx/old-master. Why? The stable backport branch (stx/stein) will track upstream stable/stein closely and I think having both upstream master and stable/stein in the repo will simplify ongoing maintenance. Summary: * master is renamed to stx/old-master (formerly used for builds) * upstream master synced to master * upstream stable/stein synced to stable/stein * new stx/stein created from stable/stein when required master and stable/stein will be populated soon, stx/stein will be created when we have something to backport to it. dt -- Dean Troyer dtroyer@gmail.com
On 3/26/2019 2:04 PM, Dean Troyer wrote:
In preparation for using the starlingx-staging/stx-nova repository for hosting our stable branch in the near future I am renaming the existing master branch (previously used for the build pre-container) to stx/old-master. Why? The stable backport branch (stx/stein) will track upstream stable/stein closely and I think having both upstream master and stable/stein in the repo will simplify ongoing maintenance.
Just to clarify, would builds be done from stx/stein once created? (And stable/stein if stx/stein doesn't exist?) Chris
On Wed, Mar 27, 2019 at 11:12 AM Chris Friesen <chris.friesen@windriver.com> wrote:
Just to clarify, would builds be done from stx/stein once created? (And stable/stein if stx/stein doesn't exist?)
When we create the stx-nova stx/stein branch we would change the build to pull from there rather than upstream. Until then I do not expect to change anything. I will mirror upstream master and stable/stein branches into stx-nova after https://review.openstack.org/#/c/648180/ merges so we have a bit of time to find other things still assuming that is the old stx nova tree. dt -- Dean Troyer dtroyer@gmail.com
participants (2)
-
Chris Friesen
-
Dean Troyer