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: Scheduling of Core Update 173
Date: Mon, 23 Jan 2023 15:36:57 +0000	[thread overview]
Message-ID: <f63b82c5-48bc-9bca-ee09-b60807f497fd@ipfire.org> (raw)

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

Hello development folks,

above all, sorry for me being rather absent recently due to the usual bunch
of things on my plate, and the day only having 24 hours, which is way too
little for me to get all of that done.

[Insert a Monthy Python-style "anyway" here...]

With regards to Core Update 173, we already have quite something in it, including
a brand new kernel (thanks, Arne!), the QMI feature developed by Michael, and
a lot of other things that I currently cannot recall, but will once I'm writing
the changelog.

>From my side, updates for Tor, libloc and the Squid ASNBL helper are still
missing, and I will take care of that in due course. Aside from that, I'm working
through patchwork, and will get back to the authors of patches I have not merged
so far later, if necessary.

Closing the Core Update by the end of this week seems sensible to me, so we can
give it an extended testing phase, given the plethora of changes in it - in case
of QMI, we suspect it will break IPTV, but none of the core developers is able
to test that.

Please keep the patches coming (many thanks for them, as always), and let me
know if there are any questions/concerns/comments.

Thanks, and best regards,
Peter Müller (back to the batcave :-)


             reply	other threads:[~2023-01-23 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 15:36 Peter Müller [this message]
2023-01-23 17:37 ` Matthias Fischer
2023-01-23 18:08   ` Adolf Belka
2023-01-23 19:48     ` Matthias Fischer
2023-01-26 10:37 ` Adolf Belka

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=f63b82c5-48bc-9bca-ee09-b60807f497fd@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