Re: [Development] Qt 6.5.2 release date delayed?

[Andy Shaw via Development]

Hi,

It is planned for releasing tomorrow so just hold out for one more day 

Kind regards,
Andy

-Original Message-
From: Development  On Behalf Of Ilya Fedin
Sent: Tuesday, July 18, 2023 3:59 PM
To: development@qt-project.org
Subject: Re: [Development] Qt 6.5.2 release date delayed?

On Thu, 13 Jul 2023 17:55:51 +
Tarja Sundqvist via Development  wrote:

> Hi Mathieu & all,
> 
> unfortunately, Qt 6.5.2 has been delayed. The final test round for the 
> release candidate is currently ongoing, though. My current estimate is 
> that we can release 6.5.2 at the beginning of next week if there are 
> no critical findings on the remaining tests. I’ll update this also to 
> the Qt’s wiki page – I’m sorry that I didn’t do it already earlier 
> (Jani Heikkinen who’s usually managing Qt 6.5.x releases is currently 
> on summer holiday and I’m substituting for him).
> 
> Best regards,
> Tarja Sundqvist
> Release manager
> 
> From: Development  On Behalf Of 
> Mathieu Pellerin Sent: torstai 13. heinäkuuta 2023 12.33
> To: development@qt-project.org
> Subject: [Development] Qt 6.5.2 release date delayed?
> 
> Greetings all,
> 
> Quick question: the Qt 6.5 release schedule
> (https://wiki.qt.io/Qt_6.5_Release) indicates that the next point 
> release was set to happen on June 28. Has the release date been 
> officially moved or can we expect it in the coming days?
> 
> Best,
> 
> Mathieu Pellerin
> 

Has the release delayed again?
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] [Announce] Security advisory: Freetype in Qt

[Andy Shaw]

Hi,

The existing pre-built versions of 5.15 and 6.2 will have this problem yes, but 
I don’t know what the plan would be for releasing an update one in these cases 
though. That would be down to the release team to comment on.

Kind regards,
Andy

-Original Message-
From: Development  On Behalf Of Giuseppe 
D'Angelo via Development
Sent: Wednesday, July 27, 2022 2:21 PM
To: development@qt-project.org
Subject: Re: [Development] [Announce] Security advisory: Freetype in Qt

Hello,

Il 27/07/22 14:00, List for announcements regarding Qt releases and development 
via Development ha scritto:
> These effects configurations of Qt that have been built against the bundled 
> version of FreeType. If you are using a pre-built version of Qt then this 
> will be using the bundled version of FreeType by default, otherwise you will 
> be using the system version by default, in which case you should check if the 
> system needs to be updated or not. If the system needs to be updated, then 
> updating it is enough to solve the issue. There is no need to rebuild Qt in 
> that case.

Does this mean that the currently available opensource binary downloads 
(through the official installer) of Qt 5.15(.2) and 6.2 are affected by 
the CVE and will not get fixed?

Should they just be removed from the online installers?

Thanks,
-- 
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] New Chief Maintainer

[Andy Shaw]

Hi,

Based on the wording I agree, it is clear that all maintainers should vote in 
this case, and it is a simple majority of those maintainers. Any maintainer who 
does not vote is not counted as part of the total, so if there is a single 
candidate then a vote is redundant, because you are voting for someone, 
abstaining means it is not counted in the total. If there are multiple 
candidates, then it has to be a majority, meaning more than half of the votes 
to win (https://en.wikipedia.org/wiki/Majority#Majority_vote - simple majority 
is covered here), but if there is only 2 candidates then one can reasonably go 
with the fact that the one with the most is the de-facto winner because if you 
redid the vote without the candidate with the fewest votes then it's fairly 
clear cut. If there is more than 2 then we should drop the one with the fewest 
votes and redo the vote and so on until we do indeed have a simple majority.

One other thing is that I think that we should do our best to make sure the 
maintainers (as a group) are aware of this, we have basically just given then 1 
week to agree on the new Chief Maintainer, which to be frank, is not long 
enough. The QUIP says 1 month's warning and Lars has given that, so we should 
use most of that month to allow a proper process and to give people a chance to 
actually get the news. All of the maintainer's email addresses are on the wiki 
so we should have a mail sent directly to them to indicate that this happened 
(not everyone is on the mailing list, and the vote itself might slip by people 
if they are on vacation or similar otherwise when it gets announced) and that 
way we can be sure everyone has been given enough time to react and vote if 
they should choose to. This is a vote which is important to the Qt Project and 
my opinion on who should be Chief Maintainer has no bearing on things since I 
am not a maintainer, but I would like to see this process make it clear that 
everyone (who is in the position to do so) feel that they had a say in this , 
and that the Qt Project is truly an open project.

Regarding the nomination process, this is woefully under documented in the QUIP 
as there is no indication as to how you get nominated for Chief Maintainer, 
from the reading of it the Maintainers themselves decide who should be Chief 
Maintainer by way of simple majority but that could in theory mean anyone can 
be nominated for it. I think that anyone can put themselves forward for being 
Chief Maintainer and should also give an indication as to why they feel they 
would be ideal for the position. Then this could be voted on in a voting page 
like we did with the previous situation so that the actual votes are 
confidential. 

Regardless of who gets the position, QUIP 2 does need to be tightened up in a 
number of ways, we should be a lot clearer on this process to avoid problems 
next time, and also there should be general wording on what happens when a 
maintainer is no longer active, if there is no one having the responsibilities 
for them formally delegated, then it shouldn't need a vote to have the 
privileges removed.

Kind regards,
Andy

-Original Message-
From: Development  On Behalf Of André Somers
Sent: Friday, May 20, 2022 5:43 AM
To: Volker Hilsheimer ; development@qt-project.org
Subject: Re: [Development] New Chief Maintainer

Hi Volker,

On 19-05-2022 22:42, Volker Hilsheimer wrote:
>> On 18 May 2022, at 11:23, André Somers  wrote:
>>
>>
>> On 18-05-2022 11:19, André Somers wrote:
>>> As I understand it [1], this needs a formal vote. However, the QUIP 
>>> does not specify a full procedure. I would suggest:
>> And then I forget the actual link:
>>
>> https://quips-qt-io.herokuapp.com/quip-0002.html#how-to-become-chief-
>> maintainer
>
> Thanks André.
>
> The QUIP asks for a simple-majority vote of all Maintainers. Either way, 
> let’s see what other nominations we get.
>
> May I propose that until end of Wednesday 25th, Maintainers can nominate 
> other candidates (including themselves), and then we can have a vote amongst 
> those candidates nominated (the simple majority is enough as per QUIP). The 
> QUIP doesn’t explicitly require the candidate to be a Maintainer.
>
> If we have only one candidate by end of Wednesday, then we can use lazy 
> consensus, i.e. as long as none of the maintainers object to the candidate, 
> that candidate becomes chief maintainer. Although I’d expect that whoever has 
> an objection to one candidate also nominates another candidate.

