From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.29 - Core Update 183 is available for testing Date: Tue, 23 Jan 2024 15:19:23 +0100 Message-ID: <0e71b0e3-ae87-42fe-ab78-67040966526b@ipfire.org> In-Reply-To: <1C40C90F-925D-4284-AD40-CFC98BFDF6C9@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5157414300365177299==" List-Id: --===============5157414300365177299== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, One thing I noticed with the Core Update 183 Testing announcement. It doesn't= announce the EOL of the Icinga addon and its removal in Core Update 185 as w= e discussed in the last Video Call meeting. Regards, Adolf. On 23/01/2024 15:10, Michael Tremer wrote: >=20 >=20 >> On 23 Jan 2024, at 13:23, Adolf Belka wrote: >> >> Hi All, >> >> On 23/01/2024 14:20, Adolf Belka wrote: >>> Hi All, >>> >>> On 23/01/2024 13:11, Adolf Belka wrote: >>>> Hi All, >>>> >>>> First feedback is that the email notification of the Testing Release is = great. The old version was always a bit dull and on my mobile it always ended= up with dark writing on a dark background. >>>> >>>> Now the email notification looks the same on my desktop and my mobile an= d is much more eye catching. >>>> >>>> On the top of the WUI page the IPFire_ has replaced the fiery penguin bu= t the underscoring indicating that it is a link ends up going above the under= score character. Was that intended? It's not a big thing and I can live with = it no problems but it did just look a bit peculiar at first glance. >>>> >>> >>> Ignore my comment. I had to refresh the browser page as it was keeping mo= st of it from the cache. I had not seen all the changes previously due to the= cache. >>> >>> Not as simple as refreshing the browser page. One of my systems now has t= he full new version but the other is still showing mostly the old version wit= h just the tux icon changed. >>> >> I had to go into firefox settings and tell it to clear the cached web cont= ent. Then the IPFire WUI is now fully updated. Sorry for the noise. >=20 > Ah I got you now=E2=80=A6 >=20 > I was wondering what we can do about this=E2=80=A6 Browsers will definitely= cache the old CSS and so we might actually show a lot of garbage until thing= s get refreshed. >=20 > A lazy solution could simply be to rename the CSS file. That way, browsers = definitely will fetch it again. Otherwise, they should actually check every t= ime if the content they have is actually current as we do not send any long t= ime caching headers. But some people like to break RFCs in favour of =E2=80= =9Cperformance=E2=80=9D. >=20 > -Michael >=20 >> >> Regards, >> >> Adolf. >> >>> Regards, >>> >>> Adolf. >>> >>> >>>> The upgrade process went fine, including the reboot. Everything cam back= with no issues. >>>> >>>> Will now start to look at the various screens and test things out. >>>> >>>> Regards, >>>> Adolf. >>>> >>>> On 23/01/2024 11:55, IPFire Project wrote: >>>>> It is time for testing the next version of IPFire - and it is going to = be a big one: A new major version - IPFire 2.29 - Core Update 183. There is a= n update of the design of the web user interface, a fresh kernel based on Lin= ux 6.6, a lot of package updates and improvements and bug fixes throughout th= e entire system. >>>>> =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C = =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80= =8C =E2=80=8C =E2=80=8C =E2=80=8C >>>>> >>>>> >>>>> IPFire_ >>>>> >>>>> >>>>> IPFire 2.29 - Core Update 183 is available for testing >>>>> >>>>> It is time for testing the next version of IPFire - and it is going to = be a big one: A new major version - IPFire 2.29 - Core Update 183. There is a= n update of the design of the web user interface, a fresh kernel based on Lin= ux 6.6, a lot of package updates and improvements and bug fixes throughout th= e entire system. >>>>> >>>>> Read The Full Post On Our Blog >>>>> >>>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe 8,= 45711 Datteln, Germany >>>>> >>>>> Unsubscribe >=20 >=20 --===============5157414300365177299==--