<div dir="ltr"><div dir="ltr">If we decide to follow the depreciation process we can wait until tomorrow or Wednesday early in the morning. <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 29 mars 2021 à 16:52, Ghanshyam Mann <<a href="mailto:gmann@ghanshyammann.com">gmann@ghanshyammann.com</a>> a écrit :<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 Mon, 29 Mar 2021 09:26:31 -0500 Slawek Kaplonski <<a href="mailto:skaplons@redhat.com" target="_blank">skaplons@redhat.com</a>> wrote ----<br>
> Hi,<br>
> <br>
> On Mon, Mar 29, 2021 at 08:53:58AM -0500, Ghanshyam Mann wrote:<br>
> > ---- On Mon, 29 Mar 2021 06:14:06 -0500 Akihiro Motoki <<a href="mailto:amotoki@gmail.com" target="_blank">amotoki@gmail.com</a>> wrote ----<br>
> > > On Mon, Mar 29, 2021 at 8:07 PM Slawek Kaplonski <<a href="mailto:skaplons@redhat.com" target="_blank">skaplons@redhat.com</a>> wrote:<br>
> > > ><br>
> > > > Hi,<br>
> > > ><br>
> > > > On Mon, Mar 29, 2021 at 11:52:59AM +0200, Herve Beraud wrote:<br>
> > > > > Hello,<br>
> > > > ><br>
> > > > > The main question is, does the previous Victoria version [1] will be<br>
> > > > > compatible with the latest neutron changes and with the latest engine<br>
> > > > > facade introduced during Wallaby?<br>
> > > ><br>
> > > > It won't be compatible. Networking-midonet from Victoria will not work properly<br>
> > > > with Neutron Wallaby.<br>
> > > ><br>
> > > > ><br>
> > > > > Releasing an unfixed engine facade code is useless, so we shouldn't release<br>
> > > > > a new version of networking-midonet, because the project code won't be<br>
> > > > > compatible with the rest of our projects (AFAIK neutron), unless, the<br>
> > > > > previous version will not compatible either, and, unless, not releasing a<br>
> > > > > Wallaby version leave the project branch uncut and so leave the<br>
> > > > > corresponding series unmaintainable, and so unfixable a posteriori.<br>
> > > > ><br>
> > > > > If we do not release a new version then we will use a previous version of<br>
> > > > > networking-midonet. This version will be the last Victoria version [1].<br>
> > > > ><br>
> > > > > I suppose that this version (the victoria version) isn't compatible with<br>
> > > > > the new facade engine either, isn't it?<br>
> > > ><br>
> > > > Correct. It's not compatible.<br>
> > > ><br>
> > > > ><br>
> > > > > So release or not release a new version won't solve the facade engine<br>
> > > > > problem, isn't?<br>
> > > ><br>
> > > > Yes.<br>
> > > ><br>
> > > > ><br>
> > > > > You said that neutron evolved and networking-midonet didn't, hence even if<br>
> > > > > we release networking-midonet in the current state it will fail too, isn't<br>
> > > > > it?<br>
> > > ><br>
> > > > Also yes :)<br>
> > > ><br>
> > > > ><br>
> > > > > However, releasing a new version and branching on it can give you the<br>
> > > > > needed maintenance window to allow you to fix the issue later, when your<br>
> > > > > gates will be fixed and then patches backported. git tags are cheap.<br>
> > > > ><br>
> > > > > We should notice that since Victoria some patches have been merged in<br>
> > > > > Wallaby so even if they aren't ground breaking changes they are changes<br>
> > > > > that it is worth to release.<br>
> > > > ><br>
> > > > > From a release point of view I think it's worth it to release a new version<br>
> > > > > and to cut Wallaby. We are close to the it's deadline. That will land the<br>
> > > > > available delta between Victoria and Wallaby. That will allow to fix the<br>
> > > > > engine facade by opening a maintenance window. If the project is still<br>
> > > > > lacking maintainers in a few weeks / months, this will allow a more smooth<br>
> > > > > deprecation of this one.<br>
> > > > ><br>
> > > > > Thoughts?<br>
> > > ><br>
> > > > Based on Your feedback I agree that we should release now what we have. Even if<br>
> > > > it's broken we can then fix it and backport fixes to stable/wallaby branch.<br>
> > > ><br>
> > > > @Akihiro: are You ok with that too?<br>
> > > <br>
> > > I was writing another reply and did not notice this mail.<br>
> > > While I still have a doubt on releasing the broken code (which we are<br>
> > > not sure can be fixed soon or not),<br>
> > > I am okay with either decision.<br>
> > <br>
> > Yeah, releasing broken code and especially where we do not if there will be<br>
> > maintainer to fix it or not seems risky for me too.<br>
> > <br>
> > One option is to deprecate it for wallaby which means follow the deprecation steps<br>
> > mentioned in project-team-guide[1]. If maintainers show up then it can be un-deprecated. <br>
> > With that, we will not have any compatible wallaby version which I think is a better<br>
> > choice than releasing the broken code.<br>
> <br>
> We were asking about that some time ago already and then some new maintainers<br>
> stepped in. But as now there is that problem again with networking-midonet I'm<br>
> fine to deprecate it (or ask about it again at least).<br>
> But isn't it too late in the cycle now? Last time when we were doing that it was<br>
> before milestone-2 IIRC. Now we are almost at the end of the cycle. Should we do<br>
> it still now?<br>
<br>
As there is nothing released for Wallaby[1], we can still do this. As per the process, TC<br>
can merge the required patches on that repo if no core is available to +A.<br>
<br>
> If yes, how much time do we really have to e.g. ask for some new maintainers?<br>
> <br>
<br>
I will say asap :) but I think the release team can set the deadline as they have to take care<br>
of release things.<br>
<br>
[1] <a href="https://opendev.org/openstack/releases/src/commit/30492c964f5d7eb85d806086c5b1c656b5c9e9f9/deliverables/wallaby/networking-midonet.yaml" rel="noreferrer" target="_blank">https://opendev.org/openstack/releases/src/commit/30492c964f5d7eb85d806086c5b1c656b5c9e9f9/deliverables/wallaby/networking-midonet.yaml</a><br>
<br>
<br>
-gmann<br>
<br>
> > <br>
> > Releasing the broken code now with the hope of someone will come up and fix it with<br>
> > backport makes me a little uncomfortable and if it did not get fix then we will live<br>
> > with broken release forever. <br>
> > <br>
> > <br>
> > [1]<a href="https://docs.openstack.org/project-team-guide/repository.html#deprecating-a-repository" rel="noreferrer" target="_blank">https://docs.openstack.org/project-team-guide/repository.html#deprecating-a-repository</a><br>
> > <br>
> > -gmann<br>
> > <br>
> > > <br>
> > > ><br>
> > > > ><br>
> > > > > [1]<br>
> > > > > <a href="https://opendev.org/openstack/releases/src/branch/master/deliverables/victoria/networking-midonet.yaml" rel="noreferrer" target="_blank">https://opendev.org/openstack/releases/src/branch/master/deliverables/victoria/networking-midonet.yaml</a><br>
> > > > ><br>
> > > > > Le lun. 29 mars 2021 à 10:32, Slawek Kaplonski <<a href="mailto:skaplons@redhat.com" target="_blank">skaplons@redhat.com</a>> a<br>
> > > > > écrit :<br>
> > > > ><br>
> > > > > > Hi,<br>
> > > > > ><br>
> > > > > > We have opened release patch for networking-midonet [1] but our concern<br>
> > > > > > about<br>
> > > > > > that project is that its gate is completly broken since some time thus we<br>
> > > > > > don't really know if the project is still working and valid to be released.<br>
> > > > > > In Wallaby cycle Neutron for example finished transition to the engine<br>
> > > > > > facade,<br>
> > > > > > and patch to adjust that in networking-midonet is still opened [2] (and<br>
> > > > > > red as<br>
> > > > > > there were some unrelated issues with most of the jobs there).<br>
> > > > > ><br>
> > > > > > In the past we had discussion about networking-midonet project and it's<br>
> > > > > > status<br>
> > > > > > as the official Neutron stadium project. Then some new folks stepped in to<br>
> > > > > > maintain it but now it seems a bit like (again) it lacks of maintainers.<br>
> > > > > > I know that it is very late in the cycle now so my question to the TC and<br>
> > > > > > release teams is: should we release stable/wallaby with its current state,<br>
> > > > > > even if it's broken or should we maybe don't release it at all until its<br>
> > > > > > gate<br>
> > > > > > will be up and running?<br>
> > > > > ><br>
> > > > > > [1] <a href="https://review.opendev.org/c/openstack/releases/+/781713" rel="noreferrer" target="_blank">https://review.opendev.org/c/openstack/releases/+/781713</a><br>
> > > > > > [2] <a href="https://review.opendev.org/c/openstack/networking-midonet/+/770797" rel="noreferrer" target="_blank">https://review.opendev.org/c/openstack/networking-midonet/+/770797</a><br>
> > > > > ><br>
> > > > > > --<br>
> > > > > > Slawek Kaplonski<br>
> > > > > > Principal Software Engineer<br>
> > > > > > Red Hat<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > --<br>
> > > > > Hervé Beraud<br>
> > > > > Senior Software Engineer at Red Hat<br>
> > > > > irc: hberaud<br>
> > > > > <a href="https://github.com/4383/" rel="noreferrer" target="_blank">https://github.com/4383/</a><br>
> > > > > <a href="https://twitter.com/4383hberaud" rel="noreferrer" target="_blank">https://twitter.com/4383hberaud</a><br>
> > > > > -----BEGIN PGP SIGNATURE-----<br>
> > > > ><br>
> > > > > wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+<br>
> > > > > Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+<br>
> > > > > RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP<br>
> > > > > F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G<br>
> > > > > 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g<br>
> > > > > glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw<br>
> > > > > m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ<br>
> > > > > hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0<br>
> > > > > qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y<br>
> > > > > F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3<br>
> > > > > B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O<br>
> > > > > v6rDpkeNksZ9fFSyoY2o<br>
> > > > > =ECSj<br>
> > > > > -----END PGP SIGNATURE-----<br>
> > > ><br>
> > > > --<br>
> > > > Slawek Kaplonski<br>
> > > > Principal Software Engineer<br>
> > > > Red Hat<br>
> > > <br>
> > > <br>
> > <br>
> <br>
> -- <br>
> Slawek Kaplonski<br>
> Principal Software Engineer<br>
> Red Hat<br>
> <br>
<br>
</blockquote></div><br clear="all"><br>-- <br><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>Hervé Beraud</div><div>Senior Software Engineer at Red Hat</div><div>irc: hberaud</div><div><a href="https://github.com/4383/" target="_blank">https://github.com/4383/</a></div><div><a href="https://twitter.com/4383hberaud" target="_blank">https://twitter.com/4383hberaud</a><br></div><div>-----BEGIN PGP SIGNATURE-----<br><br>wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+<br>Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+<br>RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP<br>F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G<br>5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g<br>glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw<br>m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ<br>hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0<br>qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y<br>F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3<br>B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O<br>v6rDpkeNksZ9fFSyoY2o<br>=ECSj<br>-----END PGP SIGNATURE-----<br><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div>