Open Stack

ONOS is not part of Neutron and hence Neutron Release team should not
be involved in its matters. If gerrit ACLs say otherwise, you should
fix the ACLs.

Ihar

On Tue, Apr 24, 2018 at 1:22 AM, Sangho Shin <sangho at opennetworking.org> wrote:
> Dear Neutron-Release team members,
>
> Can any of you handle the issue below?
>
> Thank you so much for your help in advance.
>
> Sangho
>
>
>> On 20 Apr 2018, at 10:01 AM, Sangho Shin <sangho at opennetworking.org> wrote:
>>
>> Dear Neutron-Release team,
>>
>> I wonder if any of you can add me to the network-onos-release member.
>> It seems that Vikram is busy. :-)
>>
>> Thank you,
>>
>> Sangho
>>
>>
>>
>>> On 19 Apr 2018, at 9:18 AM, Sangho Shin <sangho at opennetworking.org> wrote:
>>>
>>> Ian,
>>>
>>> Thank you so much for your help.
>>> I have requested Vikram to add me to the release team.
>>> He should be able to help me. :-)
>>>
>>> Sangho
>>>
>>>
>>>> On 19 Apr 2018, at 8:36 AM, Ian Wienand <iwienand at redhat.com> wrote:
>>>>
>>>> On 04/19/2018 01:19 AM, Ian Y. Choi wrote:
>>>>> By the way, since the networking-onos-release group has no neutron
>>>>> release team group, I think infra team can help to include neutron
>>>>> release team and neutron release team can help to create branches
>>>>> for the repo if there is no reponse from current
>>>>> networking-onos-release group member.
>>>>
>>>> This seems sane and I've added neutron-release to
>>>> networking-onos-release.
>>>>
>>>> I'm hesitant to give advice on branching within a project like neutron
>>>> as I'm sure there's stuff I'm not aware of; but members of the
>>>> neutron-release team should be able to get you going.
>>>>
>>>> Thanks,
>>>>
>>>> -i
>>>
>>
>