Re: IPFire 2.29 - Core Update 183 is available for testing

Re: IPFire 2.29 - Core Update 183 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

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 and is much more eye catching.

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 underscore 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.

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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> 
> 
>   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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
> 
> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
> 
> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
> 
> Unsubscribe <https://www.ipfire.org/unsubscribe>
> 

Re: IPFire 2.29 - Core Update 183 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]

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 and is much more eye catching.
>
> 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 underscore 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 most 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 the full new version but the other is still showing mostly the old version with just the tux icon changed.

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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>
>>
>>   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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>
>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>
>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>
>> Unsubscribe <https://www.ipfire.org/unsubscribe>
>>

Re: IPFire 2.29 - Core Update 183 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 2715 bytes --]

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 and is much more eye catching.
>>
>> 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 underscore 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 most 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 the full new version but the other is still showing mostly the old version with just the tux icon changed.
>
I had to go into firefox settings and tell it to clear the cached web content. Then the IPFire WUI is now fully updated. Sorry for the noise.

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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>
>>>
>>>   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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>
>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>>
>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>>
>>> Unsubscribe <https://www.ipfire.org/unsubscribe>
>>>

Re: IPFire 2.29 - Core Update 183 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 3386 bytes --]



> On 23 Jan 2024, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> 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 and is much more eye catching.
>>> 
>>> 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 underscore 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 most 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 the full new version but the other is still showing mostly the old version with just the tux icon changed.
>> 
> I had to go into firefox settings and tell it to clear the cached web content. Then the IPFire WUI is now fully updated. Sorry for the noise.

Ah I got you now…

I was wondering what we can do about this… Browsers will definitely cache 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 definitely will fetch it again. Otherwise, they should actually check every time if the content they have is actually current as we do not send any long time caching headers. But some people like to break RFCs in favour of “performance”.

-Michael

> 
> 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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>> 
>>>> 
>>>>   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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>> 
>>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>>> 
>>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>>> 
>>>> Unsubscribe <https://www.ipfire.org/unsubscribe>

Re: IPFire 2.29 - Core Update 183 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 3715 bytes --]

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 we discussed in the last Video Call meeting.

Regards,
Adolf.

On 23/01/2024 15:10, Michael Tremer wrote:
> 
> 
>> On 23 Jan 2024, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> 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 and is much more eye catching.
>>>>
>>>> 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 underscore 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 most 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 the full new version but the other is still showing mostly the old version with just the tux icon changed.
>>>
>> I had to go into firefox settings and tell it to clear the cached web content. Then the IPFire WUI is now fully updated. Sorry for the noise.
> 
> Ah I got you now…
> 
> I was wondering what we can do about this… Browsers will definitely cache 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 definitely will fetch it again. Otherwise, they should actually check every time if the content they have is actually current as we do not send any long time caching headers. But some people like to break RFCs in favour of “performance”.
> 
> -Michael
> 
>>
>> 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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>>>
>>>>>
>>>>>    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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>>>
>>>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>>>>
>>>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>>>>
>>>>> Unsubscribe <https://www.ipfire.org/unsubscribe>
> 
> 

Re: IPFire 2.29 - Core Update 183 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 4073 bytes --]

Thank you for the reminder… I will add that.

I am currently quite buried in a lot of things that I am trying to handle simultaneously. So, please, if things don’t look right, let me know :)

-Michael

> On 23 Jan 2024, at 14:19, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 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 we discussed in the last Video Call meeting.
> 
> Regards,
> Adolf.
> 
> On 23/01/2024 15:10, Michael Tremer wrote:
>>> On 23 Jan 2024, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> 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 and is much more eye catching.
>>>>> 
>>>>> 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 underscore 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 most 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 the full new version but the other is still showing mostly the old version with just the tux icon changed.
>>>> 
>>> I had to go into firefox settings and tell it to clear the cached web content. Then the IPFire WUI is now fully updated. Sorry for the noise.
>> Ah I got you now…
>> I was wondering what we can do about this… Browsers will definitely cache 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 definitely will fetch it again. Otherwise, they should actually check every time if the content they have is actually current as we do not send any long time caching headers. But some people like to break RFCs in favour of “performance”.
>> -Michael
>>> 
>>> 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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>>>> 
>>>>>> 
>>>>>>   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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>>>> 
>>>>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>>>>> 
>>>>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>>>>> 
>>>>>> Unsubscribe <https://www.ipfire.org/unsubscribe>

Re: IPFire 2.29 - Core Update 183 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 5040 bytes --]

Hi All,

Have been exercising CU183 Testing. Everything has gone fine.

I tested out my existing OpenVPN RW and N2N connections and they worked 
fine.

Created new RW and N2N connections. The RW worked without any problems.

The N2N connection worked but the client end download icon and status 
area are not working. This is nothing to do with CU183 Testing. This 
comes from the fix I did for bug 11048 and therefore has been present 
since CU181.

I have created a new bug entry for this (13548) which I have assigned to 
myself.
I have looked at the code and have figured out what the problem is and 
will create a patch to test and fix it.

Everything else that I have tested on CU183 has worked without issues. I 
have not found any issue related to CU183 changes.

A very quiet update.

Regards,
Adolf.


On 23/01/2024 15:20, Michael Tremer wrote:
> Thank you for the reminder… I will add that.
> 
> I am currently quite buried in a lot of things that I am trying to handle simultaneously. So, please, if things don’t look right, let me know :)
> 
> -Michael
> 
>> On 23 Jan 2024, at 14:19, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> 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 we discussed in the last Video Call meeting.
>>
>> Regards,
>> Adolf.
>>
>> On 23/01/2024 15:10, Michael Tremer wrote:
>>>> On 23 Jan 2024, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> 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 and is much more eye catching.
>>>>>>
>>>>>> 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 underscore 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 most 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 the full new version but the other is still showing mostly the old version with just the tux icon changed.
>>>>>
>>>> I had to go into firefox settings and tell it to clear the cached web content. Then the IPFire WUI is now fully updated. Sorry for the noise.
>>> Ah I got you now…
>>> I was wondering what we can do about this… Browsers will definitely cache 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 definitely will fetch it again. Otherwise, they should actually check every time if the content they have is actually current as we do not send any long time caching headers. But some people like to break RFCs in favour of “performance”.
>>> -Michael
>>>>
>>>> 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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>>>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>>>>>
>>>>>>>
>>>>>>>    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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>>>>>>>
>>>>>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>>>>>>
>>>>>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>>>>>>
>>>>>>> Unsubscribe <https://www.ipfire.org/unsubscribe>
> 

-- 
Sent from my laptop

Re: IPFire 2.29 - Core Update 183 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]

Hello,

> On 23 Jan 2024, at 12:11, Adolf Belka <adolf.belka(a)ipfire.org> 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.

Thank you for the feedback.

I actually spent quite a lot of time on these because those emails should look decent enough to get people onto the website. There is now actually two versions of CSS that we are shipping: One in light and one in dark mode.

I have however seen email clients that still don’t show those emails anywhere near what they are supposed to look like.

> Now the email notification looks the same on my desktop and my mobile and is much more eye catching.

Very good!

> 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 underscore 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.

I don’t quite understand. Are you expecting the header to be a link?

> 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.

Looking forward to hearing all the things we broke :)

-Michael

> 
> 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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>  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 an update of the design of the web user interface, a fresh kernel based on Linux 6.6, a lot of package updates and improvements and bug fixes throughout the entire system.
>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-183-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>> Unsubscribe <https://www.ipfire.org/unsubscribe>