osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[release][stable][trove] Please add Lingxian Kong to trove-stable-maint group



Sent from my iPhone

> On Apr 11, 2019, at 4:47 PM, Lingxian Kong <anlin.kong at gmail.com> wrote:
> 
> Matt,
> 
> I've already replied in the patch, since you also mentioned the patch here, i think it's necessary also reply you here.
> 
> That patch failed to get attention from other team members and the community who are not interested in such change, as the PTL, i have to merge it myself to not block other patches. At the same time, some users were complaining the current trove image build approach, which could be improved with that patch.
> 
> If self-approved is something you disagree, I'd appreciate if you could offer some help for the review.

Should we perhaps look into the possibility of removing Trove from following stable policy by any chance?

Itâ??s not ideal but I feel if the projects needs to start getting overhauled and brought to a good place, we may need to do this at cost of its stability?

> ---
> Cheers,
> Lingxian Kong
> Catalyst Cloud
> 
> 
>> On Fri, Apr 12, 2019 at 5:11 AM Matt Riedemann <mriedemos at gmail.com> wrote:
>> On 4/9/2019 7:37 PM, Tony Breeds wrote:
>> > Being PTL doesn't give you automatic rights to the stable branches as the
>> > requirements there are different.  I'm really happy to start mentoring
>> > you on the stable policy and have you review stables patches then after
>> > 3months(ish) we can add you to the stable group assuming everything
>> > looks good.
>> 
>> Maybe we should start a FAQ for this in the stable docs. This question 
>> comes up every release.
>> 
>> BTW, this is a good example of why PTLs aren't automatically on the 
>> stable team:
>> 
>> https://review.openstack.org/#/c/651672/
>> 
>> That change is extremely questionable as a backport.
>> 
>> -- 
>> 
>> Thanks,
>> 
>> Matt
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190411/5d529c00/attachment.html>