Re: [Development] Nominating Jøger Hansegård for approver rights

+1 --Liang From: Development on behalf of Tor Arne Vestbø via Development Sent: Thursday, March 14, 2024 10:06 AM To: development Subject: [Development] Nominating Jøger Hansegård for approver rights Hi, I would like to nominate Jøger Hansegård for approver

Re: [Development] who can fix this bug?

Forgot one thing. If I didn't remember wrong, Nvidia only releases 340.108 driver for 5.15 and earlier kernel, and there are some community work to modify it to work with later versions of kernel. I assume we can't support those cases under this situation. --Liang

Re: [Development] who can fix this bug?

Please report it in jira, https://bugreports.qt.io/ , if you think it's a real Qt bug. Please provide a complete, minimal example with enough information about how to reproduce your issue according to https://wiki.qt.io/ReportingBugsInQt . I have a machine with GT218 [GeForce 210] with 340.108

Re: [Development] Nominating Axel Spoerl as approver

+1 From: Development on behalf of Volker Hilsheimer via Development Sent: Monday, December 5, 2022 10:57 AM To: development@qt-project.org Subject: [Development] Nominating Axel Spoerl as approver Hi, I’d like to nominate Axel Spoerl as an approver for the

Re: [Development] QFreedesktopApplication

About the gapplication, I assume it's sth about "man gapplication", see also http://manpages.ubuntu.com/manpages/impish/man1/gapplication.1.html . - SYNOPSIS gapplication help [COMMAND] gapplication version gapplication list-apps gapplication launch APPID

Re: [Development] QTouchDevice in Qt 6 ?

https://www.qt.io/blog/input-events-in-qt-6 Hope it helps. —Liang > On 8 Oct 2021, at 16:02, Martin Koller wrote: > > Hi, > > seems QTouchDevice in Qt6 is gone, but I don't see any mentioning of it in > https://doc.qt.io/qt-6/gui-changes-qt6.html > > Any hint to some information regarding

Re: [Development] Patch workflow in qt5 supermodule (provisioning)

Hi, I think we haven’t move to “cherry-pick” mode, (dev first, then cherry-pick to other branches) yet. So still like before, do it in the lowest needed branch of 5.14/5.15/dev, then cherry-pick to 5.12 if needed. —Liang > On 20 Feb 2020, at 13:03, Konstantin Tokarev wrote: > > Hello, > >

Re: [Development] Gerrit comment "Continuous Integration: Running"

Please help to create ticket for Project:Coin(COIN) in jira, thanks. —Liang > On 23 Feb 2020, at 15:19, Konstantin Tokarev wrote: > > Weird thing is happening with Coin or Gerrit - all integrating changes got > "Continuous Integration: Running" > comment. Restaging leads to "Continuous

Re: [Development] Proposal: Eliminate soft branching phase from release process

We are using soft branching phase for two categories: 1. feature frozen or minor branch, like dev to 5.14, many new changes are targeting 5.14 release, but happened in dev branch, and not easy to be integrated or verified soon. the one week soft branching phase could help bit here. 2. patch

Re: [Development] [Gerrit-admin] Cherry-pick mode for 5.12

If you found anything else is missing, please let me know, thanks. I think 5.12 could be full cherry-pick mode now. To provisioning change owners, please do in 5.13 branch first and then cherry-pick to 5.12 if needed. —Liang > On 3 Sep 2019, at 07:53, Liang Qi wrote: > > It happened so

Re: [Development] Merge and Integration status report - 2019.09.06

During the weekend, qt5 dev and 5.15 got integrated. 5.12.5->5.12 merges are done including qt5 and all submodules. 5.12->5.13 merges are still ongoing. —Liang > On 6 Sep 2019, at 14:19, Liang Qi wrote: > > Integrations > > * qt5 5.12 and 5.13 are healthy, the

[Development] Merge and Integration status report - 2019.09.06

Integrations * qt5 5.12 and 5.13 are healthy, the last submodule update integrated at 2 days ago * qt5 5.14: * ongoing: https://codereview.qt-project.org/c/qt/qt5/+/272221 , hope it could finish a bit later tonight * previous integrated submodule update is 8 days ago. * qt5 dev:

Re: [Development] [Gerrit-admin] Cherry-pick mode for 5.12

