From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: The Upcoming Core Update(s)
Date: Thu, 23 Nov 2023 15:45:39 +0000 [thread overview]
Message-ID: <D6AC7E01-3971-4D47-BF09-A1E7470CAF67@ipfire.org> (raw)
In-Reply-To: <f080612bfe31dc7c838f976435c17742@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
Hello Arne,
> On 23 Nov 2023, at 08:22, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> Am 2023-11-05 14:15, schrieb Michael Tremer:
>> Hello everyone,
>> Since this month’s video conference has been canceled, here is a couple of updates from my side:
>> * Core Update 181 has been branched yesterday. I have this running in my office for a little while and it seems to be a solid update. It also has a lot of security fixes, so please give it a good test that we can hopefully release this in two weeks.
>> * For the following update(s): what do we have in the pipeline? Just to coordinate that we don’t have too much in one update :)
>> Best,
>> -Michael
>
> I have grub-2.12-rc1 and i build a kernel update to 6.6.x which looks good. I plan for core183...
> We should consider to change the IPFire version number because if you update from older versions it load 1.5GB at once before install it.
Yes, I am happy to do this. It is kind of overdue and in this step we should consider taking all legacy versions from the server.
> Arne
next prev parent reply other threads:[~2023-11-23 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 13:15 Michael Tremer
2023-11-07 18:22 ` Peter Müller
2023-11-07 21:10 ` Adolf Belka
2023-11-21 20:39 ` Peter Müller
2023-11-21 20:50 ` Adolf Belka
2023-11-23 8:22 ` Arne Fitzenreiter
2023-11-23 15:45 ` Michael Tremer [this message]
2023-11-24 13:31 ` Peter Müller
2024-01-16 15:10 ` 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=D6AC7E01-3971-4D47-BF09-A1E7470CAF67@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