From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Core Update 157 Date: Tue, 18 May 2021 09:53:14 +0100 Message-ID: In-Reply-To: <7a3cb033-f747-7bc0-1f09-6284906346fd@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0830746667496030106==" List-Id: --===============0830746667496030106== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 17 May 2021, at 23:02, Peter M=C3=BCller wr= ote: >=20 > Hello Michael, >=20 > it just occurred to me that there are two patches fixing a nasty bug in fwh= osts.cgi still left in the queue: >=20 > - https://patchwork.ipfire.org/patch/4199/ > - https://patchwork.ipfire.org/patch/4206/ >=20 > Since fwhosts.cgi was primarily written by Alex, I asked him to review thes= e, but have not heard anything back. A timeout cannot be taken as an acknowledgement. Did you try getting in touch= with Alex? -Michael > Shall we merge them anyway? >=20 > Thanks, and best regards, > Peter M=C3=BCller >=20 >=20 >> Hello, >>=20 >>> On 17 May 2021, at 22:28, Peter M=C3=BCller = wrote: >>>=20 >>> Hello Michael, >>>=20 >>> thanks for your message. >>>=20 >>> I am currently working on dropping all the packages and add-ons, as we di= scussed earlier >>> this month. A patchset will be ready within the next few hours, ideally b= efore midnight, >>> Deo volente. >>=20 >> Cool. Thank you. This won=E2=80=99t make it into Core Update 157 because I= want to allow some time for discussion. >>=20 >>> Aside from that, I do not have anything stable enough to make it into Cor= e Update 158. >>=20 >> Thanks for letting me know :) >>=20 >> -Michael >>=20 >>> Thanks, and best regards, >>> Peter M=C3=BCller >>>=20 >>>=20 >>>> Hello, >>>>=20 >>>> Because there are so many things going on at the same time, I would like= to start a brief main thread about the upcoming Core Update(s). >>>>=20 >>>> The original plan was to have this closed a while ago because Core Updat= e 156 has already gone out. But then I decided to wait for a couple of smalle= r things until we had a security vulnerability reported which I wanted to inv= estigate more (#12616 and #12619). It is not too bad, but I would like to shi= p at least a fix that is good enough to mitigate it. We might need some more = time to figure out the details around the other half of the solution for this= problem. >>>>=20 >>>> Now this update has become *very* large. It is the largest update we hav= e ever had and that might break things. Therefore I do not want to merge anyt= hing more that has to go into the core system, but add-on packages are fine. >>>>=20 >>>> In fact, the build that I just pushed should be the final one, unless we= find any other problems. Does anyone have anything urgent and small left? Ot= herwise Core Update 158 will be open as soon as 157 has hit the master branch. >>>>=20 >>>> In order to coordinate that a little bit more and have a good and hopefu= lly brief merge window, what should be in it? >>>>=20 >>>> * Fixes for #12616 >>>> * Can we finish the migration away from Python 2? >>>> * Drop the packages discussed at the last conference call (https://wiki.= ipfire.org/devel/telco/2021-05-03)? >>>> * VPNs for iOS (https://patchwork.ipfire.org/project/ipfire/list/?series= =3D1323)? >>>>=20 >>>> What else are you guys working on that is ready for prime-time? >>>>=20 >>>> -Michael >>>>=20 >>=20 --===============0830746667496030106==--