On Tuesday, 6 February 2024 06:57:34 CET Jani Heikkinen via Development wrote:
> > How about instead we drop at an LTS+2 release? The next one is actually
> > 6.7.
> We can't switch this in 6.7 at this point anymore; we don't have packages
> for MSVC2022 at the moment and doing this (adding new
>
> How about instead we drop at an LTS+2 release? The next one is actually 6.7.
>
We can't switch this in 6.7 at this point anymore; we don't have packages for
MSVC2022 at the moment and doing this (adding new packages + removing ones)
change this late of process is too risky
br,
Jani
--
On Monday, 5 February 2024 01:36:39 PST Marc Mutz via Development wrote:
> I've always understood it such that we as Qt must preserve the property
> that the hash for equal elements is equal within _one_ run of _one_
> process. This means you can use the hash in I/O in any way. That's why
> we
On Monday, 5 February 2024 01:39:47 PST Marc Mutz via Development wrote:
> I think we don't drop supported compilers, except in LTS+1 releases (6.9
> being the next).
I would advise you drop it before the LTS, so you don't have to keep
supporting it for however long your LTS cycle is.
How about
This is DONE
From: Development on behalf of CI
Maintenance Break via Development
Sent: Monday, February 5, 2024 6:03 AM
To: development@qt-project.org
Subject: Re: [Development] Monthly CI maintenance break - February (Mon, Feb
5th 2024)
This starts NOW
From what I see, the open questions from the thread in May are still:
- (paraphrasing Ville) which C++ 20 features are worth breaking (primarily
embedded) users who want new Qt version but don’t yet have the compilers that
can give them these facilities?
Hi,
For Qt 6.8 we continue to work on Phase 1 item
https://bugreports.qt.io/browse/QTBUG-109360. In other words we will not
mandate C++20 compilers in Qt 6.8 yet. An LTS release is not the right for such
a breaking change anyway. The possible releases for such a drastic change are
6.9 or
On 03.02.24 18:13, Thiago Macieira wrote:
> On Wednesday, 21 December 2022 09:51:52 PST Vladimir Minenko via Development
> wrote:
>> We got four user stories on Qt Bug Reports:
>>
>> 1. Use C++20 code with Qt - https://bugreports.qt.io/browse/QTBUG-109360
>> 2. C++20 is required for the
On Saturday, 3 February 2024 18:08:25 CET Thiago Macieira wrote:
> The compiler is pretty buggy and has several, unfixed conformance issues
> with C++.
>
> One year ago I asked on the interest mailing list about using a non-latest
> MSVC:
>
I think we don't drop supported compilers, except in LTS+1 releases (6.9
being the next).
On 03.02.24 18:08, Thiago Macieira wrote:
> The compiler is pretty buggy and has several, unfixed conformance issues with
> C++.
>
> One year ago I asked on the interest mailing list about using a
Hi,
I've always understood it such that we as Qt must preserve the property
that the hash for equal elements is equal within _one_ run of _one_
process. This means you can use the hash in I/O in any way. That's why
we have qt_hash, which you _can_ (and do) use in I/O (but is private
API,
11 matches
Mail list logo
