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