Open Stack

On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote:
> 
> Julien Danjou <julien at danjou.info> wrote on 08/16/2017 02:13:10 PM:
> > From: Julien Danjou <julien at danjou.info>
> > To: "Eric S Berglund" <esberglu at us.ibm.com>
> > Cc: openstack-dev at lists.openstack.org
> > Date: 08/16/2017 02:14 PM
> > Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer
> > stable/pike branch outlook
> >
> > On Wed, Aug 16 2017, Eric S Berglund wrote:
> >
> > Hi Eric,
> >
> > > Is there an outlook for cutting a pike branch for ceilometer?
> > > We currently can't run our 3rd party CI against pike without a pike
> > > release branch and are deciding whether it's worth the time to
> > > implement a workaround.
> >
> > AFAIU it's impossible to cut a branch for our projects and release a rc1
> > because of the release model we use. The release team does not allow us
> > to do that. We need to release directly a stable version and cut a
> > branch.
> >
> > I guess we'll do that in a couple of week, at release time.
> 
> That doesn't fit my understanding of cycle-with-intermediary, which is the
> the ceilometer release model per [0]. As I read the release model
> definitions [1], cycle-with-intermediary means that you can have
> intermediate releases *as well*, but you still have to have a cycle-ending
> release in line with the projects using the cycle-with-milestones model.
> 
> Can someone on the release team clarify this for us?

That's correct the bit you're missing is cycle-with-intermediary doesn't
have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
they have the code in shape for a release they'll tag that release and
cut a stable/pike branch at the tag point.

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/480fe6a6/attachment.sig>