The procedure outlined in the linked QUIP is substantially different from the 
procedure outlined for becoming a Maintainer. The wording to me suggest we need 
an actual vote in this case, not a lazy consensus. The "simple majority" refers 
to the needed number of votes out of the quorum (simple majority meaning >50%), 
not the simplicity of the voting procedure IMO.

So no, I don't think a lazy consensus will do. And no, I don't think it's 
having an objection to a 

Re: [Development] Maintainance Tool

[Andy Shaw]

Hi,

It is because your IP is detected to be in a country we do not allow downloads. 
If you are not able to access something you have purchased then let me know and 
I will get someone to get in touch with you directly about this. Otherwise, for 
the time being, this IP block will be in place.

Regards,
Andy

From: Development  On Behalf Of Konstantin 
Ritt
Sent: Friday, March 4, 2022 1:43 PM
To: Konstantin Shegunov 
Cc: Qt development mailing list 
Subject: Re: [Development] Maintainance Tool

I don't care. I need some explanations here, at public dev ML.

Regards,
Konstantin


пт, 4 мар. 2022 г. в 15:27, Konstantin Shegunov 
mailto:kshegu...@gmail.com>>:
Hi,
I imagine you're using a russian IP address, so this[1] should shed some light 
on the matter.

Kind regards,
Konstantin.

[1]: https://forum.qt.io/topic/134724/unlock-qt-in-russia
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Welcome to our Qt Champions for 2021!

[Andy Shaw]

 a Lifetime Champion! During the last year Denis has 
once again submitted an exceptionally high number of patches to Qbs and Qt 
Creator and has continued to keep the Visual Studio code extension for Qbs 
which brings the Qbs project to an even wider audience too. Their dedication to 
keep Qbs going as an active project, much to the delight of those who continue 
to use it over CMake and qmake is what makes Denis our Maverick this year and a 
well deserved new Lifetime Champion. Congratulations Denis on being our seventh 
Lifetime Champion!

So congratulations to all of our Qt Champions for 2021 and congratulations to 
Denis once again on becoming our 7th Lifetime Champions.

Thank you to all of you and to all of your in the community for making this a 
great community to work with and thank you to Softanics for your very generous 
prize for our winners. I hope to work with all of you again in 2022! Let's make 
2022 an even better year for Qt!

Kind regards,
Andy
--
Andy Shaw
The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qbs development

[Andy Shaw]

On Thu, Sep 16, 2021 at 09:34:00AM +, Oswald Buddenhagen wrote:
> the thing is that an agreement *can* be reached, as has been many times
> before. the maintainer just doesn't give a shit.

Can we refrain from using such language on the mailing list? Not everyone 
appreciates it and there is no reason to use such language for any reason as 
part of a public discussion. The point can still be made without having to 
resort to swearing to make it.

Kind regards,
Andy
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Svar: Changes to Freenode's IRC

[Andy Shaw]

I can’t speak for QtCentre as that is not something the Qt Project has any 
control over at all. But forum.qt.io is using NodeBB which is an OpenSource 
project, so unless I am missing something then it is free software.

Andy

Fra: Development  på vegne av Jason H 

Dato: onsdag, 19. mai 2021 kl. 18:24
Til: Lisandro Damián Nicanor Pérez Meyer 
Kopi: development 
Emne: Re: [Development] Changes to Freenode's IRC
> Hi!
>
> On Wed, 19 May 2021 at 12:30, Jason H  wrote:
> >
> > Aren't all the kids these days moving to Discord?
>
> Discord is not free software, so it does not align well with a free
> software project.

QtCentre is not free software
forum.qt.io is not free software

What is the point of having alignment on the license of the service with the 
project license? Shouldn't the service be able to pick the best (for various 
definitions of "best") software for providing the service? Open Source servers 
may still require onerous terms of service to be used, the underlying code 
license implementing the service is a separate matter. I would say that as long 
as there is openly available clients for users to use, the license isn't as 
important as the terms of use for the service itself. (I'm sure Stallman would 
still disagree though) I'm open to preferring open services, but I just think 
the terms are more important than the license of the code base implementing the 
service, for me anyway.

I often wonder if Qt is still qualifies as "free software" under the new 
management? (Stopping LTS for OpenSource users in the middle of a LTS series 
really shattered my trust in Digia, if you can't tell)






___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Svar: Nominating Jarkko Koivikko as an approver

[Andy Shaw]

+1

Andy

Fra: Development 
Dato: mandag, 18. januar 2021 kl. 11:46
Til: development@qt-project.org 
Emne: [Development] Nominating Jarkko Koivikko as an approver
Hi.

I would like to nominate Jarkko Koivikko as an approver for the Qt Project.

Jarkko has been contributing to the Qt project since mid-2014, having 
practically written the entirety of the Qt Virtual Keyboard module. His 
knowledge in this area is second to none, and would be a great asset in 
ensuring the quality of commits and moving the module forward in general.

Here is the list of his changes on Gerrit:

https://codereview.qt-project.org/q/owner:jarkko.koivikko%2540code-q.fi

Cheers.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Reminder: Qt Code of Conduct

[Andy Shaw]

Hi,

This mail is being posted to all of the mailing lists individually, but not 
cross-posted because that is an invite to create havoc so for those on multiple 
mailing lists then I apologise for the fact you will get this more than once.

The Qt Code of Conduct was created and agreed upon back in October 2018 and we 
have had a lot of new contributors and people joining the Qt community that it 
is time for a reminder that the Qt Code of Conduct exists and that it is worth 
refreshing everyone's memory about it. I am happy to say that the communities 
conduct as a whole is generally positive and aside from issues occasionally 
things are going in the right direction and this community is a good place to 
be a part of. That said, it does not hurt to look at the Qt Code of Conduct 
again, or maybe in some cases for the first time which you can find here:

  http://quips-qt-io.herokuapp.com/quip-0012-Code-of-Conduct.html

I would like to add that this email is not an invitation to discuss the content 
of the Qt Code of Conduct whether you agree with it or not, but merely to 
remind people that it exists for the benefit of everyone who is part of the Qt 
community.

The Qt community has been a fundamental aspect of the Qt Project since the 
beginning, let's keep having a nice and welcoming environment to everyone.

Thank you for your time,

Andy
--
Andy Shaw
The Qt Company

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] [RFC]: Modification to QUIP-15: Security policy

[Andy Shaw]

Hi!

I have been asked in my capacity as part of the Qt Support team to update 
QUIP-15 which is about the security policy, to cover the fact that those with a 
commercial license can report issues to the Qt Company Support team. This is so 
that they can confidentially report anything they find to us and also we can 
handle any commercial only reports directly too. I have done the changes under 
proposal here:

  https://codereview.qt-project.org/c/meta/quips/+/303295

I will update the change with a link to the thread in the archive once this 
post makes it there, feel free to comment how you see fit if you have any 
feedback.

Kind regards,
Andy

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Toni Saario as approver

[Andy Shaw]

