Open Stack

> On 17 May 2016, at 16:46, Doug Hellmann <doug at doughellmann.com> wrote:
> 
> Excerpts from Ihar Hrachyshka's message of 2016-05-17 14:39:40 +0200:
>> 
>>> On 17 May 2016, at 14:27, Doug Hellmann <doug at doughellmann.com> wrote:
>>> 
>>> Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200:
>>>> 
>>>>> On 16 May 2016, at 21:16, Armando M. <armamig at gmail.com> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>> On 16 May 2016 at 05:15, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>>>> 
>>>>>> On 11 May 2016, at 22:05, Sukhdev Kapur <sukhdevkapur at gmail.com> wrote:
>>>>>> 
>>>>>> 
>>>>>> Folks,
>>>>>> 
>>>>>> I am happy to announce that Mitaka release for L2 Gateway is released and now available at https://pypi.python.org/pypi/networking-l2gw.
>>>>>> 
>>>>>> You can install it by using "pip install networking-l2gw"
>>>>>> 
>>>>>> This release has several enhancements and fixes for issues discovered in liberty release.
>>>>> 
>>>>> How do you release it? I think the way to release new deliverables as of Newton dev cycle is thru openstack/releases repository, as documented in https://review.openstack.org/#/c/308984/
>>>>> 
>>>>> Have you pushed git tag manually?
>>>>> 
>>>>> I can only see the stable branch, tags can only be pushed by the neutron-release team.  
>>>> 
>>>> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
>>>> 
>>>> Git tag history suggests that Carl pushed it (manually I guess?) It seems that we release some independent deliverables thru openstack/releases, and some manually pushing tags into repos.
>>>> 
>>>> I would love if we can consolidate all our releases to use a single automation mechanism (openstack/releases patches), independent of release model. For that, I would like to hear from release folks whether we are allowed to use openstack/releases repo for release:independent deliverables that are part of an official project (neutron).
>>> 
>>> We're working on it. This cycle we've expanded coverage of the releases
>>> repo to all official projects using cycle-based models.
>>> 
>>>> 
>>>> [Note that it would not mean we move the oversight burden for those deliverables onto release team; neutron-release folks would still need to approve them; it’s only about technicalities, not governance]
>>>> 
>>>> The existence of the following git directory suggests that it’s supported:
>>>> 
>>>> https://github.com/openstack/releases/tree/master/deliverables/_independent
>>>> 
>>>> We already have some networking-* subprojects there, like networking-bgpvpn or networking-odl. I would love to see all new releases tracked there.
>>> 
>>> Any official projects following the independent model may use the
>>> openstack/releases repository to record their releases after they
>>> are tagged.
>> 
>> You mean we should follow the steps:
>> - first, push git tag manually;
>> - then, propose openstack/releases patch describing the new tag?
> 
> Yes.
> 
>> 
>> If that’s the case, it was not exactly followed for some late neutron stadium releases, like: https://review.openstack.org/#/c/308962/
>> 
>> Actually, that later one created the tag in the repo for us. So what’s the reason to take the first step manually?
> 
> Creating the tags is still a manual step, even when you submit the
> request and the release team does it for you. We've said we would help a
> few teams who asked, but most teams should tag themselves before
> recording the results in the releases repo. I expect this to change
> after newton, when the automation work is done.

Oh, that’s great to know. I haven’t realized that it’s not automated yet, and that release folks expect tags to be created before openstack/releases patches are sent for release:independent. I assume it’s documented somewhere?..

Ihar