From: Michael Tremer <michael.tremer@ipfire.org>
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 [thread overview]
Message-ID: <A56F6FD1-C33B-453B-99E2-F82D6A530634@ipfire.org> (raw)
In-Reply-To: <6fdbb389-0c09-5388-a16c-87890a7e9b67@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
Hello,
> On 1 May 2022, at 09:32, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello development folks,
>
> being in charge of mastering Core Update 168, I would like to close the merge 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!
>
> Yet to come is Stefan's work on the IPS, which he refers to as "IPSv4"; I did not have time
> to go through that, but will hopefully do so today or on Wednesday. Also, Core Update 168
> comes with a Suricata update, which hopefully will finally cure things like #12812.
>
> Going through Patchwork, I seek review of the following patches, as they are 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-hofmann(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, which 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 breaking 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.
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2022-05-03 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 8:32 Peter Müller
2022-05-03 10:29 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A56F6FD1-C33B-453B-99E2-F82D6A530634@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox