Re: [Development] Jira action buttons

[Alexander Blasche]

> -Original Message-
> From: Mitch Curtis

> I'm noticing this for bugs too (QTBUG-57965). Do you have a report for 
> tracking
> this issue, or do you know when it will be fixed?

Done.

I am fixing as soon as somebody points them out to me. There is no easy way to 
identify them 

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

Re: [Development] Jira action buttons

[Alexander Blasche]

Hi,

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Samuel Gaist
> Sent: Sunday, 8 January 2017 23:44

> Is there any rule/filter that are applied on the bug reports related to the 
> actions
> made available ?
> 
> For example:
> 
> https://bugreports.qt.io/browse/QTBUG-57991: I have  Edit, Comment, Assign,
> More
> 
> https://bugreports.qt.io/browse/QTBUG-57996 : Same as above plus Not
> enough info, Accept, Close
> 
> I wanted to close https://bugreports.qt.io/browse/QTBUG-57993 as a duplicate
> of https://bugreports.qt.io/browse/QTBUG-57992 but I can’t do it currently
> because for both of them I only get the reduced set of buttons.

This is a bug. Nobody had any state transition options for this task. Jira ran 
out of disk space last week. Maybe this has caused the problem. In any case, I 
have recovered the work flow state and marked QTBUG-57993 as duplicate of 
QTBUG-57992.

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

Re: [Development] Nominating Konstantin Tokarev for Approver status

[Alexander Blasche]

Congratulations to Konstantin. Your rights have been adjusted.

--
Alex




From: Development  
on behalf of Allan Sandfeld Jensen 
Sent: Monday, 5 December 2016 1:23:45 PM
To: development@qt-project.org
Subject: [Development] Nominating Konstantin Tokarev for Approver status

Hi all,

I just noticed Konstantin Tokarev who has been doing most of the development,
and practical maintenance of QtWebKit after it moved into "removed" state is
still missing reviewer status. I suggest we correct this.

Besides his work in the official qtwebkit branch, he also doing the QtWebKit-
NG project trying to make a new updated QtWebKit module with a recent upstream
WebKit.

Here are his recent merged commits:
https://codereview.qt-project.org/#/q/owner:"Konstantin+Tokarev"+status:merged,n,z

And reviews:
https://codereview.qt-project.org/#/q/reviewer:"Konstantin+Tokarev",n,z