Seems that the 25 got dropped in the link you had in the browser. If that is in 
there then it does find all 8 pages. You can also just add:

 owner:toni.saa...@qt.io

to the search field and that should work too.

Regards,
Andy

-Original Message-
From: Development  on behalf of Sergio 
Ahumada 
Date: Monday, 9 March 2020 at 21:20
To: "development@qt-project.org" 
Subject: Re: [Development] Toni Saario as approver

On 09.03.20 12:58, Heikki Halmet wrote:
> Hi all, 
> 
> I’d like to nominate Toni Saario as approver for the Qt Project.
> 
> Toni has been working in the CI team as a Coin SW developer since he
> joined the Qt Company over one year ago. First as a trainee and starting
> from last august as a full-time employee. Toni has been focusing mainly
> to improve and maintain Coin SW. I’ll trust that he will use the
> approver rights responsibly and follow the Qt guidelines.
> 
> Here is the list of his changes:
> 
> https://codereview.qt-project.org/q/owner:toni.saario%2540qt.io,175

"No changes"

-- 
Sergio Ahumada
sahum...@texla.cl


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Daniel Smith as approver

[Andy Shaw]

+1 from me too

Andy

-Original Message-
From: Development  on behalf of Volker 
Hilsheimer 
Date: Monday, 2 March 2020 at 17:42
To: "development@qt-project.org" 
Subject: [Development] Nominating Daniel Smith as approver

Hi all,


I’d like to nominate Daniel Smith as approver for the Qt Project.

Daniel has been working with Qt since he joined the Qt Company as a 
full-time employee in the Oslo QA team two years ago.

He’s been focusing on the QA infrastructure, which includes the test rigs 
for the rendering tests, and enabling auto-testing on Android. More recently, 
Daniel has implemented a bunch of very useful tooling, such as the 
un-blacklisting tool, and the cherry-pick bot that will implement our new 
branch policy.

He’s a gerrit admin, and I trust that he will follow the Qt guidelines, and 
use the approver rights responsibly.

Here is a list of his changes:
  https://codereview.qt-project.org/q/owner:Daniel.Smith%2540qt.io


Disclaimer: I’m Daniel's manager in the Qt Company.


Best regards,
Volker

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating André Hartmann for maintainer for QCanBus API

[Andy Shaw]

+1

Andy

-Opprinnelig melding-
Fra: Development  på vegne av Alex Blasche 

Dato: tirsdag 26. november 2019 09:39
Til: "development@qt-project.org" 
Emne: [Development] Nominating André Hartmann for maintainer for QCanBus API

Hi,

The QCanbus API is part of the QtSerialBus module. Since its first release 
it has come a long way. In particular, André Hartmann & Denis Shienkov made big 
contributions over time. For that I am very grateful. Thank you.

As the current maintainer of the QCanBus API I would like to hand the 
maintainer baton over to André. 

He has done a very good job of fixing the day-to-day issues popping up on a 
regular base. Unrelated to QtSerialBus, he contributed to Qt Creator and other 
parts in QtBase.

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Gerrit update

[Andy Shaw]

Isn't it the stage one you want anyway as that puts it to CI etc.

Andy

-Opprinnelig melding-
Fra: Development  på vegne av 
"development@qt-project.org" 
Organisasjon: KDAB
Svar til: Bogdan Vatra 
Dato: tirsdag 1. oktober 2019 07:56
Til: "development@qt-project.org" 
Emne: Re: [Development] Gerrit update

Hi,

  Since yesterday I can't submit any of my patches. The submit "button" is 
gay, e.g. https://codereview.qt-project.org/c/qt/qtbase/+/273675 

Am I doing something wrong?

Cheers,
BogDan.

În ziua de luni, 30 septembrie 2019, la 09:40:36 EEST, Heikki Halmet a 
scris:
> Hi,
> 
> Coin fixed and integrations should be work now. 
> Thanks for your patience!
> 
> 
> Br
> Heikki
> 
> -Original Message-
> From: Development  On Behalf Of Heikki
> Halmet
 Sent: maanantai 30. syyskuuta 2019 9.20
> To: Jukka Jokiniva ; Qt Project Development
> Mailing-List 
 Subject: Re: [Development]
> Gerrit update - problem with integrations 
> Hi,
> 
> We have problem in Coin with the newer Gerrit version. It means that
> currently integrations won't work. We are fixing the issue with highest
> priority.
 
> 
> Br
> Heikki
> 
> -Original Message-
> From: Development  On Behalf Of Jukka
> Jokiniva
 Sent: maanantai 30. syyskuuta 2019 8.52
> To: Qt Project Development Mailing-List 
> Subject: [Development] Gerrit is back online
> 
> 
> Gerrit is back online,
> 
> Main changes to the functionality are:
>* Confirmation dialog for Stage button has been removed.
>* Each staging attempt doesn't not generate new patch set for the 
change.
> New patch set is added only after successful integration.
 
>  --Jukka
> 
> 
> 
> On 30/09/2019, 7.57, "Development on behalf of Jukka Jokiniva"
> 
> wrote:
 
> 
> Hi,
> 
> Gerrit 3.0.2 upgrade starts in 5 minutes. The 
codereview.qt-project.org
> will be offline for about  20 - 30 mins.
 
> --Jukka
> 
> 
> 
> On 23/09/2019, 16.50, "Development on behalf of Frederik Gladhorn"
> 
> wrote:
 
> Hi all,
> 
> I hope this is a complete no-event, but we'd like to give you a
> heads-up, in 
 case something unexpected comes up. We Gerrit admins are
> currently working towards moving us to Gerrit 3.0.2.
> 
> The plan is to upgrade on Monday next week, the 30th of September.
> There are no huge improvements in Gerrit itself, it's a cleanup
> release 
 mostly, getting rid of the old database handling moving
> completely to note-db. 
> We don't expect major issues, the testserver upgrade takes around
> five minutes, 
 so there will be a short down-time, but otherwise there
> shouldn't be any real interruptions.
> We'll be testing in the meantime and may still postpone the 
upgrade,
> in case 
 any blockers are found.
> 
> Cheers,
> Frederik
> 
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Kavindra Palaraja for approvership

[Andy Shaw]

+1 from me too. I have reviewed a number of her doc patches and she would be a 
good asset to help with approving too!

Andy

From: Development  on behalf of Paul 
Wicking 
Date: Thursday, 11 July 2019 at 17:29
To: "development@qt-project.org" 
Subject: [Development] Nominating Kavindra Palaraja for approvership

Hi all,

I’d like to nominate Kavindra Palaraja as approver. She is a very active 
contributor and reviewer, in particular for documentation related changes, 
focusing on the Qt Automotive platform. She’s a former employee of Trolltech 
and Nokia, and has a lot of experience with Qt’s documentation. Currently, she 
is employed as tech writer for Luxoft.

If you're curious, here's a list of her changes:

https://codereview.qt-project.org/q/owner:kpalaraja%2540luxoft.com

and a list of changes she's on as a reviewer:

