[openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

Clark Boylan cboylan at sapwetik.org
Fri Nov 20 12:37:06 UTC 2015


On Fri, Nov 20, 2015, at 04:32 AM, Julien Danjou wrote:
> On Fri, Nov 20 2015, Clark Boylan wrote:
> 
> > If you have a stable/X.Y branch or stable/foo but are still wanting to
> > map onto the 6 month release cycle (we know this because you are running
> > devstack-gate) how do we make that mapping? is it arbitrary? is there
> > some deterministic method? Things like this affect the changes necessary
> > to the tools but should be listed upfront.
> 
> Honestly, we don't use devstack-gate because we map onto a 6 months
> release. We use devstack-gate because that seems to be the canonical way
> of using devstack in the gate. :)
Mayne I should've said "because you are running devstack via
devstack-gate". Running devstack requires making choices of what
services to run based on the 6 month release cycle,
> 
> Right now, I think the problem I stated in:
>   [openstack-dev] [infra][devstack][gnocchi] Unable to run devstack-gate
>   with stable/1.3
>   http://lists.openstack.org/pipermail/openstack-dev/2015-November/079849.html
> 
> is pretty clear. Or if it's not feel free to reply to it and I'll give
> more information. :)
Will look and followup there.

Clark



More information about the OpenStack-dev mailing list