It happened so fast this time. But 5.12.5 was branched out before this cherry-pick mode change on 5.12 branch, I plan to do the 5.12.5->5.12->5.13 merges after 5.12.5 is out. Is it OK? —Liang > On 2 Sep 2019, at 15:13, Kari Oikarinen wrote: > > > > On 2.9.2019 15.23, Lars Knoll wrote: >>

Re: [Development] [Android] Raising minimum supported Android NDK version to r19

On Thu, 1 Aug 2019 at 18:58, Alexey Rochev wrote: > > Hello, > I'm currently investigating several problems with building Qt with > recent (r19 and r20) NDK versions. In NDK r19 Google added a new > toolchain, and we need to use it for some features to work (e.g. > LTCG). It would greatly

Re: [Development] qtlottie build broken: "Missing CMake tests. Either create tests in tests/auto/cmake"

https://codereview.qt-project.org/c/qt/qtlottie/+/268295 http://bugreports.qt.io/browse/QTBUG-77130 Liang > On 22 Jul 2019, at 21:22, Simon Hausmann wrote: > > I think I fixed that last week. What’s your sha1? > > There is not C++ application linkage for the module in question so cmake app >

[Development] Merge and Integration status report - 2019.06.28

Integrations * qt5 5.12: submodule updated two days ago. The only issue is qtvirtualkeyboard was decoupled from qt5, see https://bugreports.qt.io/browse/QTBUG-76371 , need to wait COIN production update * qt5 5.13: submodule updated three days ago. The only issue is

Re: [Development] Gerrit is back

Gerrit admins, Thanks for the upgrade. I like MERGE_LIST feature very much, https://codereview.qt-project.org/c/qt/qtbase/+/262306/5..6//MERGE_LIST But I have one question, when I search a sha1 of one commit, the old gerrit only shows the change itself, the new gerrit will also show all

[Development] Merge and Integration status report - 2019.05.09

Integrations and Provisionings * qt5 5.9, 5.12, 5.13, 5.13.0 and dev are healthy, after https://testresults.qt.io/coin/integration/qt/qt5/tasks/1557406940 , qt5 dev finally got integrated after about 4 weeks. Merges Please check

Re: [Development] Be careful with duplicate Change-Ids in multiple branches in gerrit

> On 7 May 2019, at 22:13, Oswald Buddenhagen wrote: > > On Tue, May 07, 2019 at 01:52:48PM +0000, Liang Qi wrote: >> This is a very common issue when I do the integraton work in qt5. >> >> For example, currently we have 5.12->5.13->dev merge order, and the

[Development] Be careful with duplicate Change-Ids in multiple branches in gerrit

This is a very common issue when I do the integraton work in qt5. For example, currently we have 5.12->5.13->dev merge order, and the last round 5.13->5.13.0 today. One change(changeA) had been integrated in 5.13, and another change(changeB) with duplicate Change-Id was pushed to 5.13.0 branch

[Development] Merge and Integration status report - 2019.03.15

Integrations and Provisionings * qt5 5.12, 5.13 and dev are healthy, finally after https://testresults.qt.io/coin/integration/qt/qt5/tasks/1552656661 Merges Please check

[Development] Merge and Integration status report - 2019.03.08

Integrations and Provisionings * qt5 5.12 and 5.13 are healthy * qt5 dev: submodule update on March 4 excluded qtbase, the previous one with qtbase in about one month ago on Feb. 7. Currently only known blocker is https://bugreports.qt.io/browse/QTBUG-74126 , Parse error at

Re: [Development] Coin maintenance update

Do you have any records for the qt5 integration history? How many minutes is average? Or what is next step in your plan? For example, let COIN to decide when to pick up an approved qt5 submodule update? I think there is no hope to stage any qt5 changes in work hour, perhaps same in midnight.

[Development] Merge and Integration status report - 2019.02.01

Merges * Submodules and qt5 are fine. Integrations and Provisionings * qt5 5.12 are healthy * Trying to have a few changes from Ryan, about docker based network test server for Windows, see

Re: [Development] Archiving is working

Looks like the index was also regenerated for October 2016, [Development] Coin news - Jedrzej Nowacki Tue Oct 25 10:22:41 EEST 2016 Current link: https://lists.qt-project.org/pipermail/development/2016-October/055084.html It was:

Re: [Development] Nominating Sami Nurmenniemi for Approver status

