public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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:20:14 +0000	[thread overview]
Message-ID: <CD498A1B-C872-4CB9-A305-C47F6AF52D98@ipfire.org> (raw)
In-Reply-To: <0e71b0e3-ae87-42fe-ab78-67040966526b@ipfire.org>

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


  reply	other threads:[~2024-01-23 14:20 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 [this message]
2024-01-30 13:25             ` Adolf Belka
2024-01-23 14:07   ` Michael Tremer

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=CD498A1B-C872-4CB9-A305-C47F6AF52D98@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