[openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-17 Thread Steven Hardy
Hi all, Recently I had some discussion with folks around the future strategy for TripleO wrt upgrades, releases and branches, specifically: - How do we support a "stable" TripleO release/branch that enables folks to easily deploy the current stable release of OpenStack - Related to the above, h

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-09-09 Thread Steven Hardy
On Tue, Aug 18, 2015 at 02:28:39PM -0400, James Slagle wrote: > On Tue, Aug 18, 2015 at 2:10 PM, Steven Hardy wrote: > > On Mon, Aug 17, 2015 at 03:29:07PM -0400, James Slagle wrote: > >> On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: > >> > Hi all, > >> > > >> > Recently I had some discuss

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-17 Thread James Slagle
On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: > Hi all, > > Recently I had some discussion with folks around the future strategy for > TripleO wrt upgrades, releases and branches, specifically: > > - How do we support a "stable" TripleO release/branch that enables folks to > easily deploy

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-17 Thread Giulio Fidente
On 08/17/2015 09:29 PM, James Slagle wrote: On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: Hi all, Recently I had some discussion with folks around the future strategy for TripleO wrt upgrades, releases and branches, specifically: - How do we support a "stable" TripleO release/branch th

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-18 Thread marios
On 17/08/15 22:29, James Slagle wrote: > On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: >> Hi all, >> >> Recently I had some discussion with folks around the future strategy for >> TripleO wrt upgrades, releases and branches, specifically: >> >> - How do we support a "stable" TripleO release

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-18 Thread Thierry Carrez
Steven Hardy wrote: > The obvious answer is a stable branch for certain TripleO components, and > in particular for t-h-t, but this has disadvantages if we take the > OpenStack wide "no feature backports" approach - for example "upgrade > support to liberty" could be considered a feature, and many

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-18 Thread Zane Bitter
On 17/08/15 15:29, James Slagle wrote: > >I'd like propose we take a somewhat modified "release branch" approach, >which combines many of the advantages of the stable-branch model, but >allows for a somewhat more liberal approach to backports, where most things >are considered valid backports pro

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-18 Thread Steven Hardy
On Mon, Aug 17, 2015 at 03:29:07PM -0400, James Slagle wrote: > On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: > > Hi all, > > > > Recently I had some discussion with folks around the future strategy for > > TripleO wrt upgrades, releases and branches, specifically: > > > > - How do we suppo

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-18 Thread James Slagle
On Tue, Aug 18, 2015 at 2:10 PM, Steven Hardy wrote: > On Mon, Aug 17, 2015 at 03:29:07PM -0400, James Slagle wrote: >> On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: >> > Hi all, >> > >> > Recently I had some discussion with folks around the future strategy for >> > TripleO wrt upgrades, r

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

2015-08-18 Thread Steven Hardy
On Tue, Aug 18, 2015 at 02:28:39PM -0400, James Slagle wrote: > On Tue, Aug 18, 2015 at 2:10 PM, Steven Hardy wrote: > > On Mon, Aug 17, 2015 at 03:29:07PM -0400, James Slagle wrote: > >> On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: > >> > Hi all, > >> > > >> > Recently I had some discuss