https://codereview.qt-project.org/q/reviewer:kpalaraja%2540luxoft.com


Best,
Paul
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Dropping sqlite2 plugin for Qt6/cmake port

[Andy Shaw]

I am all for it, we should also drop QTDS at the same time, that has been 
obsoleted since 4.7 and it is high time for removal.

Andy
 

-Original Message-
From: Development  on behalf of 
"development@qt-project.org" 
Reply-To: Albert Astals Cid 
Date: Friday, 3 May 2019 at 10:46
To: "development@qt-project.org" 
Subject: [Development] Dropping sqlite2 plugin for Qt6/cmake port

While trying to get more src/plugins/sqldrivers/ code built with CMake i 
realized that there is no FindSQLite2.cmake in cmake and we would have to 
create/maintain our own.

Then i realized that the latest release of sqlite2 was on 2005 and thought 
maybe we can just drop it?

So I'm proposing to drop src/plugins/sqldrivers/sqlite2/ from Qt6/cmake 
port 
of Qt.

Opinions?

Best Regards,
  Albert

P.S: sqlite3 code is already building fine in the cmake port

-- 
Albert Astals Cid | albert.astals@kdab.com | Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - The Qt, C++ and OpenGL Experts

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt 5.14.0 schedule proposal

[Andy Shaw]

I think you have a typo there ( 17 weeks before 26.11.2019 would be 30.07.2019.

Andy

-Original Message-
From: Development  on behalf of Edward 
Welbourne 
Date: Thursday, 2 May 2019 at 10:27
To: Jani Heikkinen 
Cc: "development@qt-project.org" , 
"releas...@qt-project.org" 
Subject: Re: [Development] Qt 5.14.0 schedule proposal

Jani Heikkinen (2 May 2019 08:00)
> We are in final steps with Qt 5.13.0 release and so on it is time to 
start planning Qt 5.14.0 initial schedule.
>
> Qt 5.13 isn't indicating anything why we could cut the schedule so my 
proposal is based on Qt 5.12.0 and Qt 5.13.0 ones:
>
> - 19.08.2019: Soft branching from 'dev' to '5.14' start
> - 26.08.2019: Feature Freeze & Finalize branching from 'dev' to '5.14'
> - 03.09.2019: Alpha release
> - 17.09.2019: Beta1 release
> - 12.11.2019: RC
> - 26.11.2019: Qt 5.14.0 Final Release
>
> And as earlier we will produce additional Beta n releases ~(bi)weekly 
between beta1 and RC.
>
> Any thoughts?

Only a consistency glitch: that puts FF 13 weeks before final release;
but [0] says we allow 17 weeks.  We should either update [0] or do what
it says !  For reference, 17 weeks before 2019-11-26 is 2019-08-30.

* [0] https://wiki.qt.io/Qt5Releasing

Eddy.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Go's "defer" statement for C++/Qt

[Andy Shaw]

I took the liberty of fixing this as I found something else in the doc that was 
wrong too so figured it was quicker to go and do it instead of mentioning it (

https://codereview.qt-project.org/255289

to avoid any duplicates of people doing it already.

Andy

-Opprinnelig melding-
Fra: Development  på vegne av Timur 
Pocheptsov 
Dato: fredag 8. mars 2019 06:49
Til: Jason H , Tor Arne Vestbø 
Kopi: "development@qt-project.org" 
Emne: Re: [Development] Go's "defer" statement for C++/Qt

Tor Arne +2! :D



From: Development [development-boun...@qt-project.org] on behalf of Jason H 
[jh...@gmx.com]
Sent: Thursday, March 7, 2019 11:59 PM
To: Tor Arne Vestbø
Cc: Qt development mailing list
Subject: Re: [Development] Go's "defer" statement for C++/Qt

The verbiage in the example is wrong:

 code_that_might_through_exceptions();

should be:

 code_that_might_throw_exceptions();

Took me a moment to figure out just what it meant.


> Sent: Thursday, March 07, 2019 at 12:09 PM
> From: "Tor Arne Vestbø" 
> To: "Volker Hilsheimer" 
> Cc: "Qt development mailing list" 
> Subject: Re: [Development] Go's "defer" statement for C++/Qt
>
> https://doc.qt.io/qt-5/qscopeguard.html 
>
> Tor Arne
>
> > On 7 Mar 2019, at 18:01, Volker Hilsheimer  
wrote:
> >
> > Ahoy,
> >
> > In what little development I’ve done in golang, I appreciated the 
“defer” statement as a means to write cleaner code. Basically, defer schedules 
a statement for execution when the stack unwinds.
> >
> > https://tour.golang.org/flowcontrol/12
> >
> > We have several specialized helper classes in Qt for similar purposes, 
f.ex QMutexLocker and friends, or the internal QBoolBlocker [1]. Seeing the 
various specialized classes we have, I thought that something generic in Qt 
could be useful to have (although our specialised classes provide some 
additional convenience and/or logic).
> >
> > So, I pushed a few lines code to
> >
> > https://git.qt.io/vohilshe/qt_defer
> >
> > Would like to hear what you think.
> >
> > Perhaps someone can find ways to make this more elegant without 
introducing tons of preprocessor/macro shenanigans, or perhaps even without 
depending on C++17's implicit template argument deduction (without enabling 
C++17 in the config this doesn't build for me, even though I don’t use auto in 
the template paramter list).
> >
> >
> > Cheers,
> > Volker
> >
> >
> > [1] which was requested to be made public in 
https://bugreports.qt.io/browse/QTBUG-38575
> >
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > https://lists.qt-project.org/listinfo/development
>
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
>
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] codereview, merge please

[Andy Shaw]

Since it has the +2 you can click on the "Merge patch 2 to staging" now, is 
that button showing up for you?

Andy

-Opprinnelig melding-
Fra: Development  på vegne av Martin Koller 

Dato: fredag 15. februar 2019 11:04
Til: "development@qt-project.org" 
Emne: [Development] codereview, merge please

Hi,

I made a patch here
https://codereview.qt-project.org/#/c/249171/

but it's still not merged.
Did I forget something ?

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

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

[Andy Shaw]

Unfortunately no (

Though if you want them to be addressed sooner, then at least providing the 
missing info for QTBUG-72687 would help in that case at least.

Andy

-Opprinnelig melding-
Fra: Development  på vegne av Aleksey 
Kontsevich 
Dato: mandag 7. januar 2019 09:23
Til: Jani Heikkinen , ekke , 
"developm...@lists.qt-project.org" 
Emne: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started

Very strange. May I move them to P0-Blocker then? :)

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


07.01.2019, 07:37, "Jani Heikkinen" :
>>  -Original Message-
>>  From: Development  On Behalf Of
>>  Aleksey Kontsevich
>>  Sent: lauantai 5. tammikuuta 2019 12.23
>>  To: ekke ; developm...@lists.qt-project.org
>>  Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1'
>>  started
>>
>>  Hi,
>>
>>  What about QTBUG-72687 and QTBUG-72227?
>
> QTBUG-72687 or QTBUG-72227 aren't really a release blocker, sorry.
>
> br,
> Jani
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Christian Ehrlicher for Approver

