For the record, I added Lucas to the gerrit group. I assume he will
mostly focus on OVN patches. You are still welcome to review other
repo patches, and if you stick to it, I am happy to expand your role
to cover all of them.
As for OVN, you only have one +2, and existing stable reviewers may
not
Hi,
> Please tell me who from the OVN group is ready to take the burden, and
> I will make you part of neutron-stable-maint. I think it's ok to be
> more laissez faire with backports for subprojects than we were used
> to, with the recent drop in core team membership and reduced capacity.
Great!
Please tell me who from the OVN group is ready to take the burden, and
I will make you part of neutron-stable-maint. I think it's ok to be
more laissez faire with backports for subprojects than we were used
to, with the recent drop in core team membership and reduced capacity.
Ihar
On Wed, Dec
On 20 December 2017 at 00:27, Miguel Angel Ajo Pelayo
wrote:
> If we could have one member from networking-ovn on the
> neutron-stable-maint team that would be great. That means the member would
> have to be trusted not to handle neutron-patches when not knowing what he's
>
That may help, of course, but I gues it could also be capacity related.
On Wed, Dec 20, 2017 at 11:42 AM Takashi Yamamoto
wrote:
> On Wed, Dec 20, 2017 at 7:18 PM, Lucas Alvares Gomes
> wrote:
> > Hi,
> >
> >>> Hi all,
> >>>
> >>> Just sending this
On Wed, Dec 20, 2017 at 7:18 PM, Lucas Alvares Gomes
wrote:
> Hi,
>
>>> Hi all,
>>>
>>> Just sending this email to try to understand the model for stable branch
>>> maintenance in networking-ovn (potentially other neutron drivers too).
>>>
>>> Right now, only members of
Hi,
>> Hi all,
>>
>> Just sending this email to try to understand the model for stable branch
>> maintenance in networking-ovn (potentially other neutron drivers too).
>>
>> Right now, only members of the ``neutron-stable-maint`` gerrit group are
>> able to approve patches for the stable
If we could have one member from networking-ovn on the neutron-stable-maint
team that would be great. That means the member would have to be trusted
not to handle neutron-patches when not knowing what he's doing, and of
course, follow the stable guidelines, which are absolutely important. But I
On 19 December 2017 at 08:21, Lucas Alvares Gomes
wrote:
> Hi all,
>
> Just sending this email to try to understand the model for stable branch
> maintenance in networking-ovn (potentially other neutron drivers too).
>
> Right now, only members of the