<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div id="AppleMailSignature" dir="ltr">Sent from my iPhone</div><div dir="ltr"><br>On Apr 11, 2019, at 4:47 PM, Lingxian Kong <<a href="mailto:anlin.kong@gmail.com">anlin.kong@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Matt,</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">I've already replied in the patch, since you also mentioned the patch here, i think it's necessary also reply you here.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default"><div class="gmail_default"><font face="monospace, monospace">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.</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">If self-approved is something you disagree, I'd appreciate if you could offer some help for the review.</font></div></div></div></div></div></blockquote><div><br></div><div>Should we perhaps look into the possibility of removing Trove from following stable policy by any chance?</div><div><br></div><div>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?</div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font face="monospace, monospace">---</font></div><div><font face="monospace, monospace">Cheers,<br>Lingxian Kong</font></div><div><font face="monospace, monospace">Catalyst Cloud</font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 12, 2019 at 5:11 AM Matt Riedemann <<a href="mailto:mriedemos@gmail.com">mriedemos@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 4/9/2019 7:37 PM, Tony Breeds wrote:<br>
> Being PTL doesn't give you automatic rights to the stable branches as the<br>
> requirements there are different. I'm really happy to start mentoring<br>
> you on the stable policy and have you review stables patches then after<br>
> 3months(ish) we can add you to the stable group assuming everything<br>
> looks good.<br>
<br>
Maybe we should start a FAQ for this in the stable docs. This question <br>
comes up every release.<br>
<br>
BTW, this is a good example of why PTLs aren't automatically on the <br>
stable team:<br>
<br>
<a href="https://review.openstack.org/#/c/651672/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/651672/</a><br>
<br>
That change is extremely questionable as a backport.<br>
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt<br>
<br>
</blockquote></div>
</div></blockquote></body></html>