From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 176 is available for testing Date: Sat, 08 Jul 2023 11:28:00 +0000 Message-ID: <0f94600b-f00b-b72c-d614-b13ce60d4754@ipfire.org> In-Reply-To: <14953D83-593B-4E8C-9251-9437368A24BA@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7181840627862760295==" List-Id: --===============7181840627862760295== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello *, Core Update 176 is running on my testing machine for a couple of days by now, without any issues or anomalies whatsoever. From my perspective, this Core Update is ready to be released. @Michael: I'll send you a draft for the release announcement in due course. Thanks, and best regards, Peter M=C3=BCller > Thank you for your feedback. >=20 > I didn=E2=80=99t hear anything bad yet either. >=20 > -Michael >=20 >> On 29 Jun 2023, at 18:18, Adolf Belka wrote: >> >> >> Hi All, >> >> So far everything I have tested has worked as expected. That includes the = OpenVPN roadwarrior connection. >> >> Looking good so far :crossed_fingers: >> >> Regards, >> >> Adolf. >> >> >> On 29/06/2023 12:20, IPFire Project wrote: >>> IPFire Logo >>> there is a new post from Peter M=C3=BCller on the IPFire Blog: >>> *IPFire 2.27 - Core Update 176 is available for testing* >>> The next update, IPFire 2.27 - Core Update 176, is available for testi= ng. It features a toolchain and package updates (among the security-relevant = of them are Intel microcodes), brings the latest batch of bug fixes. >>> Click Here To Read More >>> The IPFire Project >>> Don't like these emails? Unsubscribe . >=20 --===============7181840627862760295==--