Best regards
`Allan
___
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] Q_COMPILER_VARIADIC_TEMPLATES since Qt 5.7

[Alexander Blasche]

From: Development  
on behalf of Thiago Macieira 

>QOverload could be used, but I'd rather you didn't use it in the Qt sources.
>It's a bit ugly.

Currently not all Qt compilers work with it which makes it a no go for Qt 
itself. I had to remove it again:

https://bugreports.qt.io/browse/QTBUG-55747

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

Re: [Development] Proposal to adjust release candidate process

[Alexander Blasche]

Hi,

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: Tuesday, 20 December 2016 16:14
 
> I wonder how much of the current pressure on releases is driven by the time-
> based release policy. We aim for a new minor release every 6 months which is
> admirable. But I wonder about the consequences of trying to stick to that at 
> the
> expense of quality of the 5.x.0 releases, especially given the long turn 
> around for
> subsequent patch releases.
...
 > * Do not rush the release at the expense of quality or when it's convenient 
 > due
> to packagers going on vacation etc. We release only when the release is
> deemed to meet quality standards.

Tuukka kind of made this point already but I'd like to make it more succinct.

We do not want to change the time or the quality constraint. We want to adjust 
the feature constraint. This means that you and I as maintainers very much have 
it in our hands to manage the release pressure. You have to fight your own 
weaker self and accept that you may not keep the quality up with your feature 
plans for the module you maintain.

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

Re: [Development] Nominating Teemu Holappa for Approver and Maintainer status.

[Alexander Blasche]

Congratulations to Teemu. His rights have been adjusted.

--
Alex


From: Development  
on behalf of Gatis Paeglis 
Sent: Thursday, 24 November 2016 2:00:32 PM
To: development@qt-project.org
Subject: [Development] Nominating Teemu Holappa for Approver and Maintainer 
status.

Hi,

I'd like to nominate Teemu Holappa for the Approver status. He joined Digia 
(now The Qt Company) 3+ years ago as a Qt consultant. Teemu has contributed to 
meta-boot2qt and anything else that needs fixing to get Qt for Device Creation 
releases out the door.

Here is his gerrit dashboard:

https://codereview.qt-project.org/#/q/owner:%22Teemu+Holappa+%253Cteemu.holappa%2540qt.io%253E%22+status:merged,n,z

Teemu also has done a good job at reviewing changes for meta-{boot2qt, qt5, 
mingw} among other projects:

https://codereview.qt-project.org/#/q/reviewer:%22Teemu+Holappa+%253Cteemu.holappa%2540qt.io%253E%22+status:merged,n,z

I'd also like to nominate him as the Maintainer of the qtdeviceutilities module 
(http://code.qt.io/cgit/qt/qtdeviceutilities.git/). Teemu has heavily 
refactored this module and added significant amount of new features. He is the 
go-to guy in the team when qtdeviceutilities is the topic.


Gatis Paeglis.

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

Re: [Development] Nominating Antti Määttä as Qt3D approver

[Alexander Blasche]

Congratulations to Antti Määttä. Approver rights have been set.

--
Alex


From: Development  
on behalf of Pasi Keränen 
Sent: Tuesday, 15 November 2016 6:16:06 AM
To: Sean Harmer; development@qt-project.org
Subject: Re: [Development]  Nominating Antti Määttä as Qt3D approver

+1 from me as well.

Regards,
Pasi

On 14/11/16 17:19, "Development on behalf of Sean Harmer" 
 wrote:

On Monday 14 November 2016 15:15:16 Paul Lemire wrote:
> Hi
>
> I would like to propose the nomination of Antti Määttä for approver 
status.
> Antti has been contributing many patches to Qt3D adding new features and
> providing bug fixes. In addition, having another approver would be a great
> help to reduce the amount of time patches are spent awaiting a review.

+1 from me.

Cheers,

Sean

___
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] Qt 5.9

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Jake Petroules

> > That's why I still think we should proceed as I proposed: Keep online 
> > offering
> as it is but drop separate macos + android offline installer (have macOS and
> macOS + mobile targets for macOS offline offering). Decreasing our offline
> installer offering is essential; needed testing effort at the moment is 
> really huge
> & it is increasing all the time because of these parallel releases. That's 
> why we
> need to decrease stuff to be tested to make our live easier.
> 
> So don't test them. I'm not joking. There should be no reason to test every
> possible combination; just test each platform through the online installer and
> that should implicitly test that the offline one works.

Sorry but that's not going to fly.

> Our process shouldn't be so flimsy and untrustworthy that we're testing every
> possible combination. Let the community do it, and if there's a problem, we'll
> surely know soon enough.

Software is a living and breathing thing. Its nature is such that it evolves 
changes each time. Not testing is not an option. We could have more confidence 
if history wouldn't proof us constantly wrong. Jake, even you had your fair 
share of breaks during release time. Stop breaking other platforms with your 
iOS changes and we can talk again ;)

You can use the online installer if you want only one mobile platform but not 
the other. Sure there is more MBs to download with offline but the releasing 
and testing effort is an even greater concern.

Dropping 32bit once Apple says so is a much more rewarding and likely 
opportunity.

> One solution could be that we start using online ones at first & bring 
> offline ones
> later. Earlier we have released beta with offline only so should we do this
> differently with Qt 5.9:
> >
> > Qt 5.9 alpha: src only
> > Qt 5.9 beta: online only

I am against this. Online installers are much harder to handle when you have to 
continuously install competing Qt versions. Testing requires to install 4 
different builds of Qt during for example beta time. Both types of builds have 
their advantage and testing/trialing is not one where the online installer 
shines.

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

Re: [Development] Qt 5.9

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Thiago
> Macieira
> Sent: Tuesday, 29 November 2016 21:05
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.9
> 
> On terça-feira, 29 de novembro de 2016 18:49:51 PST Roland Winklmeier wrote:
> > > On 28 Nov 2016, at 16:40, Alexander Blasche
> > > <alexander.blas...@qt.io>
> > > wrote:
> > >
> > > Ok, let's summarize and restate the package list for Qt 5.9 based on
> > > the comments provided on this mail thread. The list describes the
> > > delta to Qt
> > > 5.8 packages:
> > >
> > > * MinGW remains 5.3 using 32 bit
> >
> > Since I'm using MinGW binaries in 32 bit and 64 bit mode (as plugins
> > for flight simulator applications which exist in 32 and 64 bit), I
> > would be very happy to have both as official MinGW installers.
> > Especially since the MinGW debug binaries are huge compared to the
> > MSVC ones. So I tend to use
> > 64 bit ones (up to now self compiled from source) whenever possible.
> > Would it be an option to add the MinGW 64 bit installer and keep the 32 bit
> one?
> 
> Agreed with Roland. I thought one of the major conclusions from this thread is
> that we would provide 64-bit MinGW with Qt 5.9. I don't see that in Alex's
> conclusion email.

The big problem is that there are still plenty of 32bit users because they 
truly use 32bit platforms or 3rdparty software forces them to do so. Moving to 
64 bit excludes users without alternatives. 32 bit does not exclude. Yes, I 
know this is a chicken and egg problem but right now we have reduced the 32bit 
package count for 5.9 already. Let's not rush too much.

> > 64 bit ones (up to now self compiled from source) whenever possible.
Mind you, Roland himself stated the continued need for 32 bit.

> > Would it be an option to add the MinGW 64 bit installer and keep the 32 bit
> one?

There are already 11 windows binary types/packages in the current setup and 
that's too many. I see some opportunity when 2013 drops out in the future.

--
Alex

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

Re: [Development] Qt 5.9

[Alexander Blasche]

Ok, let's summarize and restate the package list for Qt 5.9 based on the 
comments provided on this mail thread. The list describes the delta to Qt 5.8 
packages:

* For macOS we drop 10.9 and support 10.10, 10.11 & 10.12
* For iOS we drop 7.x and support 8.x, 9.x, 10.x
* MinGW remains 5.3 using 32 bit
* Add MSVC 2017 64bit desktop
* Add MSVC 2017 UWP (x64, x86, armv7)
* Drop MSVC 2013 x86
* Drop MSVC 2013 for WinRT/WinPhone & MSVC 2013 for WinRT 8.1 and WinPhone 8.1 
* Drop standalone macOS Android installer; One having iOS & Android
* For Windows Android start doing Android Windows build with MinGW53
* Start supporting QNX 7.0

--
Alex

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

Re: [Development] Whoever is responsible for QtGamepad

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Thiago
> Macieira

> Please have a component created for you in JIRA and take ownership of
> https://bugreports.qt.io/browse/QTBUG-57338

Done and assigned to Andy.

I also took the liberty of updating https://wiki.qt.io/Maintainers.
 --
Alex
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.9

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Thiago
> Macieira
> I know the sample size here is horrible, but in your opinion what compiler 
> should
> we keep offering a 32-bit binary build for?
> 
> MSVC 2013
> MSVC 2015
> MinGW

I can offer one more pointer for this question. Looking at our Visual Studio 
Addon 2.0 release:

MSVC2013 
https://marketplace.visualstudio.com/items?itemName=TheQtCompany.QtVisualStudioTools
MSVC2015 
https://marketplace.visualstudio.com/items?itemName=TheQtCompany.QtVisualStudioTools2015

We can see a strong preference for MSVC2015 in the download figures (370 vs 
1620 as of just now).
MSVC2015 32bit would live much longer as a supported compiler option for the Qt 
project as well.

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

Re: [Development] Qt 5.9

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Alexander
> Blasche
 
> I don't think we can drop all 32bit support. I do believe MSVC 2017 should be
> part of the deal though. That's a good suggestion. Keeping these two options 
> in
> mind, I suggest to drop MSVC 2013 32 bit against MSVC 2017 64bit. This keeps
> the number of packages the same.

To make it more obvious here is my suggestion:

5.9:
32-bit  64-bit
MSVC 2013  N   Y
MSVC 2015  Y   Y
MSVC 2017  N   Y
MinGW N       Y

--
[Alexander Blasche] Alex
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.9

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Thiago
> Macieira



> Good point. Considering that MSVC 2017 is coming (RC is already out), I'd also
> be prepared to have it available for 5.9, so I propose:
> 
> 5.7 (for comparison, no  change):
> 32-bit  64-bit
> MSVC 2013  Y   Y
> MSVC 2015  Y   Y
> MSVC 2017  N   N
> MinGW  Y   N
> (5 packages)
> 
> 5.8:
> 32-bit  64-bit
> MSVC 2013  Y   Y
> MSVC 2015  N   Y
I am not aware that we are dropping 2015 32bit support in 5.8. I thought the 
platform/compiler definition for 5.8 was set in stone a long time ago.

> MSVC 2017  N   N
> MinGW  Y   Y
> (5 packages)
> 
> 5.9:
> 32-bit  64-bit
> MSVC 2013  N   Y
> MSVC 2015  N   Y
> MSVC 2017  N   Y
> MinGW  N   Y
> (4 packages)

I don't think we can drop all 32bit support. I do believe MSVC 2017 should be 
part of the deal though. That's a good suggestion. Keeping these two options in 
mind, I suggest to drop MSVC 2013 32 bit against MSVC 2017 64bit. This keeps 
the number of packages the same.


> This also allows us to pick one compiler to provide 32-bit support with if we
> need to. I just think it's time to let it die and get people who need it to 
> compile
> from source.

Compiling Qt from source (especially on Windows) is still a major headache for 
our customers.

> 
> There are no current Intel 32-bit only CPUs that regular Windows runs on, only
> legacy. I don't know AMD's product line, but I'd be surprised if it is 
> different.

The currently sold CPU's are not really the measurement stick here. The 
measurement stick is actually installed Win 32 systems. 

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

Re: [Development] Nominating James McDonnell for approver status

[Alexander Blasche]

> -Original Message-
> From: Lars Knoll
 
> I added him to the gerrit Approver group. Alex can do any adjustments to Jira
> that are required.

Done.
--
Alex


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

Re: [Development] Upcoming Jira outage (9 Nov 2:00-4:00 UTC)

[Alexander Blasche]

Hi,

The changes are completed.You may need to clean the cache to load the site.

Compression was enabled during the changes,see 
https://bugreports.qt.io/browse/QTJIRA-300

--
Alex


From: Development <development-bounces+alexander.blasche=qt...@qt-project.org> 
on behalf of Alexander Blasche <alexander.blas...@qt.io>
Sent: Tuesday, 8 November 2016 9:42:33 AM
To: development@qt-project.org; qt-crea...@qt-project.org; 
inter...@qt-project.org Interest
Subject: [Development] Upcoming Jira outage (9 Nov 2:00-4:00 UTC)

Hi,

Due to maintenance on the Jira machine, bugreports.qt.io will be temporarily 
unavailable on

November 9 , 2:00 AM ~ 4:00AM UTC+0

We apologize for the inconvenience that this might cause.

--
Alex
___
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] Upcoming Jira outage (9 Nov 2:00-4:00 UTC)

[Alexander Blasche]

Hi,

Due to maintenance on the Jira machine, bugreports.qt.io will be temporarily 
unavailable on

November 9 , 2:00 AM ~ 4:00AM UTC+0

We apologize for the inconvenience that this might cause.

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

Re: [Development] dev doesnt builds

[Alexander Blasche]

Hi

>Cannot read .qt5/qtbase/src/corelib/qtcore-config.pri: No such file or 
>directory
>Cannot read .qt5/qtbase/src/gui/qtgui-config.pri: No such file or directory
>Project ERROR: Could not find feature system-zlib.
>Makefile:45: recipe for target 'sub-src-make_first' failed
>make[1]: *** [sub-src-make_first] Error 3
>make[1]: Leaving directory '../qt5/qtbase'
>Makefile:78: recipe for target 'module-qtbase-make_first' failed
>make: *** [module-qtbase-make_first] Error 2

>is there a workaround for this?


I had the same problem. Make sure that you have an up-to-date qt5.git checkout 
for dev as well. In combination with git clean the problem solved itself for me.

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

Re: [Development] Nominating Paolo Angelelli for Approver status

[Alexander Blasche]

Congratulations to Paolo.

The permissions have been adjusted.

--
Alex


From: Development <development-bounces+alexander.blasche=qt...@qt-project.org> 
on behalf of Alexander Blasche <alexander.blas...@qt.io>
Sent: Friday, 26 August 2016 10:17:12 AM
To: development@qt-project.org
Subject: [Development]  Nominating Paolo Angelelli for Approver status

Hi,

I'd like to nominate Paolo Angelelli for Approver status. He joined The Qt 
Company at the end of 2015, and has been working full time on Qt since. Paolo 
has been actively involved fixing and improving QtPositioning and QtLocation.

--
Alex
___
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] Maintainers: your action needed: Qt 5.6.2 change files mostly missing!

[Alexander Blasche]

Ok, I was not aware of TP status. In this case I stand corrected.

--
Alex


From: Simon Hausmann
Sent: Monday, 12 September 2016 1:25:16 PM
To: Alexander Blasche; Sean Harmer; Jani Heikkinen
Cc: development@qt-project.org
Subject: Re: [Development] Maintainers: your action needed: Qt 5.6.2 change 
files mostly missing!

Hi,


It should be noted that Qt3D has "preview" status in the Qt 5.6 branch. So I 
don't think anybody should rely on the content

of qt3d in the 5.6 branch and consequently look for a changelog :)



Simon


From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> on 
behalf of Alexander Blasche <alexander.blas...@qt.io>
Sent: Monday, September 12, 2016 11:46:31 AM
To: Sean Harmer; Jani Heikkinen
Cc: development@qt-project.org
Subject: Re: [Development] Maintainers: your action needed: Qt 5.6.2 change 
files mostly missing!

Hi Sean,

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: Monday, 12 September 2016 9:59

> Qt 3D doesn’t need one for 5.6.2.

If that's the case then please add a statement to the change log telling the 
reader that there were no noteworthy changes. To the Qt user there is no way to 
distinguish a missing change log due to no changes from a missing change log 
because we didn't write it (despite having potentially a lot).

In my opinion there are noteworthy changes in Qt3D. There are 2 bugs fixed and 
hover event related changes... Don't you think this is relevant?

--
Alex
___
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] Maintainers: your action needed: Qt 5.6.2 change files mostly missing!

[Alexander Blasche]

Hi Sean,

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: Monday, 12 September 2016 9:59

> Qt 3D doesn’t need one for 5.6.2.

If that's the case then please add a statement to the change log telling the 
reader that there were no noteworthy changes. To the Qt user there is no way to 
distinguish a missing change log due to no changes from a missing change log 
because we didn't write it (despite having potentially a lot).

In my opinion there are noteworthy changes in Qt3D. There are 2 bugs fixed and 
hover event related changes... Don't you think this is relevant?

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

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

[Alexander Blasche]

From: Marc Mutz 

>On Wednesday 07 September 2016 08:37:01 Friedemann Kleint wrote:
>> ** After 5.7 is closed and sanity bot is upgraded (to handle
>> cherry-picking), go into cherrypicking mode for 5.6. Developer is
>> responsible for doing the cherrypicking
>> ** Cherry-picking technicalities need to be figured out: Let sanity bot
>> verify source ("cherrypicked from") the SHA1

>I'm sorry, but this is nonsense.

I agree with Marc. Why cant we do 5.6->5.8 merges once the 5.7 branch is 
closed? Since the 5.6 branch will get fewer and fewer patches as the strictness 
of its commits increases I see no reason why 5.6->5.8 could pose a problem.

Maybe you sb can elaborate why we have to go to cherry-picking? The notes don't 
say and I wasn't in this QtCon meeting.
--
Alex
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt Network Maintainership Changes

[Alexander Blasche]

>From: Development  
>on behalf of Richard Moore 

>I'd like to nominate Timur  as my replacement - he's already spent an 
>inordinate amount of time fixing bugs, 
>to say nothing of adding support for HTTP/2 so I'm sure things are in good 
>hands.

+1

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

[Development] Nominating Paolo Angelelli for Approver status

[Alexander Blasche]

Hi,

I'd like to nominate Paolo Angelelli for Approver status. He joined The Qt 
Company at the end of 2015, and has been working full time on Qt since. Paolo 
has been actively involved fixing and improving QtPositioning and QtLocation.

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

Re: [Development] Nominating Johan Helsing for Approver status

[Alexander Blasche]

Congratulations. The permission changes have been enacted.

--
Alex


From: Development  
on behalf of Giulio Camuffo 
Sent: Monday, 8 August 2016 9:14:55 AM
To: Erik Larsson
Cc: Qt development mailing list
Subject: Re: [Development] Nominating Johan Helsing for Approver status

+1

2016-08-06 8:31 GMT+02:00 Erik Larsson :
> +1
>
> 2016-08-04 12:22 GMT+02:00 Paul Tvete :
>>
>> Hi all,
>>
>>
>> I'd like to nominate Johan Helsing for Approver status. He joined The Qt
>> Company half a year ago, and has been working full time on Qt since. Johan
>> has been actively involved in making the QtWaylandCompositor module ready
>> for Qt 5.8, as well as doing a major part of the bug fixes for Qt Wayland in
>> 5.6 and 5.7.
>>
>> Here is his gerrit dashboard:
>>
>> https://codereview.qt-project.org/#/q/owner:%22Johan+Helsing%22,n,z
>>
>> Johan's list of reviews can be found at:
>>
>>
>> https://codereview.qt-project.org/#/q/reviewer:%22Johan+Helsing+%253Cjohan.helsing%2540theqtcompany.com%253E%22,p,003e6e7d0002807d
>>
>> Cheers,
>>
>> - Paul
>>
>>
>> ___
>> 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

[Development] Be aware: QtLocation's free MapQuest service discontinued

[Alexander Blasche]

Hi,

Qt Location provides three content/map provider plugins (HERE, MapBox and 
MapQuest). The first two providers require an account to run and MapQuest was 
free of any registration so far. Unfortunately this changed this Monday. More 
details in:

https://bugreports.qt.io/browse/QTBUG-54599

As a consequence any QtLocation application that uses MapQuest will no longer 
receive any map tiles. The only possible way to fix this today is to change 
from MapQuest to HERE or MapBox. Although those providers require a 
registration they do offer free of charge usage models. Please be aware of 
their terms and conditions though. 

We are very sorry for this problem but at the end of the day there is not much 
Qt can do. We are working on a patch to change to a new registration free 
provider and even a related indirection but at the end of the day, registration 
free access is becoming a thing of the past.

Going forward I would suggest to to always consider some form of registered 
usage for any map provider. While we will continue to address upcoming service 
changes this does ensure that there is some form of business relationship 
between you and your chosen map tile provider. At the very least it means that  
notifications can be received before drastic changes happen.

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

[Development] Source break policy for function overloads

[Alexander Blasche]

Hi,

Yesterday, I stumbled over a break in QtSerialBus due to the addition of new 
QTimer::setInterval(..) overloads in qtbase/dev. This was introduced by 

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

Unfortunately this has the undesirable side effect that lines like:

q->connect(q, ::timeoutChanged, element.timer.data(), 
::setInterval);

do not compile anymore. The function pointer to setInterval() becomes 
ambiguous. While the fix (https://codereview.qt-project.org/#/c/165034/) was 
not difficult once you know what is happening this can hit every customer and 
basically reduces the source compatibility promise into absurdity.

While talking to several devs in the office I could not find a congruent 
opinion on this issue. Do we or even can we care? Do we have a policy?

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

Re: [Development] Nominating Frank Meerkoetter for Approver status

[Alexander Blasche]

Conratulations to Frank. The rights have been adjusted accordingly.

--
Alex

From: Development  
on behalf of Simon Hausmann 
Sent: Friday, 20 May 2016 2:49:52 PM
To: development@qt-project.org
Subject: [Development] Nominating Frank Meerkoetter for Approver status

Hi,


I would like to nominate Frank for approver status. He has done a fair bit of 
surgery in the QML engine and also seems to be active on qtopcua/serialbus.


I appreciate his input on my patches and I trust him to responsibly review.



Simon

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

Re: [Development] modbus over serial port on windows 7 ?

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Denis Shienkov
> Sent: Thursday, 2 June 2016 7:11
> To: development@qt-project.org
> Subject: Re: [Development] modbus over serial port on windows 7 ?
> 
> > only the value of around 50ms gives a stable result in my case.
> 
> Hehh.. I warned the QtSerialBus team that introduction of 3.5 timeouts will 
> lead
> to bugs and that it doesn't make sense (though, it is described in the Modbus
> specification).

> We do not need to rely on this 'characters timeouts', because the
> OS can not provide this precision timeout (besides, Qt5 event loop introduces
> also an delay). But, nobody haven't listened to me.

Denis, that's a nice simplistic viewpoint but does not work for Modbus and 
comments like the above do not help either. 
Certain error cases can only be detected if you make assumptions about 
timeouts. Otherwise there is no way to determine where one packet stops and 
where the next one begins. We are dealing with contradicting requirements on 
protocol and OS level.

Obviously the current point is not optimal. We have to tweak more. Let's see 
what we can manage in QTBUG-53767. Please shift this discussion to the bug now. 
Thank you.

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

Re: [Development] Nominating Alexandru Croitor for Approver status

[Alexander Blasche]

Congratulations to Alexandru. Approver rights have been granted.

--
Alex


From: Development  
on behalf of Michael Brüning 
Sent: Wednesday, 11 May 2016 1:14:09 PM
To: development@qt-project.org
Subject: [Development] Nominating Alexandru Croitor for Approver status

Hi all,

I would like to nominate Alexandru Croitor for Approver status.
Alexandru joined The Qt Company about 6 months ago and has been working
full time on Qt since then and especially on the Qt WebEngine module.

Here is his Gerrit dashboard:
https://codereview.qt-project.org/#/q/owner:"Alexandru Croitor
"status:merged,n,z

And a list of his reviews:
https://codereview.qt-project.org/#/q/reviewer:"Alexandru Croitor
",n,z

Cheers,
Michael
___
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 Frank Meerkoetter for Approver status

[Alexander Blasche]

>I would like to nominate Frank for approver status. He has done a fair bit of 
>surgery in the QML

>engine and also seems to be active on qtopcua/serialbus.

+1

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

Re: [Development] Bluetooth Services problem

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Matías Néstor
> Ares
> Sent: Sunday, 15 May 2016 9:41
> To:  
> Subject: Re: [Development] Bluetooth Services problem
> 
> Problem persist in QT 5.6.1
> some help will be very appreciated !!

What platform are you using QtBluetooth on? (Bluez, Android, iOS and what 
particular version)
Please state the qtconnectivity SHA that you are using for your 5.6.1 build!
Which particular discovery mode triggers the warning (full or minimal)?
What exactly is printed in your command line when onServiceDiscovered is 
triggered?

--
Alex

> 2016-05-05 3:34 GMT-03:00 Matías Néstor Ares   >:
> 
> 
>   Hi Everybody!!
> 
>   I'm having an issue with bluetooth on QML on android  Qt 5.6.0
>   I can't even fully test the example:
>http://doc.qt.io/qt-5/qtbluetooth-scanner-example.html
> 
>   trying to access service inside onServiceDiscovered: it gets undefined.
> 
> 
>   as documentation says :  serviceDiscovered(BluetoothService service)
>serviceDiscovered parameter is "service" but it is undefined...
> 
>   is it a bug? is there some workaround?
> 
>   Thanks in advance.
> 
>   Best regards
> 

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

Re: [Development] Proposing Oliver Wolff as QtANGLE maintainer

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Andrew Knight

> Although this is not an official Qt module or platform, I propose Oliver
> as the new (Qt) ANGLE maintainer. He deserves a badge of honor for
> taking on this often less-than-satisfying, yet crucial, task within the
> Qt Project.

Indeed, thank you very much for stepping up. Here is my +1.

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

Re: [Development] Proposing Maurice Kalinowski as the Qt for Windows Runtime (winrt) Platform Maintainer

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Andrew Knight

> That said, I would like to propose Maurice Kalinowski as the new Windows
> Runtime Platform Maintainer.

+1 

--
Alex
 

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

Re: [Development] Header review for 5.7 (vs 5.6)

[Alexander Blasche]

> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Thiago Macieira
> Sent: Tuesday, 3 May 2016 18:59
> To: development@qt-project.org
> Subject: Re: [Development] Header review for 5.7 (vs 5.6)
> 
> Em terça-feira, 3 de maio de 2016, às 16:24:32 PDT, Edward Welbourne escreveu:
> > Consequently, to take the example of qtbase, instead of looking at more
> > than 100 k lines with no colouring mark-up to help you see what's really
> > changed, reviewers only need to look at a little under 8 k lines, split
> > up nicely by which file they're in and actually making good use of
> > Gerrit's ability to display diffs nicely.  Just be sure you don't do
> > anything silly like telling Gerrit to merge these commits
> 
> Thanks Eddy and everyone else who took the header diff to the next step!
> 
> BTW, I just checked and saw that the ABI report by Andrey was updated with 5.7
> beta:
> http://abi-laboratory.pro/tracker/timeline/qt/

Indeed thank you very very much.

This is not an urgent request but latest 5.8 please add coverage for the 
following git repos:

qtandroidextra, qtserialbus, qtsensors,

Thank you.

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

Re: [Development] Nominating Volker Krause for Approver status

[Alexander Blasche]

Hi,

Volker has acquired the OG approver rights. Congratulations.

--
Alex


From: Development 
 on 
behalf of Frederik Gladhorn 
Sent: Thursday, 31 March 2016 13:08
To: development@qt-project.org
Subject: Re: [Development] Nominating Volker Krause for Approver status

On Wednesday, March 30, 2016 09:34:40 AM Sean Harmer wrote:
> Hi All,
>
> I'd like to nominate Volker Krause for approver status. Volker is one of the
> main authors of GammaRay, is very active in the Qt Automotive sphere where
> he leads up KDAB's contributions, and has touched many parts all over Qt
> (including Qt 3D).
>
> His dashboard is at:
>
> https://codereview.qt-project.org/#/q/owner:%22Volker+Krause%22,n,z
>
> and reviews at:
>
> https://codereview.qt-project.org/#/q/reviewer:%22Volker+Krause%22,n,z
>
> Can I get a +1 please?

+1 from me as well :)

Greetings,
Frederik

>
> Cheers,
>
> Sean
>
> Disclaimer: I work at KDAB with Volker.
> --
> Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
> Klarälvdalens Datakonsult AB, a KDAB Group company
> Tel. UK +44 (0)1625 809908, Sweden (HQ) +46-563-540090
> KDAB - Qt Experts - Platform-independent software solutions
> ___
> 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