From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Preliminary information regarding merge window closure for Core Update 168 Date: Tue, 03 May 2022 11:29:24 +0100 Message-ID: In-Reply-To: <6fdbb389-0c09-5388-a16c-87890a7e9b67@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7379577195430264388==" List-Id: --===============7379577195430264388== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 1 May 2022, at 09:32, Peter M=C3=BCller wro= te: >=20 > Hello development folks, >=20 > being in charge of mastering Core Update 168, I would like to close the mer= ge window for > it on Monday, May 9th. At the moment, we have a heap of updated packages in= it, an updated > linux-firmware, as well as contributions and bug fixes to the web interface= . Thank you all! >=20 > Yet to come is Stefan's work on the IPS, which he refers to as "IPSv4"; I d= id not have time > to go through that, but will hopefully do so today or on Wednesday. Also, C= ore Update 168 > comes with a Suricata update, which hopefully will finally cure things like= #12812. >=20 > Going through Patchwork, I seek review of the following patches, as they ar= e either beyond > my Perl/CUPS/... skills, or were handed in by myself: > - https://patchwork.ipfire.org/project/ipfire/patch/20220428142416.23557-1-= daniel.weismueller(a)ipfire.org/ > - https://patchwork.ipfire.org/project/ipfire/patch/20220425191245.1493-1-h= ofmann(a)leo-andres.de/ > - https://patchwork.ipfire.org/project/ipfire/patch/43e66e1b-b231-8869-4348= -8172d820d7a5(a)ipfire.org/ > - https://patchwork.ipfire.org/project/ipfire/patch/2a19b137-55c7-ecb4-6161= -8e87dc1a9a6b(a)ipfire.org/ > - https://patchwork.ipfire.org/project/ipfire/patch/9039a2e6-fcc4-e6d1-00b0= -9ed018592611(a)ipfire.org/ > - https://patchwork.ipfire.org/project/ipfire/patch/20220412103336.59296-1-= adolf.belka(a)ipfire.org/ > (@Michael: You told me to update HAproxy to the latest 2.4.x version, whic= h I did. Are you fine > with the non-LTS 2.5.x branch as well?) Yes I am, as long as it is supported. HAProxy has never introduced any breaki= ng changes for me, so I am happy. -Michael > So, please keep your contributions coming. As always, feel free to drop me = a line in case > of questions, comments, or criticism. >=20 > Thanks, and best regards, > Peter M=C3=BCller --===============7379577195430264388==--