[Andy Shaw]

+1 from me, always happy to review his changes too!

Andy

Fra: Development  på vegne 
av Richard Gustavsen 
Dato: tirsdag 20. november 2018 09:38
Til: "development@qt-project.org" 
Emne: [Development] Nominating Christian Ehrlicher for Approver

Hi,

I'd like to nominate Christian Ehrlicher for approver rights.

He has done a lot of work in Qt, especially Widgets and Item Views, with more 
than 150 patches being merged during the last year.

He has also been equally active in Jira, verifying bug reports, identifying 
duplicates, etc.

His work:
https://codereview.qt-project.org/#/q/owner:%22Christian+Ehrlicher%22,n,z

His reviews:
https://codereview.qt-project.org/#/q/reviewer:%22Christian+Ehrlicher%22,n,z

Br,
Richard Moe Gustavsen

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Hardcoded strings and qstricmp comparison

[Andy Shaw]

Edward Welbourne  skrev følgende den 14.11.2018, 11:03:

Andy Shaw (14 November 2018 09:34) wrote:
> ... there may be some problems that are connected to using qstricmp
> and other functions that are expecting latin1 strings for one reason
> or another. The reason that this might be a problem is because we are
> encoding our source code as UTF-8 and there is a theoretical problem
> that due to this that we are not protecting the strings correctly to
> ensure that they are treated as latin1 when we explicitly write them
> internally. It could be that reality is that this will never be a
> problem, and if that is the case then please give me the background on
> that so I can pass this on too.
>
> For user code I get that we can just say that they should do something
> like:
>
>   qstricmp(str, QLatin1String("a").latin1());
>
> and that would be ensuring it is correctly seen as a latin1 encoded
> string. If this is how it should be done, then shouldn’t we change our
> usage of it in the Qt code as well to do the same thing? Or am I
> missing something?

Well, as long as the source string is actually printable ASCII, there
should be no problem, as UTF-8 and Latin-1 agree on those.

If the source string contains bytes > 127, such bytes should be encoded
using suitable escapes; if the string is to be read as Latin-1 and the
source file is encoded in UTF-8, the raw form of the bytes would not be
displayed as the character it would actually be read as.

So I'm not quite sure what problem you're referring to, but if a string
in the source is meant to be Latin-1, it shouldn't be entered in literal
form in the source code, it should be entered using escapes,

  QLatin1Char yUmlaut('\xff');

for example.


I am speaking purely theoretically, there may not be a problem, I don't know 
enough to be sure that’s why I am asking ( Though I think this clarifies enough 
for me, as long as we are using characters <= 127 in ASCII then there is no 
problem on our side. And the user has to just be aware of it themselves when 
they are using these functions to remember that their source code will be UTF-8 
encoded and not Latin1 and thus should escape characters > 127.

Andy


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Hardcoded strings and qstricmp comparison

[Andy Shaw]

Hi!

In connection to a support case I have been working on it was brought to my 
attention that there may be some problems that are connected to using qstricmp 
and other functions that are expecting latin1 strings for one reason or 
another. The reason that this might be a problem is because we are encoding our 
source code as UTF-8 and there is a theoretical problem that due to this that 
we are not protecting the strings correctly to ensure that they are treated as 
latin1 when we explicitly write them internally. It could be that reality is 
that this will never be a problem, and if that is the case then please give me 
the background on that so I can pass this on too.

For user code I get that we can just say that they should do something like:

  qstricmp(str, QLatin1String("a").latin1());

and that would be ensuring it is correctly seen as a latin1 encoded string. If 
this is how it should be done, then shouldn’t we change our usage of it in the 
Qt code as well to do the same thing? Or am I missing something?

Kind Regards,
Andy
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt Champions 2018 nominations open

[Andy Shaw]

Hi!

We have now opened the nominations for Qt Champions in 2018!

As before, please think about who has helped you out the most during the past 
year and nominate them via the Qt wiki at https://wiki.qt.io/QtChampions.

The categories are:

Community Builder
Content Creator
Quality Assurer
Developer
Fixer
Ambassador
Rookie of the Year
Maverick

The criteria for the nominations can be found on the same page. If there is 
anyone who should be in several categories, or has done something that does not 
fit in any of the categories. then please mention this too!

The nominations will be kept open until the 16th December 2018 and the winners 
announced soon after that. Qt Champions will receive hand-picked Qt Champion 
items and a full Qt license for a year.

So please go to https://wiki.qt.io/QtChampions and make your nominations!

Kind regards,
Andy
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Who is in charge of qt-project.org?

[Andy Shaw]

It is there, but you have to go to http://lists.qt-project.org for now, it is 
being moved to a new server so at some point the https address will be back, 
but until then you need to use the http address.

Andy 

Development på vegne av Christian Gagneraud 
 skrev følgende den 31.10.2018, 14:36:

Hi,

Can we have Qt mailing list archive back?
I believe it is tracked by
https://bugreports.qt.io/browse/QTWEBSITE-831 and as been going on for
weeks. Can the "Qt Project Hosting Foundation" (from whois record)
take care of that?
What is going on?

Chris
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HTTPS on lists.qt-project.org was Re: Build system for Qt 6

[Andy Shaw]

Just as a FYI, I have reported this on internally so hopefully this will get 
fixed shortly.

Andy

Development på vegne av Thiago Macieira 
 skrev følgende den 30.10.2018, 17:22:

On Tuesday, 30 October 2018 02:26:33 PDT Christian Gagneraud wrote:
> https://lists.qt-project.org/mailman/listinfo/qbs gives me:
> Secure Connection Failed

The lists.qt-project.org HTTPS server is misconfigured (has been for a week 
or 
so) and is replying with non-encrypted HTTP on port 443.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Proposing Albert Astals Cid for Approver

[Andy Shaw]

A +1 from me too, his help with the printing side has been really valuable!

Andy

Development på vegne av Frederik Gladhorn 
 skrev følgende den 21.03.2018, 16.27:

A big +1 from me as well :)

Cheers,
Frederik


