Nicolas Fella wrote:
> The fact that KDE does not use Qt6 yet has rather little to do with the
> quality of Qt6.
Where have I claimed that it does? I sense a strawman…
My point is that it takes time for KDE and other downstreams to adopt a new
major release of Qt, no matter the reason why it doe
Am 07.09.22 um 08:45 schrieb Kevin Kofler via Development:
Alex Blasche wrote:
2.) An alternative might be to make this change in one go for Qt 7. We
would keep Qt 6.x on the status quo but start adding compatible
replacement APi with an absolute change at 7.0 (ifdefs or typedefs come to
mind).
Ilya Fedin wrote:
> I believe the fact KDE is not ported to Qt 6 yet is more question of
> bureaucracy coordination of a lot of people in different KDE projects.
> That is, deciding that they want to port to Qt 6 takes time, then every
> project maintainer should do the port and it seems they want
On Tuesday, 6 September 2022 23:45:45 PDT Kevin Kofler via Development wrote:
> It scares me that a Qt 7 is already being planned or discussed at all,
We had "### Qt 7" remarks in Qt 6.0.0.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineer
On Mon, Sep 05, 2022 at 05:15:45PM +, Marc Mutz wrote:
> [...]
>We have the tools (QT_REMOVED_SINCE + Ivan's work on
>-disable-deprecated-until) to have a user-configurable, rolling BC window
>now We should use these tools to avoid accumulating too much technical
>[...]
>Th
> On 7 Sep 2022, at 08:36, Alex Blasche wrote:
>
> Hi Volker,
>
>>
>> From: Development on behalf of Volker
>> Hilsheimer
>
>> I agree that it would be great if users of Qt could flip on aggressive
>> compile options to get warnings about narrowing-c
Hi all,
we have released Qt 5.15.6 opensource today:
* release note:
https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.6/release-note.md
* source packages in download.qt.io:
* https://download.qt.io/official_releases/qt/5.15/5.15.6/
*
https://download.qt.io/o
Congratulations David and Eskil, the maintainers page is now updated.
Volker
> On 24 Aug 2022, at 10:36, Volker Hilsheimer wrote:
>
> Hi,
>
>
> Giulio has informed me that he won’t be able to continue as the maintainer of
> Qt Wayland. Thanks Giulio for your contribution!
>
> Qt Wayland i
On Wed, 07 Sep 2022 08:45:45 +0200
Kevin Kofler via Development wrote:
> It scares me that a Qt 7 is already being planned or discussed at
> all, considering that your major consumers such as KDE Plasma are not
> even ported to Qt 6 yet! (Note that I am talking about *consumers*
> here, not only
> On 7 Sep 2022, at 09:00, Andreas Aardal Hanssen wrote:
>
> On Wed, Sep 7, 2022, at 08:45, Kevin Kofler via Development wrote:
>> Alex Blasche wrote:
>>> 2.) An alternative might be to make this change in one go for Qt 7. We
>>> would keep Qt 6.x on the status quo but start adding compatible
>>>
On Wed, Sep 7, 2022, at 08:45, Kevin Kofler via Development wrote:
> Alex Blasche wrote:
> > 2.) An alternative might be to make this change in one go for Qt 7. We
> > would keep Qt 6.x on the status quo but start adding compatible
> > replacement APi with an absolute change at 7.0 (ifdefs or typed
11 matches
Mail list logo
