public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Stefan Schantl <stefan.schantl@ipfire.org>
Cc: development@lists.ipfire.org
Subject: Re: Core 199 Feedback
Date: Tue, 25 Nov 2025 10:43:15 +0000	[thread overview]
Message-ID: <B068A992-B951-4030-B4D4-06ED7152EF94@ipfire.org> (raw)
In-Reply-To: <19ab15ebf80.27e7.cac9d3ffac9e24d09d20af05166fd73b@ipfire.org>

Hello Stefan,

Thank you for the feedback.

The testing release announcement is just going out now:

  https://www.ipfire.org/blog/ipfire-2-29-core-update-199-is-available-for-testing

So far, I am not aware of any regressions, but we shall see this very soon when we have some more feedback from the community.

I was hopefully to have another update in testing before Christmas, but I suppose the timeline does not allow this. So we should still ensure that we are able to release this well before Christmas so that we don’t give admins a last-minute update job.

So, please, test, test, test!

-Michael

> On 23 Nov 2025, at 15:39, Stefan Schantl <stefan.schantl@ipfire.org> wrote:
> 
> Hello developers,
> 
> today I upgraded my productive system to the latest development version
> of core update 199.
> 
> As far as I can see, there are no bigger issues in the update.
> 
> The process run's smooth and without any problems.
> 
> The system proper came up during reboot and also the connection to the
> internet via QMI has been established successfull again.
> 
> The IDS is working and reporting properly.
> IPSec Net-to-Net connections are established again and I can process
> data through it.
> 
> The LLDPD service did not come up after the first reboot and also the
> previous selected option to enable the service and the choosen
> description was gone dure an overwrite of the settings file in
> /var/ipfire/lldp. Thats totaly okay for me because I had manually
> installed and tested the feature, any in my personal opinion a very
> limited amount of other testers may be affected by this too.
> 
> That are the first test results / feedback for now.
> 
> Best regards,
> 
> -Stefan



      reply	other threads:[~2025-11-25 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23 15:39 Stefan Schantl
2025-11-25 10:43 ` 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=B068A992-B951-4030-B4D4-06ED7152EF94@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=stefan.schantl@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