On onsdag 21. mars 2018 12.33.06 CET Sérgio Martins wrote:
> Hi,
> 
> 
> Albert has been a long time contributor to KDE and Qt and very well
> known in the community.
> 
> His dashboards speak for himself, with many bugs fixed:
> (For some reason pasting-and-opening URLs from gerrit is broken, so
> you'll have to search yourself)
> 
> 
> at KDAB:
> owner:"Albert Astals Cid "
> 
> 
> at Canonical:
> owner:albert.ast...@canonical.com
> 
> 
> on his free-time with KDE hat:
> owner:"Albert Astals Cid "
> 
> 
> 
> And recently he was tricked into fixing many printing and CUPS bugs, so
> thanks Albert!
> 
> 
> Disclaimer: He's a collegue of mine at KDAB, knew him from KDE and lives
> somewhat near me, in the Iberian peninsula.
> 
> 
> 
> Regards,


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Valentyn Doroshchuk for Approver status

[Andy Shaw]

+1 from me too.


Andy


Fra: Development  på vegne 
av Timur Pocheptsov 
Sendt: 20. mars 2018 15:14:05
Til: André Hartmann; Laszlo Agocs; development@qt-project.org
Emne: Re: [Development] Nominating Valentyn Doroshchuk for Approver status


+1 from me.


Best regards,

Timur.


From: Development  
on behalf of André Hartmann 
Sent: Tuesday, March 20, 2018 3:02:11 PM
To: Laszlo Agocs; development@qt-project.org
Subject: Re: [Development] Nominating Valentyn Doroshchuk for Approver status

+1 from my side also :)

André

Am 20.03.2018 um 14:29 schrieb Laszlo Agocs:
> +1 from me as well.
>
> Cheers,
> Laszlo
>
> -Original Message-
> From: Development  On 
> Behalf Of Shawn Rutledge
> Sent: tirsdag 20. mars 2018 14.28
> To: development@qt-project.org
> Subject: Re: [Development] Nominating Valentyn Doroshchuk for Approver status
>
> +1 from me
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 5.11

[Andy Shaw]

I have had some people upgrading to 1.1 and asking us why it doesn’t work, so 
we have told them to downgrade explaining why. I think it is the right thing to 
do with the upgrade to 1.1, but I just want to try and prevent people 
overwriting their existing version if they are using older versions of Qt still 
so it doesn’t get in the way of that. They just need to make sure they install 
OpenSSL 1.1 to a different location then.

Andy

Fra: Timur Pocheptsov <timur.pochept...@qt.io>
Dato: fredag 9. februar 2018 09.42
Til: Andy Shaw <andy.s...@qt.io>, Moore Richard <r...@kde.org>, 
"development@qt-project.org" <development@qt-project.org>
Emne: Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 
5.11


Andy, do you have any feedback from our customers about this? My anecdotal 
evidence so far - I have 0 bug-reports complaining they see a message: 
"Incompatible version of OpenSSL" (qsslsocket_openssl_symbols.cpp, line 1025), 
this means for me people using our binaries mostly have OpenSSL version below 
1.1.



Best regards,

Timur.


From: Development <development-bounces+timur.pocheptsov=qt...@qt-project.org> 
on behalf of Andy Shaw <andy.s...@qt.io>
Sent: Friday, February 9, 2018 7:44:01 AM
To: Richard Moore; development@qt-project.org
Subject: Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in 
Qt 5.11


+ 1 from me too.



Is it clear enough from the docs for 5.9  and 5.10 that it does not support 
OpenSSL 1.1? In case someone still uses that and ends  up replacing their 
existing installation of OpenSSL without realizing.



Andy



Fra: Development <development-bounces+andy.shaw=qt...@qt-project.org> på vegne 
av Moore Richard <r...@kde.org>
Dato: torsdag 8. februar 2018 21.48
Til: "development@qt-project.org" <development@qt-project.org>
Emne: Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 
5.11







On 8 February 2018 at 18:45, Thiago Macieira 
<thiago.macie...@intel.com<mailto:thiago.macie...@intel.com>> wrote:

As $SUBJECT says.

Only for 5.11 onward, so shouldn't affect the 5.6 and 5.9 LTS (which don't
have OpenSSL 1.1 support anyway) or any 5.10.x releases still to come.

As a bonus side-effect, users who hadn't realised they have an old, not-up-to-
date OpenSSL will have to fix the issue.





​

+1 those who need to use an older version will still be able to build their 
own. We really need to start actively pushing people to 1.1.



Cheers



Rich.


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 5.11

[Andy Shaw]

+ 1 from me too.

Is it clear enough from the docs for 5.9  and 5.10 that it does not support 
OpenSSL 1.1? In case someone still uses that and ends  up replacing their 
existing installation of OpenSSL without realizing.

Andy

Fra: Development  på vegne 
av Moore Richard 
Dato: torsdag 8. februar 2018 21.48
Til: "development@qt-project.org" 
Emne: Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 
5.11



On 8 February 2018 at 18:45, Thiago Macieira 
> wrote:
As $SUBJECT says.

Only for 5.11 onward, so shouldn't affect the 5.6 and 5.9 LTS (which don't
have OpenSSL 1.1 support anyway) or any 5.10.x releases still to come.

As a bonus side-effect, users who hadn't realised they have an old, not-up-to-
date OpenSSL will have to fix the issue.


​
+1 those who need to use an older version will still be able to build their 
own. We really need to start actively pushing people to 1.1.

Cheers

Rich.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Nominating Joni Poikelin for Approver status

[Andy Shaw]

Hi,

I would like to nominate Joni Poikelin for Approver status. He joined The Qt 
Company over 3 years ago and has consistently contributed to Qt across many 
modules, fixing a number of issues here and there. His Gerrit dashboard is here:

https://codereview.qt-project.org/#/q/owner:%22Joni+Poikelin+%253Cjoni.poikelin%2540qt.io%253E%22+status:merged,n,z

Disclaimer: We both work in the same team (support) inside The Qt Company.

Andy


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QT printing via CUPS (advanced printing dalog box missing)

[Andy Shaw]

I have been doing some work on the printing side of things lately, since this 
is quite a well voted for feature I’ll try and find time to investigate this 
further (assuming no one else beats me to it) over the next week or so.

Andy

Development på vegne av Thiago Macieira 
 skrev følgende den 20.11.2017, 23.45:

