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? [0] https://github.com/openstack/releases/blob/bf890914c1ec5bcd41d70140e80ef8d39df64c86/deliverables/pike/ceilometer.yaml#L3 [1] https://releases.openstack.org/reference/release_models.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170816/e7384804/attachment.html>