From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.29 - Core Update 183 is available for testing
Date: Tue, 23 Jan 2024 14:07:38 +0000 [thread overview]
Message-ID: <A7A9682D-8113-411D-ACFE-D2F025B50277@ipfire.org> (raw)
In-Reply-To: <f9960b3d-b71b-4c25-be01-363bb57e6222@ipfire.org>
[-- 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>
prev parent reply other threads:[~2024-01-23 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170600731740.2103927.2691414435820913096.ipfire@ipfire.org>
2024-01-23 12:11 ` Adolf Belka
2024-01-23 13:20 ` Adolf Belka
2024-01-23 13:23 ` Adolf Belka
2024-01-23 14:10 ` Michael Tremer
2024-01-23 14:19 ` Adolf Belka
2024-01-23 14:20 ` Michael Tremer
2024-01-30 13:25 ` Adolf Belka
2024-01-23 14:07 ` 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=A7A9682D-8113-411D-ACFE-D2F025B50277@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.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