On segunda-feira, 20 de novembro de 2017 14:01:25 PST GMAIL wrote:
> This bug has been reported on QT ( see
> https://bugreports.qt.io/browse/QTBUG-54464) on *June 2016*. Almost a
> year and half now, the bug status is still *reported* and the resolution
> *unknown*.
> 
> I am sorry to post this information here, but we are many users affected
> by this bug and we are desperate because we don't have any feed back
> from QT. Is there anybody working on it ?

No, there is not.

The module is currently orphan, with no maintainer.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Speeding up the review process (was: PostgreSQL cross compile for Pi)

[Andy Shaw]

To make it clear, it is Viktor’s opinion here and he can state it but it does 
not mean that it is the representation of all of The Qt Company here. It was 
one point of a larger mail which he took the time to write because he wants to 
open a discussion about how we can improve the review process as a community. 
Ideas are naturally welcome and not all of them are going to be agreeable to 
everyone, and not all of them are going to be accepted moving forward either.

I personally don’t agree with the specific point made regarding where the 
contribution has come from as I believe that everyone should be treated equally 
when it comes to reviewing, just because you are or have been an employee of 
The Qt Company should not grant you any extra lenience when it comes to 
reviewing. As Eddie has already mentioned for his own sake, I also appreciate 
the feedback and the fact that someone is critically looking at my change. I 
may have been working with Qt for 17 years, but I still learn and I still make 
mistakes, my changes should be reviewed in exactly the same manner as anyone 
elses should be. I expect that and prefer it too.

Andy

Fra: Development  på vegne 
av Alexander Nassian 
Dato: fredag 13. oktober 2017 14.51
Til: Somers Andre 
Kopi: "development@qt-project.org" 
Emne: Re: [Development] Speeding up the review process (was: PostgreSQL cross 
compile for Pi)

That shows exactly the mindset of the TQC administration. Let the community do 
the work and squeeze all customers and force them to use commercial licensing 
by using fear...


Beste Grüße / Best regards,
Alexander Nassian


Am 13.10.2017 um 14:46 schrieb André Somers 
>:



Op 13/10/2017 om 13:04 schreef Viktor Engelmann:
4. I don't think we need to be as paranoid towards contributions from our own 
employees as we need to be towards external contributions.

So much for open government...

André
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development




—

bitshift dynamics GmbH
Neudorfer Str. 1, 79541 Lörrach
Registergericht: Amtsgericht Freiburg i. Breisgau, HRB 713747
Geschäftsführer: Alexander Nassian, Markus Pfaffinger

http://www.bitshift-dynamics.de

Zentrale: +49 762158673 - 0
Fax: +49 7621 58673 - 90

Allgemeine Anfragen: 
i...@bitshift-dynamics.com
Technischer Support: 
supp...@bitshift-dynamics.com
Buchhaltung: invo...@bitshift-dynamics.com
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Reviewers needed for a couple of Qt SQL patches

[Andy Shaw]

Hi,

Lately it seems the maintainer for Qt SQL has not been reviewing patches, I 
don’t know if anyone knows anymore on that, but I have a few I would like to 
get reviewed. I’ve been asking around to see if anyone is willing to review the 
patches I have but so far have had no joy. They are related to the Oracle 
plugin which does not get tested at all in CI due to a lack of means to do so.

The first two are test related and don’t change anything in the actual module, 
but makes sure the tests are correct:

https://codereview.qt-project.org/#/c/180603/
https://codereview.qt-project.org/#/c/180620/

A bug fix for a problem with the Oracle plugin here:

https://codereview.qt-project.org/#/c/205032/

and the last one:

https://codereview.qt-project.org/#/c/204639/

implements a missing feature for the Oracle plugin too. So if anyone is willing 
then please feel free!

Thanks!
Andy

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt and IoT infographic

[Andy Shaw]

If we have a Qt 6 dance will it be backported to Qt 5? ;)

Andy

Development på vegne av Thiago Macieira 
 skrev følgende den 25.08.2017, 08.20:

On Thursday, 24 August 2017 23:10:45 PDT Lorn Potter wrote:
> On 08/25/2017 02:08 PM, Thiago Macieira wrote:
> > [ "First there was Linux / and then there was Mac / now with Windows /
> > on the Open Source track"  anyone?]
> 
> ahh yes. The all time dance mega hit: Qt 4 Dance!
> 
> https://www.youtube.com/watch?v=NbTEVbQLC8s

Someone asked me today if there'll be a discussion about the Qt 6 dance at 
the 
Contributor Summit.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Katja Marttila for Approver status

[Andy Shaw]

Since it has been long past the 15 working days needed for this and no one 
objected, assuming it hasn’t already been done can someone fix the rights for 
Katja?

Andy

Andy Shaw <andy.s...@qt.io> skrev følgende den 05.04.2017, 10.08:

+1 from me.

Andy

Development på vegne av Samuli Piippo 
<development-bounces+andy.shaw=qt...@qt-project.org på vegne av 
samuli.pii...@qt.io> skrev følgende den 05.04.2017, 09.07:

Hi,

I'd like to nominate Katja Marttila for Approver status.
Katja has been working among other things as the maintainer for Qt 
Installer Framework for a while now.

Her gerrit dashboard:


https://codereview.qt-project.org/#/q/owner:%22Katja+Marttila%22+status:+merged,n,z


-samuli
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development




___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Clarification needed on a crash caused by ignoring ownership of an object

[Andy Shaw]

Thanks Marc, that covers what I needed to know to make a decision ☺

Andy

Development på vegne av Marc Mutz 
<development-bounces+andy.shaw=qt...@qt-project.org på vegne av 
marc.m...@kdab.com> skrev følgende den 04.05.2017, 10.08:

On Thursday 04 May 2017 09:58:45 Andy Shaw wrote:
> Hi,
> 
> I am trying to determine what we should be doing inside Qt in a certain
> case. When a QUndoCommand is deleted after it has been given another
> QUndoCommand as a parent it will cause a crash since the parent has not
> been informed that the child was deleted. The documentation for
> QUndoCommand is explicit on the fact that when it has a parent the
> ownership of the QUndoCommand is transferred to its parent. As such I
> would not expect it to be possible to delete the child directly anymore as
> a result as we no longer own it.
> 
> So the question is, since it is still a crash, should we still be
> accounting for this in the Qt code so as to prevent the crash or is it a
> case of it is documented to transfer ownership and as such we don’t want
> to protect against it being deleted out of Qt’s hands?

Seeing as about half of the ubsan reports are about shutdown sequences of 
object hierarchies which allow parent-owned children to be deleted by the 
user, I'm tempted to say: add an assert (set a flag when the parent deletes 
a 
child, check that the flag is set in the child's dtor).

OTOH, QObject parent-child relationships, and QTreeWidgetItems set a strong 
precedent.

I'd decide based on how much complexity this adds to the implementation, 
but 
if you prepare a patch, the pressure to merge it is going to be a great 
one. 
The work is already done, after all. So, please decide yourself. You have 
my 
blessing to close as WONTFIX, or else enable the new use-case if it's not 
too 
complex (a very subjective criterion, I agree).

Thanks,
Marc

-- 
Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Clarification needed on a crash caused by ignoring ownership of an object

[Andy Shaw]

Hi,

I am trying to determine what we should be doing inside Qt in a certain case. 
When a QUndoCommand is deleted after it has been given another QUndoCommand as 
a parent it will cause a crash since the parent has not been informed that the 
child was deleted. The documentation for QUndoCommand is explicit on the fact 
that when it has a parent the ownership of the QUndoCommand is transferred to 
its parent. As such I would not expect it to be possible to delete the child 
directly anymore as a result as we no longer own it. 

So the question is, since it is still a crash, should we still be accounting 
for this in the Qt code so as to prevent the crash or is it a case of it is 
documented to transfer ownership and as such we don’t want to protect against 
it being deleted out of Qt’s hands?

Andy

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Katja Marttila for Approver status

[Andy Shaw]

+1 from me.

Andy

Development på vegne av Samuli Piippo 
 skrev følgende den 05.04.2017, 09.07:

Hi,

I'd like to nominate Katja Marttila for Approver status.
Katja has been working among other things as the maintainer for Qt 
Installer Framework for a while now.

Her gerrit dashboard:


https://codereview.qt-project.org/#/q/owner:%22Katja+Marttila%22+status:+merged,n,z


-samuli
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Should the system proxies default setting be switched to true?

[Andy Shaw]

Since there does not seem to be any general objections, I have submitted a 
patch for this - https://codereview.qt-project.org/159120 - this is for 5.8. If 
anyone does see an issue then please say so in the comments, I will give it a 
bit of time before merging once it gets its +2 in order to give it a chance to 
be tried out in case someone hits a problem.

Andy

Fra: Simon Hausmann
Sendt: 12. mai 2016 10:01:35
Til: Andy Shaw; Kai Koehne; development@qt-project.org
Emne: Re: [Development] Should the system proxies default setting be switched   
to true?

Right, it begs the question: If a third-party application like Chrome can use 
system proxy settings by default, why can't or don't we? :)


