Re: Dropping Qt5 CI Support at the End of September 2025 - Sunsetting Qt 5

On 28/12/25 08:50, Albert Astals Cid wrote:
> El dissabte, 27 de desembre del 2025, a les 22:18:55 (Hora estàndard d’Europa
> central), Christoph Cullmann va escriure:
>> Hi,
>>
>> given we soon start 2026: Would it be time to sunset the Qt 5 stuff on
>> invent?
> In July we said it would be in September and there was not a huge uproar, so
> doing it in January 2026 (6 months later than what we said) should be more
> than enough.
>
> Doing it == "closing the remaining Qt5 CI" and that's it i guess?
>
> Or is there something else that needs to be removed?
>
> Cheers,
>    Albert
>
>> (beside the Qt patch collection)
>>
>> Greetings
>> Christoph
>>
>> On Thursday, July 3rd, 2025 at 21:33, Albert Astals Cid<[email protected]> 
> wrote:
>>> El dijous, 3 de juliol del 2025, a les 16:52:49 (Hora d’estiu d’Europa
>>>
>>> central), Neal Gompa va escriure:
>>>> On Sun, Jun 22, 2025 at 6:31 PM Albert Astals [email protected] wrote:
>>>>> Hi everyone,
>>>>>
>>>>>
>>>>> While this has been discussed in various forums, it has not yet been
>>>>> the
>>>>> main focus of any conversation.
>>>>>
>>>>>
>>>>> We are planning to drop support for Qt5 CI on invent.kde.org at the
>>>>> end of
>>>>> September 2025.
>>>>>
>>>>>
>>>>> If you are still using Qt5 you have 3 months to move to Qt6 or you can
>>>>> try
>>>>> to convince the powers that you need more time with a really good
>>>>> reason.
>>>>> Does this mean we've effectively stopped working on the Qt5 patch
>>>>> collection and we're going to EOL the 24.08-qt5 runtime for Flatpak in
>>>>> September?
>>> We do not have CI for the patch collection.
>>>
>>>
>>> I will [try to[ continue doing the rebases for the patch-collection until
>>> Qt 5.15.19 gets released next year.
>>>
>>>
>>> Best Regards,
>>> Albert

What are others thoughts on archiving any project that has not been 
ported to Qt6 or active Qt6 Merge Request / Branch?

Unarchiving projects is always possible, and the source code remains 
available for people to check out read-only and work on. If they start 
working on a port, they can request the project be unarchived.

Regards,

Justin