+1
Thanks a lot for Michael's effort on a11y.
Best regards,
Liang
On Fri, 30 May 2025 at 12:18, Volker Hilsheimer via Development
wrote:
>
> Hi,
>
>
> I would like to nominate Michael Weghorn as an approver for the Qt project.
>
> Michael has for several years been an
On Thu, 15 May 2025 at 19:04, Liang Qi wrote:
> Current work in qtwayland repo side is not merged yet:
> https://codereview.qt-project.org/c/qt/qtwayland/+/637805
>
It was merged yesterday.
> qtwayland client contents(exclude adwaita, qt-shell, ivi-shell) needs
> to be don
until the corresponding patch is merged there.
>
Current work in qtwayland repo side is not merged yet:
https://codereview.qt-project.org/c/qt/qtwayland/+/637805
We are waiting for the next round from the qt submodule update bot.
--Liang
> Regards,
> Fabian
>
>
> On 15.05.25 17:
tly in review in Qt Wayland and do not get merged before the
> freeze. Sorry for the inconvenience!
https://codereview.qt-project.org/c/qt/qtbase/+/643564 got merged.
qtwayland client contents(exclude adwaita, qt-shell, ivi-shell) needs
to be done in qtbase now. Thanks.
--Liang
--
Development
On Mon, 12 May 2025 at 10:32, Arno Rehn wrote:
>
> On 07.05.2025 21:38, Liang Qi wrote:
> > On Wed, 1 Nov 2023 at 10:40, Oswald Buddenhagen
> > wrote:
> >> On Tue, Oct 31, 2023 at 10:33:27PM +0100, Arno Rehn wrote:
> >>> On 24.10.23 21:12, Arno Rehn wrote:
r some such. this would give it broader
> exposure, and it could get a proper review on gerrit.
There is not much activity since
https://codereview.qt-project.org/c/qt/qtgamepad/+/495313 , see
https://github.com/qt/qtgamepad/commits/dev/ .
+1 for pushing qtgamepadlegacy to 6.x-legacy-api, and it w
+1, thanks.
--Liang
From: Development on behalf of Tony
Sarajärvi via Development
Sent: Wednesday, January 22, 2025 9:08 AM
To: qt-dev ; Jukka Jokiniva
Cc: Tero Heikkinen
Subject: Re: [Development] Nominating Tero Heikkinen as an approver for the Qt
Project
+1
--Liang
From: Development on behalf of Jøger
Hansegård via Development
Sent: Wednesday, May 22, 2024 10:52 AM
To: development@qt-project.org
Subject: [Development] Nominating Tim Blechmann for approver
Hi all,
I would like to nominate Tim Blechmann for
+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
minutes. The link of the questionnaire (hosted at
Google Forms): https://forms.gle/nrLaZXQUq4QMS3bu6
Thank you very much for your participation!
Best regards,
Beiqi Zhang, Peng Liang, Liming Fu
Wuhan University, China
--
Development mailing list
Development@qt-project.org
https
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
0.108 driver on Ubuntu 18.04
in office. I could have a check with 5.15 build next week.
Best regards,
Liang
From: Development on behalf of Alexander
Procenko
Sent: Wednesday, March 1, 2023 8:36 PM
To: development@qt-project.org
Subject: [Development] who ca
+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 Qt
s://github.com/GNOME/glib/blob/main/gio/gapplication.h
* https://docs.gtk.org/gio/class.Application.html
Best regards,
Liang
From: Development on behalf of Ilya Fedin
Sent: Monday, April 25, 2022 12:16 PM
To: development@qt-project.org
Subject: Re: [Development]
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
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:
>
&
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. Resta
the short one week for feature frozen period, is perhaps needed.
—Liang
> On 11 Oct 2019, at 14:16, Jani Heikkinen wrote:
>
> +1
>
> This change might also speed up patch level releases a bit
>
> br,
> Jani
>
>
>
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
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
ches which are in active developemnt, wip/qt6 and wip/cmake. Lots of
things related with merges are expected. Hope we can impove the situation very
soon.
Nice weekend!
Report from Liang
___
Development mailing list
Development@qt-project.org
https://lis
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
What do you think?
See also https://bugreports.qt.io/browse/QTQAINFRA-2568 .
Best Regards,
Liang
>
> Alexey Rochev
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
__
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 questi
>dev will come, especially for qt5
Etc
* In these last few days for the 1st half year of 2019, there are several tasks
have more priority inside TQtC. So some cancellation of integrations happened
for this purpose. Hope this doesn't hurt much.
Enjoy summer(or
changes which
have comments of that sha1. How should I do if I only want to get the change
itself? Thanks.
Best regards,
Liang
> On 20 May 2019, at 15:00, Jukka Jokiniva wrote:
>
> Dear all,
>
> we are happy to inform you that Gerrit and COIN are back online and all
> operati
+Bot+%253Cqt_forward_merge_bot%2540qt-project.org%253E%22++status:open,n,z
* Healthy, 5.12.3->5.12 merges are done
--Liang
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> 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
merged in lower branch, please try to avoid use
duplicate Change-Id in upper branch, at least in the current merge order.
If you have a change landed in 5.12, and it's ok to have duplicate Change-Id
when you cherry-picked it to 5.9, because we don't do merge from 5.9 to 5.12.
++status:open,n,z
* Healthy, 5.12.2->5.12 merges are ongoing
--Liang
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
5.12->5.13
https://codereview.qt-project.org/#/c/254450/
* qt5 5.13->dev merge depends on qt5 dev integrated with latest qtbase first,
see https://codereview.qt-project.org/#/c/254215/
Happy International Women's Day! and nice weekend.
--Liang
__
.
In same direction of your change, perhaps to limit the qt5 integration numbers
in parallel is bit better than the 15 minutes one.
—Liang
> On 25 Feb 2019, at 13:41, Aapo Keskimölö wrote:
>
> Dear Developers,
>
>
> It has recently been raised to our attention that some int
affected by above issue.
* qt5 5.13, haven't tried, because the final down merge dev->5.13 is not
finished yet
--Liang
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
/027542.html
via
https://web.archive.org/web/20161108191742/http://lists.qt-project.org/pipermail/development/2016-October/thread.html
--Liang
On Fri, 25 Jan 2019 at 14:00, Edward Welbourne wrote:
>
> Hi all,
>
> Again, our sysadmins claim they've fixed what was broken in the
&g
+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 whil
the period to have "dev" branches for both
5 and 6. I don't have solution for this issue yet.
Best regards,
Liang
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
stions...
Integrations
* qt5 5.12.1/5.12 are healthy
* qt5 dev is 5 days old, expected to have new round with qt5 5.12->dev merge
after QTQAINFRA-2591 got fixed
--Liang
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org
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
2 is healthy
* dev got latest submodule update merged in
https://codereview.qt-project.org/#/c/174522/ this morning.
Happy new year!
--Liang
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ne team is working on
it
Gerrit
* qtbase 5.12 is still locked(others repos 5.12 got unlocked on Nov. 13 morning)
-- Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> 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?
>
> 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
>&g
> 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
asks/1543278570
* https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1543265593
* https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1543189785
[1]: https://testresults.qt.io/grafana/
-- Liang
___
Development mailing list
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 shor
.qt-project.org/#/c/240554/
(Docker Provisioning: Install Docker-based test servers on macOS) soon
-- Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi, Tony,
Now the current integration for https://codereview.qt-project.org/#/c/239542/
and another change looks promising. Thanks.
And I plan to hi-jack qtbase 5.12 branch for a batch of qmake and android
changes after this integration once more.
—Liang
> On 12 Oct 2018, at 08:12, T
least before the issue got fixed.
Best Regards,
Liang
> On 12 Oct 2018, at 07:16, Tony Sarajärvi wrote:
>
> Wow… ok it took longer than expected (as usual). Not only did we have to
> remove snapshots, we also had to run unmap on the Compellent, so this whole
> thing took a while.
dev, last integration was two weeks ago, will try a new one after
qtwebengine 5.12->dev merge finished, see
https://codereview.qt-project.org/#/c/241338/ , still need someone's +2.
-- Liang
___
Development mailing list
Development@qt-project.
lleagues are working on that. During this
period, perhaps qmake timeout issue is very common on all platforms, including
Linux, Windows and macOS.
-- Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/
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 g
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&#
soon, suggest to revert
https://codereview.qt-project.org/#/c/235685/ for now, because there are
about 20-30
changes including a 5.11->dev merge in qtbase which are not integrated in
qt5 dev yet.
Merges - healthy!
Thanks Simon and Edward for their work during July!
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
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 j
at
https://codereview.qt-project.org/#/q/owner:qt_forward_merge_bot%2540qt-project.org+status:open,n,z
and integrations at
https://codereview.qt-project.org/#/q/owner:qt_submodule_update_bot%2540qt-project.org+status:open,n,z
.
-- Liang
___
Developm
. But it wasn't enough.
>
> Are you sure you already have the fix (it went into 5.11 first)? Because
> with the patch, you shouldn't see those 'line #xxx' things at all anymore.
> bidiTest should just report one single line.
>
>
> Latest qtbase 5.11->dev me
lly want to
have this merged as soon as possible.
Looks like there is some issue with coin, need someone's help to check, perhaps
reboot is needed.
-- Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/
ew.qt-project.org/#/c/232288/ Robert Griebl has a fix,
Oswald please help to review it. Suggest to revert to get 5.11 integrated
again, [see the revert][2]
Merges
* qtbase 5.11->dev, the merge is blocked because [QTBUG-68773][1] is not fixed
yet.
-- Liang
[1]: https://bugreports.qt.io/browse/QTB
] is not fixed
yet.
-- Liang
[1]: https://bugreports.qt.io/browse/QTBUG-68666
[2]: https://bugreports.qt.io/browse/QTBUG-68741
[3]: https://bugreports.qt.io/browse/QTBUG-68773
[4]: http://lists.qt-project.org/pipermail/development/2018-June/032
dev.
> You're right that the merges will be harder. What's the opinion of our merge
> master?
>
>
We will have 5.11 for a while, perhaps a 5.11.2 after summer at least. So
better to do it in 5.11, and after it got merged in dev, then do
it-hyper-blame ?
https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/git-hyper-blame.html
--Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
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 workin
eview.qt-project.org/#/c/205316/ . But not sure whether it can
help here or not.
Best Regards,
Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
/1525573813 .
My proposal is switch qtdeclarative back to
913dc3f4f2be7c2c23237bcb9bffb3192cb10d60 . The new patch set PS5 is pushed
there, and have a background build(status check) running, looks good by now.
— Liang
> On 27 Apr 2018, at 12:28, Tuukka Turunen wrote:
>
>
> Hi,
>
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,
>
Chrome is good to copy and paste those urls.
+1, but which one of above three gerrit accounts will get the permission?
And how about his career future?
--Liang
On 21 March 2018 at 12:33, Sérgio Martins wrote:
> Hi,
>
>
> Albert has been a long time contributor to KDE and Qt a
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 Mironc
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 tha
https://codereview.qt-project.org/#/c/214045/ was merged. dev is fixed now.
— Liang
> On 11 Dec 2017, at 12:22, Liang Qi wrote:
>
> dev is blocked by "Module "" () Failed to provision template
> 'qtci-osx-10.11-x86_64-3-9946c2’:” issue, should be fi
5.10 was fixed.
— Liang
> On 11 Dec 2017, at 12:22, Liang Qi 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
> 'qtci-osx-10.11-
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/21
/QTBUG-19580
https://bugreports.qt.io/browse/QTQAINFRA-824
— Liang
> On 7 Dec 2017, at 18:17, Adam Treat wrote:
>
> Hi,
>
> I think it is high time that we fix the underlying problem: supporting atomic
> commits across submodules.
>
> Once this is done we should rever
purpose, please give your
suggestion and votes. Thanks.
Best Regards,
Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
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 wrote:
>
> Hi, all,
>
> Since Oct. 20, only one change landed in qtbase 5.9,
> https://codereview.qt-project.org/#/c/209093/
>
> I will t
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
/qtbase+branch:5.9+status:open,n,z
Perhaps I can try to be the stage monkey, but I need to know which batch/set of
changes need to be staged together. Please report here or irc, thanks.
Regards,
Liang
___
Development mailing list
Development@qt
This issue was gone. qtbase dev is safe.
—Liang
> On 23 Jun 2017, at 09:27, Liang Qi wrote:
>
> 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
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
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
dea47e7ee84e017f4113844df5b1
There are only 6 changes in qtdeclarative.
Here is the merge for you: https://codereview.qt-project.org/191380
I normally will do merge if more than 10 changes, asked by someone, or just
before some releases(like 5.9 rc) and etc.
Certainly, there will be merges when 5.
all other modules, if you wish, but I'd ask to keep it
> open on QtBase, which has a lively development going on in 5.8 to this day.
>
Any new change in qtbase means need a new round of qt5.git integration and
rebuild all other modules, because th
en add this in the
modules? And there is common procedure for this purpose? for example,
patches and qt_attribution.json file if upstream doesn't have it.
Best Regards,
Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-proje
2013:
https://msdn.microsoft.com/en-us/library/fwkeyyhe(v=vs.120).aspx
If not all supported compilers support /utf-8 or similar options, what should
be done next step?
Best Regards,
Liang
> On 30 Jan 2017, at 17:30, Thiago Macieira wrote:
>
> On segunda-feira, 30 de janeiro de 2017 09:
https://codereview.qt-project.org/#/c/183817/
On Mon, Jan 30, 2017 at 4:42 PM, Marc Mutz wrote:
> On Monday 30 January 2017 02:21:57 Thiago Macieira wrote:
> > qCDebug(lcTuioSet) << "Processing SET for token " << classId << id
> << "
> > @ " << x << y << "∡" << angle <<
> >
> > That's easy
Start from qt-5.8 I can't build qt anymore under Windows(simplified
chinese locale). Since there is a file
src/plugins/generic/tuiotouch/qtuiohandler.cpp which contain non-latin-1
character, msvc2015 assume the source code's character set should be CP936
which make the complilation fail.
I
ds, if CI/COIN works fine. Or if
you want your changes not missing this chance, please send some
notification to me, for example, reply this email to me(not all).
Best Regards,
Liang
On 21 November 2016 at 14:50, Jani Heikkinen wrote:
> Hi,
> We have started branching from '5.8'
Oct 15, 2016 at 11:48 PM, Thiago Macieira wrote:
> Em sábado, 15 de outubro de 2016, às 15:33:53 PDT, Liang Jian escreveu:
> > But I am still curious about that If we don't unload the plugin, will
> > the destructor of the gobal object in it be called? If it is not called,
be called? If it is not called,
what if the gobal object of the plugin hold some memory allocated from heap?
On Sat, Oct 15, 2016 at 2:07 AM, Thiago Macieira
wrote:
> Em sexta-feira, 14 de outubro de 2016, às 16:08:27 PDT, Liang Jian
> escreveu:
> > I don't care custom
you don't think that are leaks but they will confuse memory leak detector),
that is why I hope to introduce a method to disable this feature at runtime.
On Fri, Oct 14, 2016 at 1:10 PM, Thiago Macieira
wrote:
> Em sexta-feira, 14 de outubro de 2016, às 09:11:48 CEST, Liang Jian
> escr
Macieira wrote:
> Em quinta-feira, 13 de outubro de 2016, às 22:00:35 CEST, Liang Jian
> escreveu:
> > Not unloading plugin is really a bad idea.
> > That will make any memory leak detector report tons of leaks even
> run a
> > simplest qt widgets program. Find and fix
Not unloading plugin is really a bad idea.
That will make any memory leak detector report tons of leaks even run a
simplest qt widgets program. Find and fix 'real' memory leak will be much
harder than before.
On Thursday, October 13, 2016, Thiago Macieira
wrote:
> Em quarta-feira, 12 de
me know if someone knows the repo link.
>
https://blog.qt.io/blog/2016/08/08/coin-continuous-integration-for-qt/
It's not in public domain yet.
Regards,
Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
branch for all modules except qtbase are blocked by
https://bugreports.qt.io/browse/QTBUG-56122 .
Regards,
Liang
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
upload merges.
> One person looks after integration in qt5 and all its sub-modules.
> We can spread the load (indeed, I carried it for a few weeks while
> Liang was on holiday), and I believe module owners can do their own
> merges (which saves the integration team work), but the integr
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.
>
> Anyone else seeing t
ts.
https://codereview.qt-project.org/#/c/163938/
Other cases are sth like directories reorganization, class renaming and
etc, it's very annoying when developers have changes in similar places in
5.6 and upper branches.
Best Regards,
Liang
> --
> Alex
> _
rs to have a more stable release of 5.7.2.
If we stick to do release like this kind of order, 5.6.2->5.7.1->5.8.0
Beta, it's not very difficult to have a 5.6.3->5.7.2->5.8.0 or similar.
And I would like to see it becomes a convention for future releases.
Best Regards,
Liang
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 on behalf
of Frederik Gladhorn
Sent: Monday
perience, at least for me. Perhaps it's
because lacking of binaries for 5.6 snapshots, then not enough usage and
testing.
Best Regards,
Liang
On 16 June 2016 at 08:57, Tony Sarajärvi wrote:
> Hi,
>
>
>
> Our aim was to get new platforms in immediately after the previ
1 - 100 of 177 matches
Mail list logo