Simon

From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> on 
behalf of Andy Shaw <andy.s...@qt.io>
Sent: Thursday, May 12, 2016 9:54:41 AM
To: Kai Koehne; development@qt-project.org
Subject: Re: [Development] Should the system proxies default setting be 
switchedto true?

There is an issue but this comes from the Windows side and is also documented 
by Microsoft as being a problem I believe on their side. But this should only 
be experienced the first time it needs to do this though, whereas before it 
would do this all the time. However, I would personally expect that if this is 
happening for a user, it will not be happening for just Qt either.

Andy

Fra: Kai Koehne
Sendt: 12. mai 2016 08:41:21
Til: Andy Shaw; development@qt-project.org
Emne: RE: [Development] Should the system proxies default setting be switched   
to true?

+1 for switching to using the system proxy settings by default.

I'm still a bit wary about the 'Windows issue' though. To cite our 
documentation [1]:

  "On Windows platforms, this function may take several seconds to execute 
depending on the configuration of the user's system."

Was that the problem with Windows versions configured for automatically 
querying for PAC files, but never getting any response?

Regards

Kai

[1]: http://doc.qt.io/qt-5/qnetworkproxyfactory.html#systemProxyForQuery

> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Andy Shaw
> Sent: Wednesday, May 11, 2016 3:51 PM
> To: development@qt-project.org
> Subject: [Development] Should the system proxies default setting be
> switched to true?
>
> For some time now we have had the means to configure Qt to use system
> proxies so that they are on by default or to turn it on via
> QNetworkProxyFactory. However, this is off by default so it is becoming a
> reoccurrence that people don't realise that it is not using the system proxies
> until later on. Potentially not until after a product has been released.
>
>
> The reasoning that this was not done before was due to the fact that there
> was a problem on Windows with it taking too long in some cases to get the
> information. However this seems to be solved for the most part and
> expected in some cases due to the fact that it is down to the system, but it 
> is
> just an initial start up check in this case.
>
>
> That said, does anyone see any problems with switching it so that we can
> now have it turned on by default from Qt 5.8? Naturally the configure option
> would stay so people can still turn it off if they wish.
>
>
> For reference the original thread about this can be found:
>
>
>   http://lists.qt-project.org/pipermail/development/2012-
> October/007037.html
>
>
> Andy
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Should the system proxies default setting be switched to true?

[Andy Shaw]

There is an issue but this comes from the Windows side and is also documented 
by Microsoft as being a problem I believe on their side. But this should only 
be experienced the first time it needs to do this though, whereas before it 
would do this all the time. However, I would personally expect that if this is 
happening for a user, it will not be happening for just Qt either.

Andy

Fra: Kai Koehne
Sendt: 12. mai 2016 08:41:21
Til: Andy Shaw; development@qt-project.org
Emne: RE: [Development] Should the system proxies default setting be switched   
to true?

+1 for switching to using the system proxy settings by default.

I'm still a bit wary about the 'Windows issue' though. To cite our 
documentation [1]:

  "On Windows platforms, this function may take several seconds to execute 
depending on the configuration of the user's system."

Was that the problem with Windows versions configured for automatically 
querying for PAC files, but never getting any response?

Regards

Kai

[1]: http://doc.qt.io/qt-5/qnetworkproxyfactory.html#systemProxyForQuery

> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Andy Shaw
> Sent: Wednesday, May 11, 2016 3:51 PM
> To: development@qt-project.org
> Subject: [Development] Should the system proxies default setting be
> switched to true?
>
> For some time now we have had the means to configure Qt to use system
> proxies so that they are on by default or to turn it on via
> QNetworkProxyFactory. However, this is off by default so it is becoming a
> reoccurrence that people don't realise that it is not using the system proxies
> until later on. Potentially not until after a product has been released.
>
>
> The reasoning that this was not done before was due to the fact that there
> was a problem on Windows with it taking too long in some cases to get the
> information. However this seems to be solved for the most part and
> expected in some cases due to the fact that it is down to the system, but it 
> is
> just an initial start up check in this case.
>
>
> That said, does anyone see any problems with switching it so that we can
> now have it turned on by default from Qt 5.8? Naturally the configure option
> would stay so people can still turn it off if they wish.
>
>
> For reference the original thread about this can be found:
>
>
>   http://lists.qt-project.org/pipermail/development/2012-
> October/007037.html
>
>
> Andy
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Should the system proxies default setting be switched to true?

[Andy Shaw]

For some time now we have had the means to configure Qt to use system proxies 
so that they are on by default or to turn it on via QNetworkProxyFactory. 
However, this is off by default so it is becoming a reoccurrence that people 
don't realise that it is not using the system proxies until later on. 
Potentially not until after a product has been released.


The reasoning that this was not done before was due to the fact that there was 
a problem on Windows with it taking too long in some cases to get the 
information. However this seems to be solved for the most part and expected in 
some cases due to the fact that it is down to the system, but it is just an 
initial start up check in this case.


That said, does anyone see any problems with switching it so that we can now 
have it turned on by default from Qt 5.8? Naturally the configure option would 
stay so people can still turn it off if they wish.


For reference the original thread about this can be found:


  http://lists.qt-project.org/pipermail/development/2012-October/007037.html


Andy
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Maintainers for Qt Charts and Data Visualization

[Andy Shaw]

+1 from me too, I have worked with them on it internally too so can verify that.

Andy

Fra: Development  på vegne 
av Pasi Keränen 
Sendt: 10. mai 2016 07:57:31
Til: Lars Knoll; Qt development mailing list
Emne: Re: [Development] Maintainers for Qt Charts and Data Visualization

Absolute, definite +1 for this! It’s long overdue :)

Cheers,
Pasi




On 09/05/16 14:22, "Development on behalf of Lars Knoll" 
 wrote:

>Hi,
>
>Since we now open sourced Charts and Data Visualisation for Qt 5.7, the 
>modules also need a Maintainer. I'd like to propose the two people that have 
>been maintaining these modules while they were developed inside TQtC to 
>continue in this role: Miikka Heikkinen for Charts, and Tomi Korpipää for Data 
>Visualisation.
>
>Cheers,
>Lars
>
>
>___
>Development mailing list
>Development@qt-project.org
>http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development