Qt 6.6 status:
* Qt 6.6.0 beta3 released
* Qt 6.6.0 Beta4 preparations started. Target is to release Qt 6.6.0 beta4
at week 36.
* API Change review is still ongoing, see
https://bugreports.qt.io/browse/QTBUG-114214
* Updating 3rd party components is also ongoing, see
https://bug
Hello,
> +1 in general.
> However, gerrit users should be individual contributors rather than a team
> user that is shared by multiple people, and the responsible person needs to
> have a gerrit user account.
> So, if nobody objects within a few days, please create a QTQAINFRA task
> in JIRA wit
On Tuesday, 29 August 2023 03:26:08 PDT Volker Hilsheimer via Development
wrote:
> However, gerrit users should be individual contributors rather than a team
> user that is shared by multiple people, and the responsible person needs to
> have a gerrit user account.
That also applies to Copyright:
Hi!
The reason for rounding is that the subpixel position of the glyphs is baked
into the cached rendering of the glyph itself (so horizontal position x.5 would
be a different cached object than x.0, but they should both be rendered at
pixel x). It's a bit complex because the projected position
Hi,
I've been reviewing some of the Qt 6.6 API diff's lately, focusing on the API
documentation. And frankly speaking, there was (and still is) a lot to improve
...
In particular, if you are the original *reviewer of any public API change*,
please check:
* Is there documentation for *new publ
+1 in general.
However, gerrit users should be individual contributors rather than a team user
that is shared by multiple people, and the responsible person needs to have a
gerrit user account.
So, if nobody objects within a few days, please create a QTQAINFRA task in JIRA
with the necessary d
