public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 170
Date: Wed, 27 Jul 2022 09:28:37 +0000	[thread overview]
Message-ID: <53ca7634-e481-b2db-1d0a-19bbf516ccb9@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]

Hello development folks,

first, apologies for being rather unresponsive recently. Due to some technical
difficulties, I will that way until next week - apologies also to all the people
that have been trying to reach me via the phone.

Being in charge of mastering Core Update 170, I would like to keep this update
open until August 8th, to give everyone (including myself) sufficient time to
hand in all the things they want to have in this update.

 From my end, this includes a kernel update as well as some hardening changes.
Also, I noticed several things (kmod, samba, bash, ...) to be in need of an
update, and will take care of them as well.

We won't probably include them into C170, but for the next updates, I would like
to see particularly Perl and Python being updated. Any volounteers are welcomed. :-)

Also, new versions of u-boot and the ARM firmware conglomerate have been released,
though I need to check with Arne whether we can ship them with C170 already, or
if they require some more time.

OpenSSL 3.x is currently blocked by monitoring-plugins. As soon as the latter
released a stable version, we can update OpenSSL as well; all other blockers
have been resolved.

Thanks to Michael for taking care of things during my absence. As always, feel
free to drop me a line in case of any questions or comments.

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2022-07-27  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  9:28 Peter Müller [this message]
2022-07-27 10:06 ` Adolf Belka
2022-07-28 21:06 ` Michael Tremer

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=53ca7634-e481-b2db-1d0a-19bbf516ccb9@ipfire.org \
    --to=peter.mueller@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