Hi!
We have branched '6.3.2' from '6.3' now. So from now on all changes targeted to
Qt 6.3.2 release must have 'Pick-to: 6.3.2'
As usual staging in '6.3.2' will be restricted to release team only.
br,
Jani
___
Development mailing list
Development@qt-p
On Thursday, 11 August 2022 03:21:03 PDT Shawn Rutledge wrote:
> As for POWER I do occasionally test on Debian on the old G5 machine, but not
> very often. Builds take a long time, the GPU is not good for Qt Quick, and
> not all modules build and run, but at least qtbase is usually ok.
That's abo
On Thursday, 11 August 2022 02:59:49 PDT JiDe Zhang wrote:
> Hi, Will we accept add the other architectures? A example is Loongarch(Its
> from China). Will we expectation it is fully public?
We can, so long as the complexity of its maintenance has a proportional offer
of someone maintaining it.
We are happy to announce the release of Qt Creator 8.0.1!
https://www.qt.io/blog/qt-creator-8.0.1-released-1
___
Announce mailing list
annou...@qt-project.org
https://lists.qt-project.org/listinfo/announce
___
I would like to get more familiar with RISC-V when I’ve got hardware for it,
and might consider volunteering then. (I don’t have any Qt-capable hardware
yet, only the U540 microcontroller; but better stuff is starting to become
available actually.)
As for POWER I do occasionally test on Debian
Hi, Will we accept add the other architectures? A example is Loongarch(Its from
China). Will we expectation it is fully public?
From: Development on behalf of Alex
Blasche
Sent: Thursday, August 11, 2022 16:56
To: development@qt-project.org
Subject: Re: [Devel
> -Original Message-
> From: Development On Behalf Of
> Thiago Macieira
> Like I said in my email, we don't have the resources or knowledge to fix
> architectural-specific issues in those platforms, much less apply performance
> improvements. But we will accept patches in case we break any