+1 Thank Sami for lots of help on QEMU build and etc. —Liang > On 25 Jan 2019, at 09:06, Kari Oikarinen wrote: > > Hi! > > I'd like to nominate Sami Nurmenniemi for Approver. He has already been > working > in The Qt Company in the same team as I am for a good while. > > Sami has worked on

Re: [Development] Proposal: New branch model

Lots of talks happened already on this thread. I would like to think old model as "merge" model VS new model as "cherry-pick" model. In the old "merge" model, normally we will drop a branch out to cherry-pick mode after having more than 3 branches and try to have 2 branches(change LTS branch to

[Development] Merge and Integration status report - 2019.01.22

First issue on 2019! Generally, CI/COIN was in a very good mood after the new year update. Then we met https://bugreports.qt.io/browse/QTBUG-73116 , tst_QString::localeAwareCompare fails (dev) and a few other issues. Now it looks like most of them got fixed already. Merges * Submodules

Re: [Development] [Releasing] HEADS-UP: Branching from '5.12' to '5.12.1' started

qtbase and qttools final down merges are done, https://codereview.qt-project.org/#/c/249324/ https://codereview.qt-project.org/#/c/249362/ And also qt5 5.12->5.12.1 final down merge is done, https://codereview.qt-project.org/#/c/249362/ —Liang > On 8 Jan 2019, at 08:32, Jani Heikkinen wrote:

[Development] Merge and Integration status report - 2018.12.22

Merges * 5.11.3->5.11 merges are done, including qt5, so 5.11.3 branch could be nuked. * 5.12.0->5.12, qt5 one https://codereview.qt-project.org/#/c/248857/ is ongoing * 5.11->5.12, still missing qtwebengine and qt5 * 5.12->dev, need to be done after new year Integrations * 5.12 is healthy *

[Development] Merge and Integration status report - 2018.11.15

Integrations * qt5 5.9/5.11/5.11.3/5.12/5.12.0 integrations are healthy * qt5 dev integrations: qtbase didn't update for about two weeks * https://bugreports.qt.io/browse/QTBUG-71804 'GLsizeiptr' and 'GLintptr': redefinition; different basic types, qtwebengine team is working on it

Re: [Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

> On 11 Nov 2018, at 22:25, Thiago Macieira wrote: > > On Sunday, 11 November 2018 11:44:12 PST Liang Qi wrote: >> I staged a few times from Friday night to now, got some changes integrated >> and found some issues in them. Do you have some changes need to stage? >

Re: [Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

> On 11 Nov 2018, at 20:01, Thiago Macieira wrote: > > On Thursday, 8 November 2018 04:00:08 PST Oswald Buddenhagen wrote: >> On Thu, Nov 08, 2018 at 08:29:47AM +, Liang Qi wrote: >>> I don't know how to use [Grafana] to show the statistic of qtbase 5.12

Re: [Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

> On 8 Nov 2018, at 13:00, Oswald Buddenhagen wrote: > > On Thu, Nov 08, 2018 at 08:29:47AM +0000, Liang Qi wrote: >> I don't know how to use [Grafana] to show the statistic of qtbase 5.12 >> integrations in coin. There are only 3 successful integrations >> yes

Re: [Development] The CI has been integrating for 38 hours

A CI/COIN reboot happened on 11am on Saturday, and sucked. Once more around 9am this morning(Oslo time). Let’s see. —Liang > On 4 Nov 2018, at 06:25, Thiago Macieira wrote: > > https://codereview.qt-project.org/244145 > Integration started Friday 16:45 CET. I guess everyone shortly left for

[Development] Merge and Integration status report - 2018.10.29

Integrations * qt5 5.9/5.11/5.12/dev integrations are healthy Merges * qtdeclarative 5.11->5.12 merge(10 days) is ongoing, https://codereview.qt-project.org/#/c/243050/ * qtbase 5.11->5.12 merge, need help, https://codereview.qt-project.org/#/c/243826/ * qtbase 5.12->dev merged on Saturday,

Re: [Development] Shutting down the CI right now!

of qemu64 instead of host-passthrough is in > effect. See if that helps. > > -Tony > > -----Original Message- > From: Liang Qi > Sent: perjantai 12. lokakuuta 2018 8.21 > To: Tony Sarajärvi > Cc: development@qt-project.org > Subject: Re: [Development] Shutting

Re: [Development] Shutting down the CI right now!

Thanks for the work, and sometimes in spare time. But there is no success for qt5 integrations and qtbase in any branch since the work from Wednesday night. See https://bugreports.qt.io/browse/QTQAINFRA-2273 , Angle building timeout (on Windows) So I suggest not to restage in above areas at

[Development] Merge and Integration status report - 2018.09.28

Integrations * qt5 5.9/5.11 integrations are healthy * qt5 5.12, one integration was done this morning, but qtbase was two days old. * * https://bugreports.qt.io/browse/QTBUG-70779 libqtgeoservices_mapboxgl.so link failure on android. Root cause was found, need help to find final solution. * qt5

[Development] Merge and Integration status report - 2018.09.05

Integrations * qt5 5.11/5.11.2/5.12 integrations are healthy, finally for 5.12 * qt5 dev, 5.12->dev merge + dev submodule update integration just started, let's see COIN is a bit slow recently, the difference between backend vm numbers and coin running numbers is a bit too much. Colleagues

Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )

Perhaps it's related with https://codereview.qt-project.org/#/c/235352/ . --Liang On Wed, 5 Sep 2018 at 09:20, Helio Chissini de Castro wrote: > Morning guys > > After compile 5.12 branch from yesterday morning, i got one KDE > application failing due a compiler error on a generated moc file.

Re: [Development] HEADS-UP: Branching from 'dev' to '5.12' completed

qt5 dev->5.12 is also done last night, https://codereview.qt-project.org/#/c/237349/ . Please remember to retarget your provisioning changes in qt5 if agreed for 5.12. — Liang > On 21 Aug 2018, at 11:04, Jani Heikkinen wrote: > > Branching from 'dev' to '5.12' is now complete and Qt 5.12

[Development] Merge and Integration status report - 2018.08.13

Integrations * qt5 5.11 integration is healthy, last one is yesterday, August 12 * qt5 dev, last one is August 11, excluding qtbase since August 8 * * http://bugreports.qt.io/browse/QTBUG-69891 tests/auto/quick/drawingmodes hanging Tor Arne is working on that. But if can't get fix soon,

Re: [Development] Upgrade the XCode running in the CI's macOS 10.11

For enabling test on 10.13, see https://codereview.qt-project.org/#/c/231978/ and a few other changes from Tony. Hope that will be done soon after summer vacation. -- Liang On Thu, 12 Jul 2018 at 06:13, Tor Arne Vestbø wrote: > > > On 11 Jul 2018, at 18:21, Thiago Macieira > wrote: > > > > On

Re: [Development] Raising the minimum Android NDK version

https://bugreports.qt.io/browse/QTQAINFRA-1681 https://codereview.qt-project.org/#/c/216306/ https://codereview.qt-project.org/#/c/229465/ People are working on that, hope will get update after summer vacations. -- Liang On Fri, 6 Jul 2018 at 03:54, Thiago Macieira wrote: > I've just been

[Development] Merge and Integration status report - 2018.07.04

Merges * qtbase 5.11->dev, https://codereview.qt-project.org/#/c/231959/ finally got merged after blocked about 3 weeks. A new round is ongoing, https://codereview.qt-project.org/#/c/233803/ Integrations * qt5 dev, last one is June 29, 4 days ago. A new one is at

Re: [Development] Urgent: increase timeout for tst_qcomplextext

On Tue, 3 Jul 2018 at 10:05, Lars Knoll wrote: > > On 3 Jul 2018, at 05:55, Thiago Macieira > wrote: > > > > On Saturday, 30 June 2018 10:09:11 PDT Lars Knoll wrote: > >> Hi Thiago, > >> > >> maybe https://codereview.qt-project.org/#/c/233693/ helps with this > case. > > > > It did help some.

[Development] Merge and Integration status report - 2018.07.01

Integrations * qt5 dev integration is healthy, last one is June 29 * qt5 5.11 integration is healthy finally again, last one is June 30 Merges * qtbase 5.11->dev is ongoing, https://codereview.qt-project.org/#/c/231959/ , which was blocked about 3 weeks, lots of changes from 5.11. I really

[Development] Merge and Integration status report

Integrations * qt5 dev integration is healthy, last one is yesterday * qt5 5.11 integration failed from June 9, last integration was done on June 22, but skipped qtbase and qtwayland. * * Issue: [QTBUG-68773][1] qtwayland build failed - can't find some headers * * *

[Development] Merge and Integration status report

Integrations * qt5 dev integration failed from June 18 * * Issue: [QTBUG-68848][1] tst_QQmlDebugJS fails too often in CI, perhaps a duplicate of [QTBUG-68741][2], the issue is there about two weeks, more talks in [previous report][4] * qt5 5.11 integration failed from June 9 * * Issue:

Re: [Development] clang-format

> On 19 Jun 2018, at 09:58, Joerg Bornemann wrote: > >> * Which branch do you run it in? If an early one, there's many merges to do. >> If >> a late one, all the subsequent merges are tricky. > > Our commit policy suggests that the right branch would be dev. > You're right that the merges

Re: [Development] clang-format

On Mon, 18 Jun 2018 at 11:23, Kari Oikarinen wrote: > On 18.06.2018 12:04, Frederik Gladhorn wrote: > > > Other parts sound good, so I'll just touch on the big question. > > > And then there is the big question when we run it once over the entire > > codebase. > > I'd hesitate to ever run it

[Development] Merge and Integration status report

Integrations * qt5 dev integration failed from June 2, a submodule update without qtdeclarative was done on June. 9 * * Issue: https://bugreports.qt.io/browse/QTBUG-68666 declarative_core::MappingManagerError::test_error() failed * * * https://codereview.qt-project.org/#/c/222768 Simon is

Re: [Development] QtCS 2018 - Serialisation session notes

On Mon, 11 Jun 2018 at 13:17, Thiago Macieira wrote: > Link: https://wiki.qt.io/QtCS2018_Serialisation > > === Protobuf === > > * Need volunteers to write a Proof of Concept > ** plugin to protoc? > > About protobuf support in Qt, I have an old WIP change at

Re: [Development] CI "wave-through"

5.11.0 is fine. Latest one is successful, https://testresults.qt.io/coin/integration/qt/qt5/tasks/1525572833 But looks like there are issues in qt5 dev integration, please check https://codereview.qt-project.org/#/c/227670/ and

Re: [Development] Qt Sanity Bot down

When Qt Sanity Bot is on vacation, here is the temporary solution, click "Review" button, unfold the "Sanity-Review" section under "Code-Review", just do a "+1 Sanity review passed". --Liang On 4 April 2018 at 10:14, Dominik Holland wrote: > Hi, > > it looks

Re: [Development] Proposing Albert Astals Cid for Approver

https://codereview.qt-project.org/#/q/owner:%22Albert+Astals+Cid+%253Calbert.astals.cid%2540kdab.com%253E%22,n,z https://codereview.qt-project.org/#/q/owner:albert.astals%2540canonical.com,n,z https://codereview.qt-project.org/#/q/owner:%22Albert+Astals+Cid+%253Caacid%2540kde.org%253E%22,n,z

Re: [Development] Rebasing

https://wiki.qt.io/Branch_Guidelines search "cherry-pick" BTW, you always can ask in #qt-labs channel at freenode, see https://wiki.qt.io/Online_Communities . Perhaps will get reply much faster without sending emails in mailing list. --Liang On 26 January 2018 at 16:14, Igor Mironchik

Re: [Development] CI is suffering from problems

both are known and fixes are available. https://codereview.qt-project.org/#/c/215113/ https://codereview.qt-project.org/#/c/215046/ — Liang > On 21 Dec 2017, at 14:17, Ulf Hermann wrote: > >> You have probably already noticed this, but here’s an email notifying >> you that

Re: [Development] QtBase broken in 5.9 and 5.10. Fix is already inbound.

https://codereview.qt-project.org/#/c/214045/ was merged. dev is fixed now. — Liang > On 11 Dec 2017, at 12:22, Liang Qi <liang...@qt.io> wrote: > > dev is blocked by "Module "" () Failed to provision template > 'qtci-osx-10.11-x86_64-3-9946c2’:” issue, sh

Re: [Development] QtBase broken in 5.9 and 5.10. Fix is already inbound.

5.10 was fixed. — Liang > On 11 Dec 2017, at 12:22, Liang Qi <liang...@qt.io> wrote: > > 5.9 was fixed. The merge to 5.10 is on the way. > https://codereview.qt-project.org/#/c/214051/ > > dev is blocked by "Module "" () Failed to provision template >

Re: [Development] QtBase broken in 5.9 and 5.10. Fix is already inbound.

5.9 was fixed. The merge to 5.10 is on the way. https://codereview.qt-project.org/#/c/214051/ dev is blocked by "Module "" () Failed to provision template 'qtci-osx-10.11-x86_64-3-9946c2’:” issue, should be fixed by following change: https://codereview.qt-project.org/#/c/214045/ — Liang > On

Re: [Development] Suggestion to add labels when changing API

ee > * Implement atomic commit across submodules not in Git, but in the > gerrit/COIN layer so that COIN effectively locks integrations until commits > that span submodules are finished > * Something else? > > Cheers, > Adam > > On 12/07/2017 11:22 AM, Liang Qi wrote:

[Development] Suggestion to add labels when changing API

Since http://lists.qt-project.org/pipermail/development/2016-October/027542.html , Coin tests all changes against Qt5 instead of the latest version of all modules. The situation is sth like, some new APIs were added to qtbase in 5.10, and other modules were adapted. But around beta or

Re: [Development] qtbase 5.9 is locked down for the time being

qtbase 5.9 is unlocked now. I didn’t see flaky things happened since yesterday. —Liang > On 24 Oct 2017, at 13:32, Liang Qi <liang...@qt.io> wrote: > > Hi, all, > > Since Oct. 20, only one change landed in qtbase 5.9, > https://codereview.qt-project.org/#/c/20909

[Development] qtbase 5.9 is locked down for the time being

Hi, all, Since Oct. 20, only one change landed in qtbase 5.9, https://codereview.qt-project.org/#/c/209093/ I will try to do manual stage in qtbase 5.9 to check whether it is because flakiness test or others. —Liang ___ Development mailing list

[Development] qtbase 5.9 is in chaos mode now

There is a gap in 6.19-6.26, only 2 changes are merged in qtbase 5.9. https://codereview.qt-project.org/#/q/project:qt/qtbase+branch:5.9+status:merged,n,z And now we have about 40 changes in staged mode, I don’t see much chance to get them in.

[Development] qtbase dev is blocked in CI

Hi, There is an integration sucks from last night for qtbase dev branch. And we can’t restart coin to cancel it due to current 5.9.1 integrations. Hope we can fix the issue this afternoon or a bit later today. So please don’t stage changes in qtbase dev for now, thanks. Best Regards, Liang

Re: [Development] Proposal for Qt 5.10 platforms and configurations changes

On 27 April 2017 at 22:50, Wolfgang Baron wrote: > Hi, > > I would like to see msvc_2017 support on the Windows plattform for any > version as soon as possible. That will happen soon in 5.9, please follow up https://codereview.qt-project.org/#/c/191981/ and etc.

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

On 11 April 2017 at 10:22, Ville Voutilainen wrote: > On 11 April 2017 at 10:30, Marc Mutz wrote: > > On Tuesday 11 April 2017 07:49:28 Tuukka Turunen wrote: > >> There has been a lot of discussion about this in the mailing lists, I > think > >>

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

On 11 April 2017 at 09:30, Marc Mutz wrote: > On Tuesday 11 April 2017 07:49:28 Tuukka Turunen wrote: > > There has been a lot of discussion about this in the mailing lists, I > think > > the two ones below sum it up quite well. > > .. > > You can close 5.8 on all other

Re: [Development] Who's responsible for 3rdparty these days (QTBUG-59586)?

On 19 March 2017 at 20:01, Thiago Macieira wrote: > The rules are that only Qt Company people can import 3rdparty code, so I > know > I am not responsible. > > Who do I assign the bug to? > https://bugreports.qt.io/browse/QTBUG-59586 For QTBUG-59586, I have

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

http://doc.qt.io/qt-5/supported-platforms.html msvc 2013 is still supported in 5.8 http://doc.qt.io/qt-5.6/supported-platforms.html msvc 2010/2012/2013 are still supported in 5.6 Compiler options for msvc 2015: https://msdn.microsoft.com/en-us/library/fwkeyyhe.aspx Compiler options for msvc

Re: [Development] HEADS-UP: Branching from '5.8' to '5.8.0' started

Then there will be batches of merges 5.6->5.7->5.8 before the final down merge 5.8->5.8.0. If your changes are after those merges, it will miss the 5.8.0 release normally. (cherry-pick only for the critical things after the final down merge.) And I plan to do the merges during weekends, if

Re: [Development] COIN

On 27 September 2016 at 19:23, manish sharma <83.man...@gmail.com> wrote: > Hi, > > I am working on a project which consists of around 20 git submodules and > we use jenkins as our CI. I was searching for an alternative to manage > builds and I came across COIN scripts which qt uses to run its

Re: [Development] dev doesnt builds

On 22 September 2016 at 13:17, Vlad Stelmahovsky wrote: > Hi > > trying build dev branch and got this error all the time: > > > Cannot read .qt5/qtbase/src/corelib/qtcore-config.pri: No such file > or directory > Cannot read

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

On 12 September 2016 at 11:20, Edward Welbourne wrote: > Marc Mutz said: > > The obvious question is, then, why is only "the one person" doing merges? > > Allow more people to upload merges, and you will get the spreading you > desire. > > Several people can upload

Re: [Development] No Gerrit notification email?

http://lists.qt-project.org/pipermail/development/2016-September/027083.html On 9 September 2016 at 08:39, Marc Mutz wrote: > Hi, > > I don't get notification emails from Gerrit anymore, and since the big > downtime of Gerrit and dev ML two(?) days ago only sporadically. > >

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

On 8 September 2016 at 09:36, Alexander Blasche wrote: > > From: Marc Mutz > > >On Wednesday 07 September 2016 08:37:01 Friedemann Kleint wrote: > >> ** After 5.7 is closed and sanity bot is upgraded (to

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

On 7 September 2016 at 08:37, Friedemann Kleint wrote: > Hi, > > the notes are at: https://wiki.qt.io/QtCS2016_Managing_Qt_Branches > > * Number of existing branches (5.6LTS, 5.7.,5.8 dev) causes a number of > problems > > ** Strain on COIN which also has release

Re: [Development] RHEL 7.2 added to Coin

Could we disable RHEL 7.2? at least for QtScript. There is a failure in qt5.git dev integration. It is the only blocker for it now. https://codereview.qt-project.org/162195 Best Regards, Liang From: Development

Re: [Development] Qt 5.8 branching & Feature Freeze

"Currently we can’t put anything new in, since Coin setup is frozen." Due to my limited knowledge with coin, I don't understand this. Coin, the new CI, should not bind with any paticular branch of Qt, but some options and scripts could. For the listed new OSes, openSUSE 42.1, Ubuntu 16.04, RHEL

Re: [Development] Qt + GCC 6 no joy ?

https://bugreports.qt.io/browse/QTBUG-53373 ? On 18 May 2016 at 10:01, Bogdan Vatra wrote: > Hi, > > Did anyone tried Qt (5.7) with GCC 6 ? > I compiled Qt and QtCreator (using debian's gcc 6) but it crashes in v4 > when I > start QtCreator :(. It's a know issue or just

Re: [Development] http://testresults.qt.io/ci/status/ stale?

The status of new CI: http://testresults.qt.io/coin/ On 21 March 2016 at 18:19, MrMstormo . wrote: > > Looks like > http://testresults.qt.io/ci/status/ > is stale? All reports are erroring out, and there's no reports for 5.6, > 5.7 etc? > > Is the CI system on an early

Re: [Development] INTEGRITY changes for 5.7

Do you plan to have them in 5.7 release? Current dev branch means 5.8... On 2 March 2016 at 08:24, Rolland Dudemaine wrote: > Hi, > > I understand that 5.7 has now reached feature freeze, but I would like > to ask for an exception for patches that have been pushed a few months

Re: [Development] Closing the 5.5 branch

https://codereview.qt-project.org/146557 still need to be integrated. On 8 February 2016 at 14:03, Frederik Gladhorn < frederik.gladh...@theqtcompany.com> wrote: > Hi all, > > due to the strain that we put on the VMs that are supposed to get the > releases > out and do the testing, we decided to

Re: [Development] A simple analysis of apps using qtbase's private headers

On 22 January 2016 at 04:15, Lisandro Damián Nicanor Pérez < perezme...@gmail.com> wrote: > The following three have something in common: they are all apps coded for > Chinese people. I've been told that they need QPA's private stuff in order > to > have proper input systems, but I haven't

Re: [Development] QFont::setFamily("monospace") on OS X

Perhaps QPlatformTheme::font() is related. https://github.com/qtproject/qtbase/blob/5.6/src/gui/kernel/qplatformtheme.h Regards, Liang On 21 January 2016 at 18:29, René J.V. wrote: > Hello, > > Not sure if this is the best place to ask: > I think

Re: [Development] Qt 5.5.0 header diff: QtDeclarative.diff

On 6 June 2015 at 10:52, Allan Sandfeld Jensen k...@carewolf.com wrote: On Friday 05 June 2015, Frederik Gladhorn wrote: Would there be any way to generate diffs or changes for QML APIs? Perhaps a diff for all plugins.qmltypes files? But I guess that not all were updated yet. --

Re: [Development] Updating of 3rdparty stuff

qtimageformats: libwebp 0.4.3 update https://codereview.qt-project.org/109955 https://codereview.qt-project.org/109956 And checked other 3rdparty: jasper, libmng, libtiff, there is no update from upstream. After Beta released, I will help to update qt doc and

[Development] Outdated Branch Guidelines and Commit Policy?

https://wiki.qt.io/Branch_Guidelines It's still in dev/stable mode, not the current 5.3/5.4/5.5/dev mode. https://wiki.qt.io/Commit_Policy Make sure to follow the Branch Guidelines. Submit against the lowest applicable branch from which a release is still planned. I have seen more and more bug

[Development] what's the latest status about tests/auto/bic/data?

Hi, Looks like we have binary compatible check things(at least for linux-gcc-ia32) before, but I only found 5.0.0 and 5.1.0 data. For example, https://github.com/qtproject/qtbase/tree/dev/tests/auto/bic/data https://github.com/qtproject/qtdeclarative/tree/dev/tests/auto/bic/data I forgot how it

Re: [Development] GIMP QML exporter script (project not on Gerrit)

I guess you mean this on github, https://github.com/qtproject/qt-labs-gimp-qmlexporter Then please contribute to https://codereview.qt-project.org/#/admin/projects/qt-labs/gimp-qmlexporter Good luck! Regards, Liang On 7 January 2015 at 08:33, William Hallatt goblincod...@gmail.com wrote:

Re: [Development] Platform maintainers

Is it possible also to add sub categories under QtPorts for Windows/XCB/OS X and etc in bug tracker? Regards, Liang On 10 January 2014 23:51, Knoll Lars wrote: Yes, I was about to write a mail about it. We don't currently officially have maintainers for platforms, but they exist in reality,

Re: [Development] gitorious error

Try github mirror? git clone git://github.com/qtproject/qt.git More in https://github.com/qtproject/ On 30 December 2013 19:35, Jiergir Ogoerg f35f22...@gmail.com wrote: Hi, I'm trying to follow the pile of tutorials to be able to contribute code to qt. At

Re: [Development] QSettings, OS X

On 18 December 2013 13:41, Samuel Gaist samuel.ga...@edeltech.ch wrote: Hi, I recently came across several posts talking about QSettings not working as expected on OS X (things not yet reported on the bug tracker). On OS X 10.9, it seems that Apple has decided to cache the application

Re: [Development] Qt5 release integration build

Those changes happened in stable branch, it means they will be part of 5.2.1, then doesn't block 5.2.0 final release. Anyway, patches are welcome! Regards, Liang On 10 December 2013 20:06, Kurt Pattyn pattyn.k...@gmail.com wrote: I suppose that the warnings in the list beneath are still

[Development] Wiki: 3rd party in Qt

Hi, all, I just spent some time to gather the information of 3rd party in Qt(5). http://qt-project.org/wiki/Third_Party_In_Qt Please help to update or maintain it. Maybe there is a legal issue about wintab, more details in their webpage: http://www.pointing.com/Wintab.html Regards, Liang

[Development] Asking for review: webp support in qtimageformats

Hi, all, Just see many people are interest in JP2 and ICNS things. I want to ask for review about webp support in qtimageformats again. There are changes available since May and June, https://codereview.qt-project.org/54689 https://codereview.qt-project.org/54690

Re: [Development] Qt-5.1, qglobal.h and PIC detection

On Wednesday 06 November 2013 12:17:56 Christian Gagneraud wrote: Hi, I'm using CLang build-analize tool, and when I switched from Qt 4.8 to Qt 5.1 (insalled from Qt project's download area), I got a Qt #error, basically the code is built with -fPIC, but CLang doesn't define a PIC macro, so

  1   2   >