[tc][stable] Changing stable branch policy
akekane at redhat.com
Wed Nov 20 14:58:55 UTC 2019
My sincere apologies, but if you are certain that it is against policy and
not able to buy it then why one should be added to the team and even if its
done then why bothering about it.
Once again, sincere apologies.
On Wed, 20 Nov 2019 at 8:16 PM, Mohammed Naser <mnaser at vexxhost.com> wrote:
> On Wed, Nov 20, 2019 at 9:43 AM Abhishek Kekane <akekane at redhat.com>
> > Hi Matt,
> > For your kind information, I never asked to be to the core of
> stable-maintainer. Someone has recommended my name for it. So if you find
> it hard ir against the stable core policy, kindly remove me from this list.
> I will earn it with my efforts.
> Just for context, I don't think Matt was actually targeting you, it's
> actually something that has been raised a few times in the past with
> many other projects (i.e. Trove is one another recent memory). I'm
> happy to see you on the stable team for Glance. . :)
> > Thank you for your kind support.
> > Abhishek Kekane
> > On Wed, 20 Nov 2019 at 8:00 PM, Matt Riedemann <mriedemos at gmail.com>
> >> On 11/20/2019 1:18 AM, Zane Bitter wrote:
> >> > Because the core stable team is necessarily not as familiar with the
> >> > review/backport history of contributors in every project as the
> >> > individual project stable team is with contributors in each project.
> >> This is assuming that each project has a stable core team already, which
> >> a lot don't, that's why we get a lot of "hi I'm the PTL du jour on
> >> project X now please make me stable core even though I've never reviewed
> >> any stable branch changes before".
> >> With Tony more removed these days and I myself not wanting to vet every
> >> one of these "add me to the stable core team" requests, I'm more or less
> >> OK with the proposal so that it removes me as a bottleneck. That might
> >> mean people merge things on stable branches for their projects that
> >> don't follow the guidelines but so be it. If it's a problem hopefully
> >> they'll hear about it from their consumers, but if the project is in
> >> such maintenance mode anyway that they can break the stable guidelines,
> >> then they might not have many external consumers to complain anyway.
> >> Either way I don't need to be involved.
> >> So sure, +1 from me on the proposal given nova can still do what it's
> >> already been doing with a specific stable maint core team ACL in Gerrit.
> >> --
> >> Thanks,
> >> Matt
> > --
> > Thanks & Best Regards,
> > Abhishek Kekane
> Mohammed Naser — vexxhost
> D. 514-316-8872
> D. 800-910-1726 ext. 200
> E. mnaser at vexxhost.com
> W. https://vexxhost.com
Thanks & Best Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss