<html><body><p><font size="2"><br></font><tt><font size="2">Thierry Carrez <thierry@openstack.org> wrote on 08/17/2017 03:35:20 AM:<br>> From: Thierry Carrez <thierry@openstack.org></font></tt><br><tt><font size="2">> To: openstack-dev@lists.openstack.org</font></tt><br><tt><font size="2">> Date: 08/17/2017 03:37 AM</font></tt><br><tt><font size="2">> Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer <br>> stable/pike branch outlook</font></tt><br><tt><font size="2">> <br>> Tony Breeds wrote:<br>> > On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote:<br>> >><br>> >> Julien Danjou <julien@danjou.info> wrote on 08/16/2017 02:13:10 PM:<br>> >>> AFAIU it's impossible to cut a branch for our projects and release a rc1<br>> >>> because of the release model we use. The release team does not allow us<br>> >>> to do that. We need to release directly a stable version and cut a<br>> >>> branch.<br>> >>><br>> >>> I guess we'll do that in a couple of week, at release time.<br>> >><br>> >> That doesn't fit my understanding of cycle-with-intermediary, which is the<br>> >> the ceilometer release model per [0]. As I read the release model<br>> >> definitions [1], cycle-with-intermediary means that you can have<br>> >> intermediate releases *as well*, but you still have to have a cycle-ending<br>> >> release in line with the projects using the cycle-with-milestones model.<br>> >><br>> >> Can someone on the release team clarify this for us?<br>> > <br>> > That's correct the bit you're missing is cycle-with-intermediary doesn't<br>> > have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels<br>> > they have the code in shape for a release they'll tag that release and<br>> > cut a stable/pike branch at the tag point.<br>> <br>> Exactly. As explained a couple weeks ago in the release countdown email[1]:<br>> <br></font></tt><br><tt><font size="2">that email explicitly says: "</font></tt><tt>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</tt><tt><font size="2">"</font></tt><br><br><tt><font size="2">And that wasn't done for ceilometer. So it needs to be done, right?</font></tt><br><br><tt><font size="2">> > Deliverables following the cycle-with-intermediary model should also<br>> > create their Pike release branch next week. That means potentially<br>> > making a last Pike release, and in all cases posting the stable/pike<br>> > branch creation request:<br>> > <br>> > ...<br>> > branches:<br>> > - location: YOUR.PIKE.VERSION<br>> > name: stable/pike<br>> <br>> [1]<br>> <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-August/120574.html">http://lists.openstack.org/pipermail/openstack-dev/2017-August/120574.html</a><br>> <br>> -- <br>> Thierry Carrez (ttx)<br>> <br>> [attachment "signature.asc" deleted by William M Edmonds/Raleigh/<br>> IBM] <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></font></tt><BR>
</body></html>