Open Stack

Tony Breeds wrote:
> 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:
>>> 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.

Exactly. As explained a couple weeks ago in the release countdown email[1]:

> 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:
> 
> ...
> branches:
>   - location: YOUR.PIKE.VERSION
>     name: stable/pike

[1]
http://lists.openstack.org/pipermail/openstack-dev/2017-August/120574.html

-- 
Thierry Carrez (ttx)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/c9e1b9f8/attachment.sig>