Hi,
I would like to get input on this amendment to QUIP 16:
https://codereview.qt-project.org/c/meta/quips/+/608523
It addresses exceptions to the cherry-picking policy for refactorings.
Cheers.
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/develo
Hi,
I'd like to request an exception for
https://codereview.qt-project.org/c/qt/qtdeclarative/+/554020, which was
approved before the freeze but hasn't successfully integrated yet.
Thanks.
> -Original Message-
> From: Development On Behalf Of
> Jani Heikkinen via Development
> Sent: M
+1
Disclaimer: I work in the same team.
> -Original Message-
> From: Development On Behalf Of
> Shawn Rutledge via Development
> Sent: Saturday, 30 November 2024 5:30 AM
> To: Qt Development
> Subject: [Development] Nominating Oliver Eftevaag as maintainer of Qt Quick
> Dialogs
>
> I'm
Hi,
Once I've gotten into a specific filter (i.e.
https://testresults.qt.io/grafana/d/de08wetl3yq68f/Test%20failure%20heatmaps?var-integration=149569&var-table_name=blacklisted_tests&var-project=qt%2Fqtdeclarative&var-config=macos-13-arm64-developer-build-tests),
is there a way to see a list of
hand, asking users to
refer to archived versions of the docs is not unreasonable, especially for such
old versions. I'd still argue that there's more benefit to the user having that
added convenience, though.
From: Development on behalf of EXT Mi
I'm confused... \since does show up in the generated documentation:
- https://doc.qt.io/qt-6/qml-qtquick-item.html#focusPolicy-prop
- https://doc.qt.io/qt-6/qml-qtquick-listview.html#displayMarginBeginning-prop
For what it's worth, my vote goes for keeping that information too. As a user
it's mu
> -Original Message-
> From: Development On Behalf Of
> Sami Varanka via Development
> Sent: Tuesday, May 14, 2024 6:42 PM
> To: development@qt-project.org
> Subject: [Development] QtGraphs final API review
>
> Hi everybody!
> QtGraphs will be out of TP in 6.8, and now we need to do the f
+1
> -Original Message-
> From: Development On Behalf Of
> Paul Tvete via Development
> Sent: Tuesday, January 30, 2024 8:11 PM
> To: Qt development mailing list
> Subject: [Development] Nominating Matthias Rauter for approval status
>
> Hi,
>
> I would like to nominate Matthias Rauter
> -Original Message-
> From: Kai Uwe Broulik
> Sent: Thursday, August 24, 2023 7:38 PM
> To: EXT Mitch Curtis ; development@qt-project.org
> Subject: Re: [Development] QtQuick Dialogs Widgets fallback
>
> Hi,
> > Which style are you referring to here?
>
> The default QML one, none Fusion
> -Original Message-
> From: Development On Behalf Of
> Kai Uwe Broulik
> Sent: Wednesday, August 23, 2023 4:17 AM
> To: development@qt-project.org
> Subject: [Development] QtQuick Dialogs Widgets fallback
>
> Hi everyone,
Hi Kai,
> we found that the Qt Quick Dialogs (MessageDialog and
> -Original Message-
> From: Arno Rehn
> Sent: Wednesday, July 12, 2023 4:13 PM
> To: EXT Mitch Curtis ; Qt development mailing list
>
> Subject: Re: [Development] Behavior-changing bugfixes in patch-level releases
>
> Hi Mitch,
>
> On 12.07.2023 09:52, EXT Mitch Curtis wrote:
> >> Cont
Hi Arno,
> -Original Message-
> From: Development On Behalf Of
> Arno Rehn
> Sent: Wednesday, July 12, 2023 3:01 PM
> To: Qt development mailing list
> Subject: [Development] Behavior-changing bugfixes in patch-level releases
>
> Hey everyone,
>
> what is the policy for adding behavior
+1
> -Original Message-
> From: Development On Behalf Of
> Jan-Arve Sæther via Development
> Sent: Wednesday, June 21, 2023 2:56 AM
> To: Jack Simcox via Development
> Subject: [Development] Nominating Santhosh Kumar Selvaraj for approver
> rights
>
> Hello all,
>
> I would like to nom
+1
> -Original Message-
> From: Development On Behalf Of
> Marc Mutz via Development
> Sent: Thursday, May 4, 2023 6:10 PM
> To: development@qt-project.org
> Subject: [Development] Nominating Edward Welbourne as QLocale /
> date/time maintainer
>
> Hi,
>
> I'd like to nominate Eddy as t
The source code text seems to be missing - the line numbers seem to be correct
by I don't see any code. Inspecting the HTML shows that there is no text there,
so it's not just a CSS issue.
> -Original Message-
> From: Development On Behalf Of
> Andrey Leman via Development
> Sent: Monda
> -Original Message-
> From: Development On Behalf Of
> Eike Ziller via Development
> Sent: Monday, 12 December 2022 5:20 PM
> To: Владимир Белявский
> Cc: development@qt-project.org
> Subject: Re: [Development] Using QtCreator for Qt development
>
>
>
> > Am 10/12/2022 um 13:57 schrie
Some directories have been renamed in this patch that will hopefully be merged
soon:
https://codereview.qt-project.org/c/qt/qtdeclarative/+/444028
You may have to rebase open patches.
It may also be necessary to wipe your qtdeclarative build and rebuild.
No user-facing API/libraries should be
> -Original Message-
> From: Edward Welbourne
> Sent: Friday, 14 October 2022 4:56 PM
> To: Milian Wolff ; EXT Mitch Curtis
> Cc: Development@qt-project.org
> Subject: Re: [Development] Duplicated test data tags
[...]
> Mitch Curtis (14 October 2022 03:40) replied:
> > QTest::failOnWarnin
> -Original Message-
> From: Development On Behalf Of
> Milian Wolff
> Sent: Friday, 14 October 2022 3:00 AM
> To: Development@qt-project.org
> Subject: Re: [Development] Duplicated test data tags
>
[...]
> I have many times accidentally written bogus code that duplicated the tags.
> Get
> -Original Message-
> From: Development On Behalf Of
> Volker Hilsheimer via Development
> Sent: Monday, 10 October 2022 5:55 PM
> To: development@qt-project.org
> Subject: [Development] Using '#pragma once' instead of include guards?
>
> Hi,
>
>
> We are using `#pragma once` in a numb
20 matches
Mail list logo
