Qt 6.6 status
* Qt 6.6 Beta3 preparations are ongoing
* Content is not frozen yet but target is to freeze the content later
this week
* The latest estimate for beta3 release is Tue 22nd August
* API Change review is still ongoing, see
Hey!
Yeah, I think reviewer: is sometimes a bit misleading, so +1 for changing to
commentby:
Though, in that case we might want to also, for transparency, add
"-owner:". It's only natural
to reply on your own changes of course :)
Mårten
From:
Hi,
Emails in which we nominate contributors for Approver status usually have two
queries: the list of changes owned [1], and the list of changes that the
nominee reviewed [2].
[1] https://codereview.qt-project.org/q/owner:volker.hilsheimer%2540qt.io
[2]
+1
Disclaimer: Kwanghyo reports (indirectly) to me.
Volker
On 14 Aug 2023, at 08:54, Tomi Korpipää via Development
wrote:
Hi,
I'd like to nominate Kwanghyo Park for approver status. He is the main
developer for Surface3D graphs for the QtGraphs module, and has been
contributing to
+1
Disclaimer: He did never beat me in table kicker (perhaps out of kindness)
From: Development on behalf of Marcus
Tillmanns via Development
Sent: Tuesday, August 8, 2023 15:25
To: development@qt-project.org
Subject: [Development] Nominating Artem
Hi all!
There are still many reviews open; please help to review and fix findings to
complete the review
Open ones
qtbase
* https://codereview.qt-project.org/c/qt/qtbase/+/481745 Widgets: API
comparison from v6.5.0 to 6.6 in qtbase
* https://codereview.qt-project.org/c/qt/qtbase/+/481746
Hi all,
First beta releases from Qt 6.6 are out and it is time to start keeping
translatable strings as it is. The official string freeze for Qt 6.6 will be in
effect Tue 22nd of August 2023.
br,
Jani Heikkinen
Release Manager
--
Development mailing list
Development@qt-project.org
Hi Songziming,
Thanks for sharing.
The file system model is stack allocated after the application and the qml
engine. So it’s deleted before them, when main() goes out of scope. The QML
engine shutdown still finds a (stale) QObject and tries to disconnect signals
from it, hence the warnings.
Hi,
I create the custom model object in main function on stack. Model is
instantiated after QQmlApplicationEngine, and is deleted before
QQmlApplicationEngine. During custom model’s destruction,
QItemSelectionModelPrivate::initModel(NULL) is called.
I also tested QFileSystemModel, which also
