apologies, I'm currently away on vacation (for a while)
we can merge the stable/pike patch as it seems there are others dependent on
it. I don't believe it affects us either way.
I don't see the auto patch that creates tag so I guess we need to do it via
releases project
--
gord
________________________________
From: Sean McGinnis <sean.mcgin...@gmx.com>
Sent: Friday, August 18, 2017 4:31:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike
branch outlook
> > >>
> > >> 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.
> >
>
> that email explicitly says: "Deliverables following the
> cycle-with-intermediary model should also create their Pike release branch
> next week. That means potentially making a last Pike release, and in all
> cases posting the stable/pike branch creation request"
>
> And that wasn't done for ceilometer. So it needs to be done, right?
>
Yes, I just double checked, and there has not been a pike release yet for
ceilometer. That does need to be done soon.
Sean
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
