Re: [Development] MAINTAINERS: your action needed

[Jani Heikkinen]

Hi all,

There has been different ways of doing this. I some modules there has been that 
library one, some other the one we used at this time. Let's use that one; it is 
now in every changes file

br,
Jani

From: Development  on 
behalf of Denis Shienkov 
Sent: Friday, September 22, 2017 1:27 PM
To: Edward Welbourne; development@qt-project.org
Subject: Re: [Development] MAINTAINERS: your action needed

Previously, we (e.g. in qtserialport module) had this:


*   Library*


My question is: do we need to modify this "Qt 5.9.2 Changes" header? :)

BR,
Denis

22.09.2017 13:24, Edward Welbourne пишет:
> Denis Shienkov (22 September 2017 11:39)
>> do we need to keep this:
>>
>> 
>> *   Qt 5.9.2 Changes *
>> 
>>
>> as is?
> What were you thinking of changing about it ?
>
>   Eddy.

___
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

[Jani Heikkinen]

Use (which should be already in every changes file)


*   Qt 5.9.2 Changes
*


Jani

From: Denis Shienkov <denis.shien...@gmail.com>
Sent: Friday, September 22, 2017 2:31 PM
To: Jani Heikkinen; Edward Welbourne; development@qt-project.org
Subject: Re: [Development] MAINTAINERS: your action needed

 >  Let's use that one; it is now in every changes file

What's use? I do not understand.


22.09.2017 14:07, Jani Heikkinen пишет:
> Hi all,
>
> There has been different ways of doing this. I some modules there has been 
> that library one, some other the one we used at this time. Let's use that 
> one; it is now in every changes file
>
> br,
> Jani
> 
> From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> 
> on behalf of Denis Shienkov <denis.shien...@gmail.com>
> Sent: Friday, September 22, 2017 1:27 PM
> To: Edward Welbourne; development@qt-project.org
> Subject: Re: [Development] MAINTAINERS: your action needed
>
> Previously, we (e.g. in qtserialport module) had this:
>
> 
> *   Library*
> 
>
> My question is: do we need to modify this "Qt 5.9.2 Changes" header? :)
>
> BR,
> Denis
>
> 22.09.2017 13:24, Edward Welbourne пишет:
>> Denis Shienkov (22 September 2017 11:39)
>>> do we need to keep this:
>>>
>>> 
>>> *   Qt 5.9.2 Changes *
>>> 
>>>
>>> as is?
>> What were you thinking of changing about it ?
>>
>>Eddy.
> ___
> 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] HEADS-UP: Branching '5.9.2' from '5.9' started

[Jani Heikkinen]

Hi all,

We have finally soft branched '5.9.2' from '5.9'. So please start using '5.9.2' 
for new changes targeted to Qt 5.9.2 release. Final downmerge from '5.9' to 
'5.9.2' will happen Monday 25th September so there should be enough time to 
finalize ongoing changes in '5.9' and start using '5.9.2' for new ones. 

We are targeting to release Qt 5.9.2 as soon as possible; preferably already 
during next week so please make sure all blockers are fixed early enough. Qt 
5.9.2 blocker list here: https://bugreports.qt.io/issues/?filter=18736 . 

We (release team) will start creating initial change files for Qt 5.9.2 now. So 
Maintainers: Please finalize those initial ones immediately when available. We 
need those now really soon to be able to proceed with final release without 
further delay.

br,
Jani Heikkinen
Release Manager




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

[Development] Qt 5.6.3 released

[Jani Heikkinen]

Hi,

Qt 5.6.3 is released today, see 
http://blog.qt.io/blog/2017/09/21/qt-5-6-3-released/

Big thanks to everyone involved!

br,
Jani Heikkinen
Release Manager

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

[Development] Qt 5.9.2 and Qt Creator 4.4.1 released

[Jani Heikkinen]

Hi,

I am happy to inform Qt 5.9.2 and Qt Creator 4.4.1 are released today. Read 
more information about releases from blog posts:

Qt 5.9.2: http://blog.qt.io/blog/2017/10/06/qt-5-9-2-released/
Qt Creator 4.4.1: http://blog.qt.io/blog/2017/10/06/qt-creator-4-4-1-released/

Big thanks to everyone involved!

Br,
Jani Heikkinen
Release Manager





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

Re: [Development] Qt 5.9.2 and Qt Creator 4.4.1 released

[Jani Heikkinen]

It's there now; I just forgot to press 'save' ;)

br,
jani

From: Daniel Engelke <daniel.enge...@basyskom.com>
Sent: Friday, October 6, 2017 12:22 PM
To: 'development@qt-project.org'
Cc: Jani Heikkinen
Subject: Re: [Development] Qt 5.9.2 and Qt Creator 4.4.1 released

Hi,

http://wiki.qt.io/Qt_5.9.2_Change_Files
>>> There is currently no text in this page. You can search for this page 
>>> title<http://wiki.qt.io/Special:Search/Qt_5.9.2_Change_Files> in other 
>>> pages, or search the related 
>>> logs<http://wiki.qt.io/index.php?title=Special:Log=Qt_5.9.2_Change_Files>,
>>>  but you do not have permission to create this page.

Forgot about it or is it coming? :)

Br,
Daniel

On 10/06/2017 11:12 AM, Jani Heikkinen wrote:

Hi,

I am happy to inform Qt 5.9.2 and Qt Creator 4.4.1 are released today. Read 
more information about releases from blog posts:

Qt 5.9.2: http://blog.qt.io/blog/2017/10/06/qt-5-9-2-released/
Qt Creator 4.4.1: http://blog.qt.io/blog/2017/10/06/qt-creator-4-4-1-released/

Big thanks to everyone involved!

Br,
Jani Heikkinen
Release Manager





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


--
Daniel Engelke
Software Engineer

basysKom GmbH
Robert-Bosch-Str. 7 | 64293 Darmstadt | Germany
Tel: +49 6151 870 589 -0 | Fax: -199
daniel.enge...@basyskom.com<mailto:daniel.enge...@basyskom.com> | 
www.basyskom.com<https://www.basyskom.com>

Handelsregister: Darmstadt HRB 9352
Geschaeftsfuehrung: Dr. Eva Brucherseifer, Heike Ziegler
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Staging in '5.6'

[Jani Heikkinen]

Hi all,



After Qt 5.6.3 release, staging has been restricted in ‘5.6’ and I have 
monitored some of the changes trying to come in. I have noticed people 
sometimes trying to put some really minor P3 etc fixes in ‘5.6’ even those 
really shouldn’t be put in there. With ‘5.6’ we are already in ‘strict’ mode so 
there shouldn’t be that much changes taken in ( see 
http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.txt )



Ossi opened staging for everyone but I propose we should restrict staging for 
release team only. That way we could better monitor changes coming into ‘5.6’ 
and owners must explain really well why every change is really needed in ‘5.6’ 
series. That will decrease changes in ‘5.6’ and so on decrease the risk of new 
regression. And this all would be good preparations for moving to very strict 
mode which should happen March 2018.



br,

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

[Development] Qt 5.10 Alpha released

[Jani Heikkinen]

Hi all,

Qt 5.10 Alpha is released today, see 
http://blog.qt.io/blog/2017/09/13/qt-5-10-alpha-released/
Once again it was a bit hard but finally it is out. Big thanks to everyone 
involved!

br,
Jani Heikkinen
Release Manager



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

[Development] Qt 5.9.2 snapshot for testing

[Jani Heikkinen]

Hi all,

There is new Qt 5.9.2 snapshot available via online installer. Content isn't 
yet final Qt 5.9.2 content but pretty close; fix for one blocker + some change 
files are still missing.

Please test the snapshot to see if we really are close the release. We are 
targeting to get Qt 5.9.2 out during next week so please make sure all new 
blocker are immediately visible in blocker list ( 
https://bugreports.qt.io/issues/?filter=18736 ). But please note: Qt 5.9.3 will 
follow soon and so on we won't block Qt 5.9.2 release that easily. It means if 
issue were in Qt 5.9.1 we can release Qt 5.9.2 with it as well. And no any 
nice-to-haves in anymore; those can wait Qt 5.9.3 from now on...

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

[Development] HEADS-UP: Branching '5.9.2' completed

[Jani Heikkinen]

Hi all,

Final downmerge from '5.9' to '5.9.2' is now done. So '5.9' is for Qt 5.9.3 
from now on and all changes targeted to Qt 5.9.2 release needs to be done in 
'5.9.2'

br,
Jani

> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Jani Heikkinen
> Sent: keskiviikko 20. syyskuuta 2017 13.52
> To: development@qt-project.org
> Cc: releas...@qt-project.org
> Subject: [Development] HEADS-UP: Branching '5.9.2' from '5.9' started
> 
> Hi all,
> 
> We have finally soft branched '5.9.2' from '5.9'. So please start using 
> '5.9.2' for
> new changes targeted to Qt 5.9.2 release. Final downmerge from '5.9' to 
> '5.9.2'
> will happen Monday 25th September so there should be enough time to finalize
> ongoing changes in '5.9' and start using '5.9.2' for new ones.
> 
> We are targeting to release Qt 5.9.2 as soon as possible; preferably already
> during next week so please make sure all blockers are fixed early enough. Qt
> 5.9.2 blocker list here: https://bugreports.qt.io/issues/?filter=18736 .
> 
> We (release team) will start creating initial change files for Qt 5.9.2 now. 
> So
> Maintainers: Please finalize those initial ones immediately when available. We
> need those now really soon to be able to proceed with final release without
> further delay.
> 
> br,
> Jani Heikkinen
> Release Manager
> 
> 
> 
> 
> ___
> 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

[Jani Heikkinen]

Hi all,

Quite many of these are still not in, see 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.2%22,n,z

Please finalize and get +2 as soon as possible; preferably already today. We 
need to get these in now to be able to get release out

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Friday, September 22, 2017 12:34 PM
To: development@qt-project.org
Subject: [Development] MAINTAINERS: your action needed

Hi,

We did initial change files for Qt 5.9.2, see 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.2%22,n,z

Maintainers: Please do needed modifications immediately and get '+2' . We need 
these to be able to proceed with Qt 5.9.2 release

br,
Jani



___
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] 5.10 branching status?

[Jani Heikkinen]

Hi,

> -Original Message-
> From: Development [mailto:development-
> bounces+jani.heikkinen=qt...@qt-project.org] On Behalf Of André
> Hartmann
> Sent: tiistai 22. elokuuta 2017 9.21
> To: development@qt-project.org
> Subject: [Development] 5.10 branching status?
> 
> Hi all,
> 
> We had 5.10 feature freeze two weeks ago but I still see no 5.10 branch in
> Gerrit. That means everything submitted to master now will land in 5.10?!
> That effectively blocks master for new features, and if I want fixes for 5.10 
> I
> have to push them to master also, not knowing when a
> 5.10 branch is created.
> 
> So my question is: How is the status about 5.10 branching?
> 

We are still waiting successfully qt5.git integration before we can start 
branching. There has been progress but few tests are still failing and so on 
blocking the successfully qt5.git integration. You can follow-up the progress 
from https://codereview.qt-project.org/#/c/201350/ & see open blockers from 
https://bugreports.qt.io/issues/?filter=18856
 
The plan is to start branching immediately after qt5.git integration succeed in 
'dev' . Final downmerge from 'dev' to '5.10' will be done ~after a week from 
starting. So yes, unfortunately this means new feature development in blocked 
in 'dev' at the moment, sorry about that. We are doing our best to proceed as 
soon as possible

br,
Jani

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

[Development] HEADS-UP: Branching from 'dev' to '5.10' started

[Jani Heikkinen]

HI all,


We have finally soft branched '5.10' from 'dev'. Target is to have final 
downmerge from 'dev' to '5.10'  Friday 1st September



Please finalize ongoing changes in 'dev' and start using '5.10' for new changes 
targeted to Qt 5.10.0 release.



br,

Jani Heikkinen

Release Manager

The Qt Company



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

Re: [Development] Maintainers, your actions needed: Change files for Qt 5.6.3

[Jani Heikkinen]

> -Original Message-
> From: André Hartmann [mailto:andre.hartm...@iseg-hv.de]
> Sent: tiistai 29. elokuuta 2017 9.25
> To: Jani Heikkinen <jani.heikki...@qt.io>; development@qt-project.org
> Subject: Re: [Development] Maintainers, your actions needed: Change files
> for Qt 5.6.3
> 
> Hi Jani,
> 
> I have some comments to the change file process:
> 
> 1. The commit message is "Add change file for Qt 5.6.3" but it should be
> "Add changes file for Qt 5.6.3" (plural)

True, let's be more exact at next time

>2. In the last releases, this initial version was WIP, so the maintainer
> needed to adjust the message so it could be merged. I think this is
> useful.

There were also opposite comments earlier about this ;) But both is OK for us; 
I don't see that big difference there...


> 3. How about projects with no changes between 5.6.2 and 5.6.3
> (like qtserialbus)? Usually there is also a changes file with a line
> "No relevant changes in this release", but right now there is no file
> a all.
Yes, this is a mistake. We try to do one for all but qtserialbus was ignored 
because of some reason. It is now done.

> 
> I know it is some effort for the release team to create these templates, but
> with good templates you get consistent final files for the whole project.

True, and I think we need to improve this somehow in the future. I think we 
should discuss this in contributor summit

- Jani
> 
> Best regards,
> André
> 
> Am 29.08.2017 um 06:53 schrieb Jani Heikkinen:
> > Hi all,
> >
> > We have now created initial change files for Qt 5.6.3. Please do
> > needed modifications immediately and get '+2' as soon as possible. We
> > need to get these in to be able to proceed with Qt 5.6.3 release. You
> > can find all open change files for Qt 5.6.3 here:
> > https://codereview.qt-
> project.org/#/q/branch:5.9+status:open+message:%
> > 22Add+change+file%22,n,z
> >
> > After approval those change files will be direct pushed in '5.9',
> > cherry picked in '5.6.3' and finally direct pushed there, see
> > http://lists.qt-project.org/pipermail/development/2017-August/030722.h
> > tml
> >
> > br,
> > Jani Heikkinen
> > Release Manager
> >
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> >
> >
> 
> 
> --
> Best regards / Mit freundlichen Grüßen
> André Hartmann, Dipl.-Ing. (FH)
> Software Project Manager
> 
> iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
> Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
> D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com
> 
> Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
> Amtsgericht / Lower district court: Dresden HRB 16250 Ust.-Id.-Nr. / VAT-ID:
> DE812508942
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist
> nicht gestattet.
> 
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail.
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-
> mail is strictly forbidden.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Maintainers, your actions needed: Change files for Qt 5.6.3

[Jani Heikkinen]

Hi all,

We have now created initial change files for Qt 5.6.3. Please do needed 
modifications immediately and get '+2' as soon as possible. We need to get 
these in to be able to proceed with Qt 5.6.3 release. You can find all open 
change files for Qt 5.6.3 here: 
https://codereview.qt-project.org/#/q/branch:5.9+status:open+message:%22Add+change+file%22,n,z

After approval those change files will be direct pushed in '5.9', cherry picked 
in '5.6.3' and finally direct pushed there, see 
http://lists.qt-project.org/pipermail/development/2017-August/030722.html

br,
Jani Heikkinen
Release Manager


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

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

[Jani Heikkinen]

Hi all,

We have completed branching from 'dev' to '5.10' today. From now on 'dev' is 
for Qt 5.11 and all changes targeted to Qt 5.10 release must be done in '5.10' 
instead.
If you still have some change open in 'dev'  and it must be in Qt 5.10 release 
you need to send a re-targeting request to Frederik Gladhorn (Ossi is on 
vacation).

br,
Jani


From: Development 
[mailto:development-bounces+jani.heikkinen=qt...@qt-project.org] On Behalf Of 
Jani Heikkinen
Sent: sunnuntai 27. elokuuta 2017 12.02
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: [Development] HEADS-UP: Branching from 'dev' to '5.10' started

HI all,


We have finally soft branched '5.10' from 'dev'. Target is to have final 
downmerge from 'dev' to '5.10'  Friday 1st September



Please finalize ongoing changes in 'dev' and start using '5.10' for new changes 
targeted to Qt 5.10.0 release.



br,

Jani Heikkinen

Release Manager

The Qt Company



___
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] Qt 5.9.2 snapshot available

[Jani Heikkinen]

Hi,

We have new Qt 5.9.2 snapshot available via online installer. Instructions how 
to get it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer

Snapshot is based on https://codereview.qt-project.org/#/c/203493/

Packages are smoke tested and seems to be OK so please take a tour. Please 
report your effort via https://wiki.qt.io/Qt59_release_testing

br,
Jani Heikkinen
Release Manager

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

Re: [Development] Maintainers, your actions needed: Change files for Qt 5.6.3

[Jani Heikkinen]

Still 9 changes file without '+2':

- qt/qtbase
- qt/qtwebsockets
- qt/qtwebsockets
- qt/qtdatavis3d
- qt/qtgraphicaleffects
- qt/qtwebchannel
- qt/qtcanvas3d
- qt/qtmacextras
- qt/qtactiveqt

Maintainers, please make sure these will ready latest on Monday morning

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Thursday, August 31, 2017 9:06 AM
To: development@qt-project.org
Subject: Re: [Development] Maintainers, your actions needed: Change files for 
Qt 5.6.3

Hi all,

Still quite many Qt 5.6.3 change files still without any action or missing 
'+2'... (see 
https://codereview.qt-project.org/#/q/message:%22Add+change+file+for%22,n,z )

Maintainers, please finalize these during today; we need to get these in to be 
able to proceed with Qt 5.6.3 release

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Tuesday, August 29, 2017 1:04 PM
To: André Hartmann; development@qt-project.org
Subject: Re: [Development] Maintainers, your actions needed: Change files for 
Qt 5.6.3

> -Original Message-
> From: André Hartmann [mailto:andre.hartm...@iseg-hv.de]
> Sent: tiistai 29. elokuuta 2017 9.25
> To: Jani Heikkinen <jani.heikki...@qt.io>; development@qt-project.org
> Subject: Re: [Development] Maintainers, your actions needed: Change files
> for Qt 5.6.3
>
> Hi Jani,
>
> I have some comments to the change file process:
>
> 1. The commit message is "Add change file for Qt 5.6.3" but it should be
> "Add changes file for Qt 5.6.3" (plural)

True, let's be more exact at next time

>2. In the last releases, this initial version was WIP, so the maintainer
> needed to adjust the message so it could be merged. I think this is
> useful.

There were also opposite comments earlier about this ;) But both is OK for us; 
I don't see that big difference there...


> 3. How about projects with no changes between 5.6.2 and 5.6.3
> (like qtserialbus)? Usually there is also a changes file with a line
> "No relevant changes in this release", but right now there is no file
> a all.
Yes, this is a mistake. We try to do one for all but qtserialbus was ignored 
because of some reason. It is now done.

>
> I know it is some effort for the release team to create these templates, but
> with good templates you get consistent final files for the whole project.

True, and I think we need to improve this somehow in the future. I think we 
should discuss this in contributor summit

- Jani
>
> Best regards,
> André
>
> Am 29.08.2017 um 06:53 schrieb Jani Heikkinen:
> > Hi all,
> >
> > We have now created initial change files for Qt 5.6.3. Please do
> > needed modifications immediately and get '+2' as soon as possible. We
> > need to get these in to be able to proceed with Qt 5.6.3 release. You
> > can find all open change files for Qt 5.6.3 here:
> > https://codereview.qt-
> project.org/#/q/branch:5.9+status:open+message:%
> > 22Add+change+file%22,n,z
> >
> > After approval those change files will be direct pushed in '5.9',
> > cherry picked in '5.6.3' and finally direct pushed there, see
> > http://lists.qt-project.org/pipermail/development/2017-August/030722.h
> > tml
> >
> > br,
> > Jani Heikkinen
> > Release Manager
> >
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> >
> >
>
>
> --
> Best regards / Mit freundlichen Grüßen
> André Hartmann, Dipl.-Ing. (FH)
> Software Project Manager
>
> iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
> Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
> D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com
>
> Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
> Amtsgericht / Lower district court: Dresden HRB 16250 Ust.-Id.-Nr. / VAT-ID:
> DE812508942
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist
> nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error)
> please notify the se

Re: [Development] Maintainers, your actions needed: Change files for Qt 5.6.3

[Jani Heikkinen]

Hi all,

Still quite many Qt 5.6.3 change files still without any action or missing 
'+2'... (see 
https://codereview.qt-project.org/#/q/message:%22Add+change+file+for%22,n,z )

Maintainers, please finalize these during today; we need to get these in to be 
able to proceed with Qt 5.6.3 release

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Tuesday, August 29, 2017 1:04 PM
To: André Hartmann; development@qt-project.org
Subject: Re: [Development] Maintainers, your actions needed: Change files for 
Qt 5.6.3

> -Original Message-
> From: André Hartmann [mailto:andre.hartm...@iseg-hv.de]
> Sent: tiistai 29. elokuuta 2017 9.25
> To: Jani Heikkinen <jani.heikki...@qt.io>; development@qt-project.org
> Subject: Re: [Development] Maintainers, your actions needed: Change files
> for Qt 5.6.3
>
> Hi Jani,
>
> I have some comments to the change file process:
>
> 1. The commit message is "Add change file for Qt 5.6.3" but it should be
> "Add changes file for Qt 5.6.3" (plural)

True, let's be more exact at next time

>2. In the last releases, this initial version was WIP, so the maintainer
> needed to adjust the message so it could be merged. I think this is
> useful.

There were also opposite comments earlier about this ;) But both is OK for us; 
I don't see that big difference there...


> 3. How about projects with no changes between 5.6.2 and 5.6.3
> (like qtserialbus)? Usually there is also a changes file with a line
> "No relevant changes in this release", but right now there is no file
> a all.
Yes, this is a mistake. We try to do one for all but qtserialbus was ignored 
because of some reason. It is now done.

>
> I know it is some effort for the release team to create these templates, but
> with good templates you get consistent final files for the whole project.

True, and I think we need to improve this somehow in the future. I think we 
should discuss this in contributor summit

- Jani
>
> Best regards,
> André
>
> Am 29.08.2017 um 06:53 schrieb Jani Heikkinen:
> > Hi all,
> >
> > We have now created initial change files for Qt 5.6.3. Please do
> > needed modifications immediately and get '+2' as soon as possible. We
> > need to get these in to be able to proceed with Qt 5.6.3 release. You
> > can find all open change files for Qt 5.6.3 here:
> > https://codereview.qt-
> project.org/#/q/branch:5.9+status:open+message:%
> > 22Add+change+file%22,n,z
> >
> > After approval those change files will be direct pushed in '5.9',
> > cherry picked in '5.6.3' and finally direct pushed there, see
> > http://lists.qt-project.org/pipermail/development/2017-August/030722.h
> > tml
> >
> > br,
> > Jani Heikkinen
> > Release Manager
> >
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> >
> >
>
>
> --
> Best regards / Mit freundlichen Grüßen
> André Hartmann, Dipl.-Ing. (FH)
> Software Project Manager
>
> iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
> Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
> D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com
>
> Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
> Amtsgericht / Lower district court: Dresden HRB 16250 Ust.-Id.-Nr. / VAT-ID:
> DE812508942
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist
> nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail.
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-
> mail is strictly forbidden.
___
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] HEADS UP : Qt 5.10 soft string freeze

[Jani Heikkinen]

Hi all,

Qt 5.10 beta is out & work towards final release continues. One step on the way 
is String Freeze which should happen really soon to be able to minimize time 
needed between beta and RC. So let's start keeping the translatable strings as 
it is & fix remaining important issues. And let's have the official String 
Freeze for Qt 5.10 27th October 2017.

Br,
Jani Heikkinen
Release Manager




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

Re: [Development] Dropping of MSVC 2013

[Jani Heikkinen]

Hi,

We discussed about this last spring and then the decision was that 5.10 is too 
early but 5.11 might be possible. 

br,
Jani

> -Original Message-
> From: Development [mailto:development-
> bounces+jani.heikkinen=qt...@qt-project.org] On Behalf Of Thiago Macieira
> Sent: keskiviikko 18. lokakuuta 2017 7.51
> To: development@qt-project.org
> Subject: [Development] Dropping of MSVC 2013
> 
> This came up again in QtCS and we decided that dropping it soon is probably a
> good idea, especially after Qt 5.9 became LTS.
> 
> Did we decide on 5.10 or 5.11?
> 
> Because one of my changes for 5.10 is currently failing on MSVC 2013 as
> designed. I need to refactor it for it to compile there.
> 
> Do I need to implement it? Or shall we drop that compiler?
> --
> 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

[Development] Qt 5.10.0 RC out

[Jani Heikkinen]

Hi all,

Qt 5.10.0 RC is released today. Delta to Beta4 as an attachment.

We are targeting to get final Qt 5.10.0 out 30.11.2017 as planned so please 
test the packages now & report me immediately if you find something which 
should really block the release. But remember: We won't block the release 
without really good reasons. Qt 5.10.1 will be released quite quickly so if we 
can live with issue as known issue in Qt 5.10.0 we will. So please add those 
issues directly in known issues page 
(https://wiki.qt.io/Qt_5.10.0_Known_Issues).

Instructions how to get the release are here: 
https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

br,
Jani




qt5.10-beta4-delta-rc-commits
Description: qt5.10-beta4-delta-rc-commits
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.9.3 released

[Jani Heikkinen]

Hi all,

We have released Qt 5.9.3 today, see 
http://blog.qt.io/blog/2017/11/22/qt-5-9-3-released/

Big thanks for everyone involved!

br,
Jani Heikkinen
Release Manager

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

Re: [Development] CMake & iOS

[Jani Heikkinen]

Hi Ari,

Thanks for your feedback. Please write a bug report in the Jira about this issue

br,
Jani

From: Development  on 
behalf of Ari Salmi 
Sent: Wednesday, November 22, 2017 3:23 PM
To: development@qt-project.org
Subject: [Development] CMake & iOS

Hi,

Have anyone else tried out creating cmake project for iOS (with Qt 5.9.x and 
today announced Qt 5.9.3)?

I have - also today with Qt 5.9.3
1. Create new application with Qt Creator with cmake
2. Select iOS as target
3. Compile

—> it won’t compile for iOS (will do with macOS).

623 x warning coming out from each Qt lib:
:-1: warning: URGENT: building for OSX, but linking in object file 
(.../Qt/5.9.3/ios/lib/libQt5Core_debug.a(qresource.o)) built for iOS. Note: 
This will be an error in the future.

And failing in linking phase.
That means the default cmake config for iOS is pointing macOS toolchain?

Br, Ari

Ari Salmi
SnowGrains
www.snowgrains.com



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

[Development] Qt 5.11 initial schedule

[Jani Heikkinen]

Hi all,

Now when Qt 5.10.0 is in its final steps it is time to start scheduling Qt 
5.11. As usual we need to get it out before summer holiday period so let's 
target to get it out at the end of May as usual.  Below is my proposal for Qt 
5.11 initial schedule (based on realized schedules with Qt 5.9 and Qt 5.10):

Soft Branching starts 24th January 2018
Feature Freeze & Finalize branching 31st January 2018
Alpha Release 21st February 2018
First Beta Release 21st March 2018
Release Candidate 17th May 2018
Final Release 31st May 2018

And note: This is just an initial schedule based on earlier experience & we 
will try to get release(s) out as soon as possible after feature freeze.

br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Urgent: Qt 5.9.3 binaries built with too NEW Linux distribution

[Jani Heikkinen]

> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Konstantin Tokarev
> Sent: torstai 30. marraskuuta 2017 20.49
> To: Thiago Macieira ; development@qt-
> project.org
> Subject: Re: [Development] Urgent: Qt 5.9.3 binaries built with too NEW Linux
> distribution
> 
> 
> 
> 30.11.2017, 20:47, "Thiago Macieira" :
> > See https://bugreports.qt.io/browse/QTBUG-64820 and
> > http://lists.qt-project.org/pipermail/interest/2017-November/028766.ht
> > ml
> >
> > The Qt 5.9.3 binaries were compiled by GCC 6, which is too new for the
> > latest Ubuntu LTS (16.04). I urgently recommend:
> >
> >  1) find some older distro (possibly Ubuntu 16.04 LTS) to compile the
> > 5.10 and further 5.9 binaries with.

We will start using devtoolset-4 again, but in RHEL 7.4. It is easiest and 
safest change now & should be doable within 5.10.0 schedule. Work is already 
ongoing.
> >
> >  2) recompile the 5.9.3 binaries and post them. No changes to the
> > source code, just rebuild.

I understand that but still I think we shouldn't do this. Qt 5.9.4 is coming on 
January and I hope we can wait to fix this there. We are that hurry atm and 
even this is quite simple task it still takes quite much effort from us. One 
basic idea with this new release model is just this; if we found some 
regression it will be fixed quite soon with next patch release. So that's why I 
hope we can just add this in Qt 5.9.3 known issue & fix this in Qt 5.9.4 
instead.

br,
Jani


> 
> It seems that when RHEL was updated from 7.2 to 7.4 [1], devtoolset-6 was
> installed instead of devtoolset-4 [2]. As we use artifacts from RHEL7
> configuration as official binaries, they started to require GCC 6
> 
> [1] https://codereview.qt-project.org/#/c/204675/38
> 
> [2] One of patches integrated before that provisioning change:
> 
> https://testresults.qt.io/coin/api/results/qt/qtbase/1e813c55a1e3d07549cfe2d
> d6fe3a927c3677c19/LinuxRHEL_7_2x86_64LinuxRHEL_7_2x86_64GCCqtci-
> linux-RHEL-7.2-x86_64-
> e1aea8Release_NoUseGoldLinker/2a48a3b7dcb9652b1532a3ad14de7580b5b9b
> 1ee/build_1508179165/log.txt.gz
> 
> >
> > --
> > 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
> 
> --
> Regards,
> Konstantin
> ___
> 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] Fw: Qt 5.10 RC2 is out

[Jani Heikkinen]

Hi all,

Qt 5.10 RC2 is released today. Delta to RC1 as an attachment.

Unfortunately there is still at least two issues in RC2 which must be fixed 
before final Qt 5.10.0 release: QTBUG-64868 & QTBUG-64820. Luckily we have 
fixes for both available & we are planning to get RC3 out on Monday. And if it 
will be finally ok for the release we will release Qt 5.10.0 on Thursday as 
planned.

Instructions how to get the release are here: 
https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

br,
Jani





qt5.10-rc1-delta-rc2-commits
Description: qt5.10-rc1-delta-rc2-commits
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] MAINTAINERS, your action needed: Qt change files

[Jani Heikkinen]

Hi,

Quite many 5.10 changes file still under construction, see 
https://codereview.qt-project.org/#/q/message:%22changes+file+for+Qt+5.10.0%22,n,z

Please finalize those as soon as possible; we need those before we can create 
RC packages. 

br,
Jani

And I know, branching is still ongoing so I understand that we might need to 
wait that until finalize change files in some modules. But most of modules that 
shouldn't needed & we can finalize those already now. We are targeting to 
finalize branching immediately after qt5.git merge from 5.9 -> 5.10 is 
finalized (https://codereview.qt-project.org/#/c/211681/)

From: Jani Heikkinen
Sent: Sunday, November 12, 2017 7:09 PM
To: development@qt-project.org
Subject: RE: MAINTAINERS, your action needed: Qt change files

Hi all,

We are still missing +2 from 3 Qt 5.9.3 changes files:

- https://codereview.qt-project.org/#/c/210114/ (qt/qtx11extras)
- https://codereview.qt-project.org/#/c/210097/ (qt/qtwebchannel)
- https://codereview.qt-project.org/#/c/210104/ (qt/qtbase)

And in 5.10.0 situation is much worse, see 
https://codereview.qt-project.org/#/q/message:%22changes+file+for+Qt+5.10.0%22,n,z
Missing:
-qt/qtbase
-qt/qtx11extras
-qt/qtlocation
-qt/qt3d
-qt/qtvirtualkeyboard
-qt/qtdoc
-qt/qtwebsockets
-qt/qtscxml
-qt/qttools
-qt/qtwebengine
-qt/qtwebchannel
-qt/qtsensors
-qt/qtconnectivity
-qt/qtwinextras
-qt/qtpurchasing
-qt/qtdeclarative

br,
Jani

> -Original Message-
> From: Jani Heikkinen
> Sent: perjantai 10. marraskuuta 2017 7.57
> To: development@qt-project.org
> Subject: MAINTAINERS, your action needed: Qt change files
>
> Hi all,
>
> We have still missing quite many +2 from 5.9.3 change files, see
> https://codereview.qt-project.org/#/q/message:%22file+for+Qt+5.9.3%22,n,z
> - qt/qtx11extras
> - qt/qt3d
> - qt/qtgraphicaleffects
> - qt/qtwebchannel
> - qt/qtwebview
> - qt/qtpurchasing
> - qt/qtscxml
> - qt/qtwebengine
> - qt/qtlocation
> - qt/qtdeclarative
> - qt/qtbase
>
> We really need these in now to be able to get Qt 5.9.3 out during next week!
>
> And there is already initial change files for Qt 5.10.0, see 
> https://codereview.qt-
> project.org/#/q/message:%22changes+file+for+Qt+5.10.0%22,n,z
> Please finalize those now & get +2 as soon as possible; We should get all 
> those
> in already for rc, which should be out next Thu!
>
> br.
> jani
>

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

[Development] Qt 5.10 beta 4 released

[Jani Heikkinen]

Hi all,

Qt 5.10 beta4 is out. Instructions how to get the release are here: 
https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

Current plan is to release Qt 5.10 rc next Thu as planned so please make sure 
all blockers from blocker list (https://bugreports.qt.io/issues/?filter=18957) 
is fixed immediately. Also make sure all open release  blockers are really 
visible in the list...

Diff to beta3 can be found as an attachment.

br,
Jani Heikkinen
Release Manager




qt5.10-beta3-delta-beta4-commits
Description: qt5.10-beta3-delta-beta4-commits
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] MAINTAINERS, your action needed: Qt change files

[Jani Heikkinen]

Hi all,

We are still missing +2 from 3 Qt 5.9.3 changes files:

- https://codereview.qt-project.org/#/c/210114/ (qt/qtx11extras)
- https://codereview.qt-project.org/#/c/210097/ (qt/qtwebchannel)
- https://codereview.qt-project.org/#/c/210104/ (qt/qtbase)

And in 5.10.0 situation is much worse, see 
https://codereview.qt-project.org/#/q/message:%22changes+file+for+Qt+5.10.0%22,n,z
Missing:
-qt/qtbase
-qt/qtx11extras
-qt/qtlocation  
-qt/qt3d
-qt/qtvirtualkeyboard
-qt/qtdoc
-qt/qtwebsockets
-qt/qtscxml
-qt/qttools
-qt/qtwebengine
-qt/qtwebchannel
-qt/qtsensors
-qt/qtconnectivity
-qt/qtwinextras
-qt/qtpurchasing
-qt/qtdeclarative

br,
Jani

> -Original Message-
> From: Jani Heikkinen
> Sent: perjantai 10. marraskuuta 2017 7.57
> To: development@qt-project.org
> Subject: MAINTAINERS, your action needed: Qt change files
> 
> Hi all,
> 
> We have still missing quite many +2 from 5.9.3 change files, see
> https://codereview.qt-project.org/#/q/message:%22file+for+Qt+5.9.3%22,n,z
> - qt/qtx11extras
> - qt/qt3d
> - qt/qtgraphicaleffects
> - qt/qtwebchannel
> - qt/qtwebview
> - qt/qtpurchasing
> - qt/qtscxml
> - qt/qtwebengine
> - qt/qtlocation
> - qt/qtdeclarative
> - qt/qtbase
> 
> We really need these in now to be able to get Qt 5.9.3 out during next week!
> 
> And there is already initial change files for Qt 5.10.0, see 
> https://codereview.qt-
> project.org/#/q/message:%22changes+file+for+Qt+5.10.0%22,n,z
> Please finalize those now & get +2 as soon as possible; We should get all 
> those
> in already for rc, which should be out next Thu!
> 
> br.
> jani
> 

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

[Development] HEADS-UP: Branching '5.10.0' from '5.10' completed

[Jani Heikkinen]

Hi all,

We have finally completed branching from '5.10' -> '5.10.0'.

So from now on all changes targeted to Qt 5.10.0 release must be done in 
'5.10.0' and '5.10' is for Qt 5.10.1. 
And please remember, no any nice-to-haves in '5.10.0' anymore. 

Plan is to create Qt 5.10 RC as soon as possible, after 
a) merge from 5.9.3 is completed
b) all changes files are in and 
c) every blocker from blocker list 
(https://bugreports.qt.io/issues/?filter=18957) have a fix in '5.10.0'. 

br,
Jani

From: Jani Heikkinen
Sent: Tuesday, November 7, 2017 7:41 PM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: HEADS-UP: Branching '5.10.0' from '5.10' started

Hi all,

We have soft branched '5.10.0' from '5.10'. Please start using '5.10.0' for new 
changes targeted to Qt 5.10.0 release. Final downmerge from '5.10' to '5.10.0' 
will happen Monday 13th November so there should be enough time to finalize 
ongoing changes in '5.10' and start using '5.10.0' for new ones.



We are targeting to release Qt 5.10.0 rc immediately after branching is 
finalized (rc target 16th November) so please make sure all blockers are fixed 
immediately. Qt 5.10.0 blocker list here: 
https://bugreports.qt.io/issues/?filter=18957



We (release team) will start creating initial change files for Qt 5.10.0 now. 
So Maintainers: Please finalize those initial ones immediately when available.



br,

Jani Heikkinen

Release Manager

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

[Development] Qt 5.10 beta 3 released

[Jani Heikkinen]

Hi all,

Qt 5.10 beta3 is out. Instructions how to get the release are here: 
https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

So please test the packages and make sure all issues which must be fixed before 
final Qt 5.10.0 release are visible in rc blocker list 
(https://bugreports.qt.io/issues/?filter=18957#)

Diff to beta2 can be found as an attachment.

br,
Jani Heikkinen
Release Manager







qt5.10-beta2-delta-beta3-commits
Description: qt5.10-beta2-delta-beta3-commits
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HEADS-UP: Branching '5.9.3' started

[Jani Heikkinen]

Hi all,
 
We have soft branched '5.9.3' from '5.9'. So please start using '5.9.3' for new 
changes targeted to Qt 5.9.3 release. Final downmerge from '5.9' to '5.9.3' 
will happen Wed 8th November so there should be enough time to finalize ongoing 
changes in '5.9' and start using '5.9.3' for new ones. 

We are targeting to release Qt 5.9.3 as soon as possible so please make sure 
all blockers are fixed immediately. Qt 5.9.3 blocker list here: 
https://bugreports.qt.io/issues/?filter=18995

We (release team) will start creating initial change files for Qt 5.9.3 now. So 
Maintainers: Please finalize those initial ones immediately when available. We 
need those now really soon to be able to proceed with final release.

br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] MAINTAINERS, your action needed: Qt change files

[Jani Heikkinen]

Hi all,

We have still missing quite many +2 from 5.9.3 change files, see 
https://codereview.qt-project.org/#/q/message:%22file+for+Qt+5.9.3%22,n,z
- qt/qtx11extras
- qt/qt3d
- qt/qtgraphicaleffects
- qt/qtwebchannel
- qt/qtwebview
- qt/qtpurchasing
- qt/qtscxml
- qt/qtwebengine
- qt/qtlocation
- qt/qtdeclarative
- qt/qtbase

We really need these in now to be able to get Qt 5.9.3 out during next week!

And there is already initial change files for Qt 5.10.0, see 
https://codereview.qt-project.org/#/q/message:%22changes+file+for+Qt+5.10.0%22,n,z
Please finalize those now & get +2 as soon as possible; We should get all those 
in already for rc, which should be out next Thu!

br.
jani


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

[Development] MAINTAINERS, your action needed: Qt 5.9.3 change files

[Jani Heikkinen]

Hi all,

There is still quite many changes files under construction, see 
https://codereview.qt-project.org/#/q/message:%22file+for+Qt+5.9.3%22,n,z
Please finalize ongoing ones now; we are targeting to get Qt 5.9.3 out during 
next week so we need to get final content in as soon as possible.

+2 still missing:
- qt/qtlocation
- qt/qtscxml
- qt/qtx11extras
- qt/qt3d
- qt/qtdoc
- qt/qtwebsockets
- qt/qtbase
- qt/qtgraphicaleffects
- qt/qtwebchannel
- qt/qtwebview
- qt/qtwebengine
- qt/qtwayland
- qt/qtpurchasing
- qt/qtdeclarative

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

[Development] HEADS-UP: Branching '5.9.3' completed

[Jani Heikkinen]

Hi,

Branching from '5.9' to '5.9.3' is now completed. From now on '5.9' is for 
changes targeting to '5.9.4' release.

Plan is to get remaining Qt 5.9.3 changes files in '5.9.3' as well as possible 
fixes for open blockers & then get the Qt 5.9.3 release out. Target for the 
release is week 46 so please finalize ongoing changes files now. 

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Wednesday, November 1, 2017 3:09 PM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: [Development] HEADS-UP: Branching '5.9.3' started

Hi all,

We have soft branched '5.9.3' from '5.9'. So please start using '5.9.3' for new 
changes targeted to Qt 5.9.3 release. Final downmerge from '5.9' to '5.9.3' 
will happen Wed 8th November so there should be enough time to finalize ongoing 
changes in '5.9' and start using '5.9.3' for new ones.

We are targeting to release Qt 5.9.3 as soon as possible so please make sure 
all blockers are fixed immediately. Qt 5.9.3 blocker list here: 
https://bugreports.qt.io/issues/?filter=18995

We (release team) will start creating initial change files for Qt 5.9.3 now. So 
Maintainers: Please finalize those initial ones immediately when available. We 
need those now really soon to be able to proceed with final release.

br,
Jani Heikkinen
Release Manager
___
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] HEADS-UP: Branching '5.10.0' from '5.10' started

[Jani Heikkinen]

Hi all,

We have soft branched '5.10.0' from '5.10'. Please start using '5.10.0' for new 
changes targeted to Qt 5.10.0 release. Final downmerge from '5.10' to '5.10.0' 
will happen Monday 13th November so there should be enough time to finalize 
ongoing changes in '5.10' and start using '5.10.0' for new ones.



We are targeting to release Qt 5.10.0 rc immediately after branching is 
finalized (rc target 16th November) so please make sure all blockers are fixed 
immediately. Qt 5.10.0 blocker list here: 
https://bugreports.qt.io/issues/?filter=18957



We (release team) will start creating initial change files for Qt 5.10.0 now. 
So Maintainers: Please finalize those initial ones immediately when available.



br,

Jani Heikkinen

Release Manager

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

[Development] Qt 5.10.0 RC3 out

[Jani Heikkinen]

Hi,

We have released Qt 5.10.0 RC3 today. Delta to RC2 as an attachment.

With my current knowledge this should be now final Qt 5.10.0 content which we 
are planning to release this Thursday (if all still ok according to tests).
Instructions how to get the release are here: 
https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

br,
Jani






qt5.10-rc2-delta-rc3-commits
Description: qt5.10-rc2-delta-rc3-commits
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.10.0 and Qt Creator 4.5.0 released

[Jani Heikkinen]

Hi everyone!

I am happy to announce that Qt 5.10.0 and Qt Creator 4.5.0 are released today.

More information about releases can be found from blog posts: 
Qt 5.10.0: http://blog.qt.io/blog/2017/12/07/qt-5-10-released/
Qt Creator 4.5.0: http://blog.qt.io/blog/2017/12/07/qt-creator-4-5-0-released/

Big thanks to everyone involved!

br,
Jani Heikkinen
Release Manager
The Qt Company




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

[Development] Qt 5.10 Beta2 available

[Jani Heikkinen]

Hi all,

Qt 5.10 beta2 is now available. Instructions how to get the release are here: 
https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

Please take a tour and and test the release. And please make sure all issues 
which must be fixed before final Qt 5.10.0 release are visible in rc blocker 
list (https://bugreports.qt.io/issues/?filter=18957#)

Diff to first beta can be found as an attachment.

br,
Jani Heikkinen
Release Manager






qt5.10-beta1-delta-beta2-commits
Description: qt5.10-beta1-delta-beta2-commits
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Stop delivering 32 bit MinGW binaries from 5.12 ->

[Jani Heikkinen]

Hi all,

There is open suggestion (https://bugreports.qt.io/browse/QTBUG-35288) to start 
delivering MinGW 64 bit pre-built binaries. This has been requested several 
times in mails, blog comments etc. We have discussed this earlier, last time 
with Qt 5.10 where I proposed that we could replace 32 bit MinGW with 64 bit 
one. But at that time we weren't ready for that. And it seems 32 bit MinGW 
package is still quite widely used, see 
http://lists.qt-project.org/pipermail/development/2017-December/031674.html .

With Qt 5.11 it seems we can finally drop MSVC2013 so we could "temporarily" 
add MinGW 64 bit pre-build binaries in our packages in addition to 32 bit ones 
and remove 32 bit MinGW pre-built binaries from 5.12 onwards. Making this 
decision now would complete this discussion finally and still give users time 
to move from 32 bit to 64 bit ones...

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

[Development] Qt 5.11.0 RC released

[Jani Heikkinen]

Hi,

We have released Qt 5.11.0 RC today. It is still online delivery only and you 
can get it via online installer as an update to existing installation or just 
doing fresh installation & selecting 5.11 rc from 'preview' section. Delta to 
beta4 release can be found as an attachment.

Target is to release these packages as Qt 5.11.0 22nd of May; a bit earlier 
than originally planned. So please inform me immediately if there is something 
badly broken. But remember: We won't do rc2 without really good reasons and if 
we need to release rc2 we will take in only fix for issue(s) which is causing 
rc2 and nothing else. So please don't try to push anything else in '5.11.0' 
anymore.

br,
Jani Heikkinen
Release Manager




qt5.git
41369b628203a0400a5e81184b2aa38e44ab5350 Install the MinGW build of libclang
c5ddbdb86b837fcdd406d12e66d8193c991bdede Update clang version to 6.0
795981e7205752aa3007fa14e13b7d0e78937261 Provisioning: openSUSE-42.3: Install 
libpulse-devel
6a06c4b4fe7fad6595252ac035fc0c05627b62c6 Revert "Install Python 2.7.13 to RHEL 
with pip"
24e1a15d40c02d5cd47644d37f713182830dfb4f Adjust submodule branches
qt3d:
43cebede39c9340c29bad6c6a78b76446d54c0db Avoid locking up on Radeon
7f0bdc21a8f1a5fbe2afdba61f037a71f00c1d61 Remove race in texture data upload
dcc7f1548425c2a8cabad3282b98939f05cc2513 gltf sceneloader: request 
mirrored=false for textures
ee47bb003b7f3e104993c46c7d68a44fc466925b Add changes file for Qt 5.11.0
f3c36a720abefad17d7cf0cb84a9f5a8ab9c2984 Animation: Make a fuzzy comparison 
when verifying cubic roots
3e82b9bf123f8e2da962b13121391ae2202424c9 Doc: Remove non-existent license file 
from qt_attribution.json
85efeb9951a9e6a028043f7b6ee8ea14f44faf9c Doc: Use the correct module command 
for QML types
5eaa6dae7eccd6519149dd9869fe1fae9f73bc10 Make sure we could lock the surface 
before querying its size
qtactiveqt:
9f2d3d9c5cfd1a23e92f5eaafd3c6833202b48c7 Add changes file for Qt 5.11.0
qtandroidextras:
5d54ecc1c8e58d2339871141e6bd769f340c4e96 Add changes file for Qt 5.11.0
qtbase:
a7863a58545a6c59eaf16f36905efcbf0e4f94f9 Add changes file for Qt 5.11.0
8863b8f24fc0751d9b8015b7f1344f76942dbb82 QSysInfo: Correct the \since for 
{machine,boot}UniqueId()
e46f9d68d8a8cc75c011fb304f064b927a784d56 syncqt: fix CamelCase aliases for 
injected headers
967bb3f0d8d8c65bd1e09011d9daac21ab51b585 syncqt: don't write INJECTED_*HEADERS
8c57663ed21855ad6b888bd01785b7f4e9251ae6 Fix documentation of 
setBackendConfigurationOption
c579a77f841ed44df25553972f8807110c55808d Document libdbus-1 code in Qt D-Bus
941db4e0bb3170b6bc3cf775f150a226754e6285 Doc: Update QtConcurrent::mapped 
example snippet
0c51b832f59d536513eaa85732bc02ad72b99455 Also support reset notification on 
non-nvidia
370cd37ceabc6a27f4140a35180502eed745b5f2 Manual shortcut test: Arrange in 
QGridLayout
30874fb2df83b21138860d7470a343221f7de6cb qmake: fix sdk resolution on macos
34e34f22097c87e8e937d72117d83d8c572bbea4 iOS: Use the non deprecated 
application:openURL function
8496a5503e236ac2eb839cf62a01d8a4789b QToolTip: Hide tooltip on key event on 
macOS
0c936d74118a31dcee777a3a4a8938590e79c334 QCocoaPlatformTheme: Fix tooltip 
background color
e991fd480242a1148a9988e7830a8e77afc90e33 QMacStyle: Fix SC_ComboBoxEditField 
rect
85cb183488a821a23a15710dc610dd0e506f72f5 QMacStyle: Fix appearance of selected 
inactive tab bar button
48900145a4e62db95dee812a1d9ac6331e19bc4b QMacStyle: Clean up code, remove dead 
bits
be4eaca053eba747c0458e37ce68ae3db1e6a288 Do not ignore MenuItem on macOS
c6ee1899eaa50dae56c07b6c4b3490cc5aeb60e6 Blacklist tst_QWindow::isActive on 
Ubuntu
8caf9e6b180eeb7e6668a64694339dac2265b4d0 iOS: Allow building QML based test 
cases
3520329937ca860a14bc57e3a12b580aa5e03482 Doc: link to QEnableSharedFromThis 
from QSharedPointer docs
e0e1c7ec2da121fa2b3acc8e76eb96e959954608 iOS: Trigger manual layout of root 
view controller when coming out of background
a75f25a43fd4bc5dab659dfc8d79a120258cec5f Fix runtime platform detection on 
Apple platforms
3697366642f05dd9239f730b48feea165f411ce6 QSplitter: fix doc for widget() and 
handle()
99e52d89fec67e353e3ad8ac065268cd4c76e853 Compile when using 
-no-feature-networkinterface
9899c29daf3f867f02f4b5f920d50e877ec3f3c3 Don't ignore the shortcut when the 
QMenuBar is parentless
2b5587d901a0cc23749bf27a923d50bf0e5860d3 Use placeholder for year in header.* 
files
18ea6a6d3c3020a64a6343ac3b778c48338883c1 Remove LICENSE.GPLv3, LICENSE.LGPLv21, 
LGPL_EXCEPTION.txt
215e0f35d05d26967711e049965415cc0c2a5796 tst_qdir: Fix absoluteFilePath for 
winrt
qtcanvas3d:
9d555f6d21d013c99079323a5085529631a5 Add changes file for Qt 5.11.0
qtcharts:
4f66d1ffeecd95b4bfb71536c42dea7450ed Add missing override
35523ecc002debb95414dfb78317814900dfa732 Add changes file for Qt 5.11.0
d3f9275cbaa6a6059298ec248dd28dd6ef065e51 LegendLayout::setDettachedGeometry(): 
Remove unused variable
qtconnectivity:
43f063427a3ffc62bd85237801b28c9f9826d562 Add changes file

[Development] HEADS UP: Branching from '5.9' to '5.9.6' started

[Jani Heikkinen]

Hi,

We have soft branched '5.9.6' from '5.9' already today. This was done a bit 
earlier than informed but don't worry; final downmerge from '5.9' to '5.9.6' 
will happen Tue 22.5.2018 as planned. So there is now plenty of time to 
finalize ongoing changes in '5.9' and start using '5.9.6' for new changes 
targeted to Qt 5.9.6 release. Plan is to get Qt 5.9.6 out at the beginning of 
June

br,
Jani


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

[Development] Qt 5.11.0 RC2 out

[Jani Heikkinen]

Hi,

We have released Qt 5.11.0 RC2 today. Delta to RC(1) release can be found as an 
attachment.
We are still targeting to release Qt 5.11.0 Tue 22nd May as planned

br,
Jani
qt5.git
d75411d6e560fcec1ab36395e88b1baf26c4cb69 Fix linking of qdoc against an 
external libclang (part 1)
qt3d:
15e863517ea37ca7ba6bcb75b078272eddbc5d37 Remove erronous entry about 
QFragmentOutput in the changelog
qtbase:
6eef81ee1c82f934e14d47047d8b6103b8755321 QFileSystemEngine: don't try to use 
statx(2) if SYS_statx isn't defined
qtdoc:
0d097a6995be7498b67b1586f8b2ebdc2cef26a3 Fix whats new docs for Qt 5.11
8a0244d3f46c1eb9904d9da7e741bb2e05ca3f3d Remove the qtcluster demo
qtserialbus:
c66a364cf34b4945208f07362deabe0020e5b596 Fix compilation with MSVC 2017
qttools:
a42d3f2ac4b910ecc910ff144191cb729a745c9a Fix logic for choosing static or 
dynamic libclang linkage
36e7b1925e2ff2df167280eb3592b99697a1234d Allow to link qdoc dynamically to 
libclang
qtwebengine:
28e0320235d33f00c6c141a549dc0553ee0043a5 Update Chromium
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.11.0 released

[Jani Heikkinen]

Hi everyone!

I am happy to announce that Qt 5.11.0 is released today, see 
http://blog.qt.io/blog/2018/05/22/qt-5-11-released/
At this time we were ready slightly before originally estimated; big thanks to 
everyone involved!

br,
Jani Heikkinen
Release Manager
The Qt Company
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HEADS UP: Branching from '5.9' to '5.9.6' completed

[Jani Heikkinen]

Hi,

Branching from '5.9' -> '5.9.6' now done and '5.9' is for Qt 5.9.7.  So all 
changes targeted to Qt 5.9.6 must be done in '5.9.6' from now on.
Target is to create Qt 5.9.6 "rc" soon, test it and if all OK release Qt 5.9.6 
at the beginning of June.  So please make sure all release blockers are visible 
in 5.9.6 blocker list (https://bugreports.qt.io/issues/?filter=19339)

br,
Jani

> -Original Message-
> From: Development <development-bounces+jani.heikkinen=qt.io@qt-
> project.org> On Behalf Of Jani Heikkinen
> Sent: keskiviikko 9. toukokuuta 2018 14.01
> To: development@qt-project.org
> Cc: releas...@qt-project.org
> Subject: [Development] HEADS UP: Branching from '5.9' to '5.9.6' started
> 
> Hi,
> 
> We have soft branched '5.9.6' from '5.9' already today. This was done a bit
> earlier than informed but don't worry; final downmerge from '5.9' to '5.9.6'
> will happen Tue 22.5.2018 as planned. So there is now plenty of time to
> finalize ongoing changes in '5.9' and start using '5.9.6' for new changes
> targeted to Qt 5.9.6 release. Plan is to get Qt 5.9.6 out at the beginning of
> June
> 
> br,
> Jani
> 
> 
> ___
> 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] Cleaning old development releases from download.qt.io

[Jani Heikkinen]

Hi!

Disk usage in download.qt.io is quite huge (~1.5 TB) at the moment and it is 
causing problems for mirrors and mirroring. We are cleaning up unnecessary 
stuff from there and one thing to remove is old qt pre-releases (snapshots, 
alpha, beta and rc releases)  from 
http://download.qt.io/development_releases/qt/ . I have already hide those old 
ones but before deleting those permanently I want to get confirmation if that 
is really OK; those pre-releases aren't available in 
http://download.qt.io/archive/qt. But official releases are there of course and 
that's why I think it should be OK to remove those pre-releases. 

br,
Jani Heikkinen
Release Manager


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

Re: [Development] Qt public release build configuration

[Jani Heikkinen]

Hi.

Unfortunately it isn't that easy to figure out but the data is available; you 
just need to know from where to search it :D

Configure options can be found from (qtbase) build log, from qt5.git 
integration. E.g for 5.6.3 
here:https://testresults.qt.io/coin/integration/qt/qt5/tasks/1505476672
and for 5.9.5 here: 
https://testresults.qt.io/coin/integration/qt/qt5/tasks/1523412986

And SW details here: https://wiki.qt.io/Qt_5.6_Tools_and_Versions & 
https://wiki.qt.io/Qt_5.9_Tools_and_Versions

br,
Jani


From: Development  on 
behalf of Taras Kushnir 
Sent: Thursday, May 24, 2018 10:40 AM
To: development@qt-project.org
Subject: [Development] Qt public release build configuration

Hello

I'm going to build Qt from source for the first time in order to fix some 
issues in Quick Controls. I will need to rebuild Qt on Windows x86_64, OS X and 
Linux. Where can I find exact `configure` options used to create public 
releases 5.6.3 and 5.9.5 as well as exact versions of dependencies used to 
create the release (ICU etc.) and environments (OS version, frameworks, Windows 
Kit etc.)?

Thank you,
Taras Kushnir.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Cleaning old development releases from download.qt.io

[Jani Heikkinen]

> -Original Message-
> From: Development <development-bounces+jani.heikkinen=qt.io@qt-
> project.org> On Behalf Of Thiago Macieira
> Sent: torstai 24. toukokuuta 2018 15.23
> To: development@qt-project.org
> Subject: Re: [Development] Cleaning old development releases from
> download.qt.io
> 
> On Thursday, 24 May 2018 04:27:38 -03 Jani Heikkinen wrote:
> > Hi!
> >
> > Disk usage in download.qt.io is quite huge (~1.5 TB) at the moment and
> > it is causing problems for mirrors and mirroring. We are cleaning up
> > unnecessary stuff from there and one thing to remove is old qt
> > pre-releases (snapshots, alpha, beta and rc releases)  from
> > http://download.qt.io/development_releases/qt/ . I have already hide
> > those old ones but before deleting those permanently I want to get
> > confirmation if that is really OK; those pre-releases aren't available
> > in http://download.qt.io/archive/qt. But official releases are there
> > of course and that's why I think it should be OK to remove those pre-
> releases.
> 
> Snapshots yes. For the others, remove binaries but please keep the sources.

Is sources really needed to be stored? Those pre-releases are also tagged in 
the git so everyone can get those from there if needed. And by default users 
should user official releases which are of course still available under 
"Official Release" or "Archive" 

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

[Development] Maintainers, your action needed: Qt 5.11.1 changes files

[Jani Heikkinen]

Hi,

Initial ones here: 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.11.1%22,n,z

Please do needed updates & get approval as soon as possible; We need to get 
these in soon to be able to keep our release schedule (final packages next 
week, release 19.6.2018)

br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HEADS-UP: Branching from '5.11' -> '5.11.1' ready

[Jani Heikkinen]

Hi,

We have now done final downmerge from '5.11' -> '5.11.1'. So from now on all 
changes targeted to Qt 5.11.1 release must be done in '5.11.1' and '5.11' is 
for Qt 5.11.2 release.

Target is to create final Qt 5.11.1 packages Thu 14.6.2018 so please make sure 
fixes for all release blockers are in Wed 13.6.2018 EOB (latest, we will do 
final packages earlier if all fixes available). And please make sure that 
changes files for Qt 5.11.1 will be finalized immediately when initial ones 
available; target is to create those tomorrow.

And once again: Please do not push any nice to have fixes in '5.11.1' anymore; 
Qt 5.11.2 will be done soon as well (end of August/beginning of September).

br,
Jani

> -Original Message-
> From: Jani Heikkinen
> Sent: perjantai 1. kesäkuuta 2018 14.39
> To: development@qt-project.org
> Cc: releas...@qt-project.org
> Subject: HEADS-UP: Branching from '5.11' -> '5.11.1' started
> 
> Hi,
> 
> We have soft branched 5.11.1 from 5.11 today. Target is to finalize branching 
> &
> have final downmerge from '5.11' -> '5.11.1' Thu 7.6.2018.
> 
> Please start using '5.11.1' for new changes targeted to Qt 5.11.1 release.
> 
> br,
> Jani Heikkinen
> Release Manager
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Merge and Integration status report

[Jani Heikkinen]

Actually at least 5.11.1 declarative integration failure is timeout in qtbase 
-> Linux QEMU (gcc-armv7) build. So the failure is different there (in case it 
helps anything)

br,
Jani

From: Development  on 
behalf of Simon Hausmann 
Sent: Thursday, June 14, 2018 10:32 AM
To: development@qt-project.org
Subject: Re: [Development] Merge and Integration status report

 Hi,


Thank you Liang for the report.


On top of that, qtdeclarative is not accepting any changes in the 5.9, 5.11, 
5.11.1 and dev branches right now.


Those who may have tried staging changes there may have noticed that they are 
failing in one of the tests that launch a separate process for testing the 
debugging integration, limited to Windows 10 (x86 and x86-64).


Until we've found the root cause or a suitable workaround, please don't stage 
changes to qtdeclarative.


I can't see any recent common changes to qtbase or declarative that apply to 
all _four_ branches, so I suspect this flaky issue was caused by something 
below those two modules.


I'll post an update here when we've figured it out (workaround or solution).


Simon


From: Development  on 
behalf of Liang Qi 
Sent: Thursday, June 14, 2018 9:18:32 AM
To: development@qt-project.org
Subject: [Development] Merge and Integration status report

Integrations

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

* qt5 5.11 integration failed from June 9
* * Issue: https://bugreports.qt.io/browse/QTBUG-68773 qtwayland build failed - 
can't find some headers
* * * https://codereview.qt-project.org/#/c/232288/ Robert Griebl has a fix, 
Oswald please help to review it.
* * Issue: https://bugreports.qt.io/browse/QTBUG-68741 
tst_QQmlDebuggingEnabler::qmlscene() failed
___
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] [Interest] Maintenance Tool network error (OSX)

[Jani Heikkinen]

Hi!
This issue should be fixed now. 

It would be better to report these kind of issues to Jira, to our internal 
release team ml (qt.team.relea...@qt.io) or to development ML 
(development@qt-project.org) in the future to make sure we will notice the 
issue immediately.

br,
Jani

From: Jason H 
Sent: Wednesday, May 30, 2018 6:26 PM
To: Jani Heikkinen
Cc: inter...@qt-project.org; fro...@tungware.se
Subject: Re: [Interest] Maintenance Tool network error (OSX)

Sure. For next time, is there a contact for similar issues we should use? Maybe 
the developer list?


> Sent: Wednesday, May 30, 2018 at 1:54 AM
> From: "Jani Heikkinen" 
> To: "inter...@qt-project.org" , "fro...@tungware.se" 
> 
> Subject: Re: [Interest] Maintenance Tool network error (OSX)
>
> Hi all,
>
> Thanks for notifying this. There seems to be some issue and some release 
> content is missing from download.qt.io. We will study & fix the issue as soon 
> as possible
>
> br,
> Jani
> 
> From: Interest  on 
> behalf of Henry Skoglund 
> Sent: Tuesday, May 29, 2018 7:18 PM
> To: inter...@qt-project.org
> Subject: Re: [Interest] Maintenance Tool network error (OSX)
>
> I'm getting it too.
>
> (No Qt installed before, downloaded Online installer: ok, login: ok, but
> cannot install any version of Qt today on my brand new Mac.
>
> Also get this error just now when I tried on a new Windows 10 PC (se
> picture #2).
>
> No Qt today :-(
>
> Rgrds Henry
>
> On 2018-05-29 17:18, Jason H wrote:
> > Not sure if anyone else is getting this...
> >
> >
> >
> > ___
> > Interest mailing list
> > inter...@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/interest
> >
>
> ___
> Interest mailing list
> inter...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HEADS-UP: Branching from '5.11' -> '5.11.1' started

[Jani Heikkinen]

Hi,

We have soft branched 5.11.1 from 5.11 today. Target is to finalize branching & 
have final downmerge from '5.11' -> '5.11.1' Thu 7.6.2018. 

Please start using '5.11.1' for new changes targeted to Qt 5.11.1 release.

br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] MAINTAINERS, Your actions needed: Qt 5.9.6 changes files

[Jani Heikkinen]

Hi!

Initial ones here: 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.6%22,n,z

Please do needed modifications now & get approval. We are targeting to get Qt 
5.9.6 out at the beginning of June so we need to get all these in asap

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

[Development] HEADS UP : Qt 5.10 string freeze

[Jani Heikkinen]

Hi,

As informed a week a go string freeze for Qt 5.10 is now in effect. So please, 
no changes to translatable strings from this point, unless approved by the 
documentation team.

br,
Jani

From: Jani Heikkinen
Sent: Thursday, October 19, 2017 12:39 PM
To: localizat...@qt-project.org
Cc: development@qt-project.org; releas...@qt-project.org
Subject: HEADS UP : Qt 5.10 soft string freeze

Hi all,

Qt 5.10 beta is out & work towards final release continues. One step on the way 
is String Freeze which should happen really soon to be able to minimize time 
needed between beta and RC. So let's start keeping the translatable strings as 
it is & fix remaining important issues. And let's have the official String 
Freeze for Qt 5.10 27th October 2017.

Br,
Jani Heikkinen
Release Manager




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

[Development] Qt 5.11 feature freeze is getting closer: New submodules in Qt 5.11?

[Jani Heikkinen]

Hi all,

There is only a bit more than a month to Qt 5.11 feature freeze, see 
https://wiki.qt.io/Qt_5.11_Release . So at this point we should already know if 
there will be some new submodule modules in Qt 5.11. We are doing packaging 
confs etc for 5.11 now so please inform me immediately if there will be some 
new in. And of course get the new submodule in qt5 as soon as possible; those 
really needs to be in before we start soft branching!

br,
Jani




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

[Development] Changes files for Qt 5.9.4

[Jani Heikkinen]

Initial ones are here: 
https://codereview.qt-project.org/#/q/branch:5.9.4+message:%22Add+changes+file+for+Qt+5.9.4%22,n,z

Please finalize as soon as possible; we are trying to get release out ~Mid 
January

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

[Development] Branching '5.9.4' from '5.9' done

[Jani Heikkinen]

Hi!

Branching from '5.9' to '5.9.4' is now ready. So all changes targeted to Qt 
5.9.4 release must be done in '5.9.4' and '5.9' is for Qt 5.9.5 from now on

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Friday, December 22, 2017 4:26 PM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: [Development] Branching '5.9.4' from '5.9' started

Hi all,

We have now soft branched '5.9.4' from '5.9' so please start using '5.9.4' for 
new changes targeting Qt 5.9.4 release. Target is to do final downmerge from 
'5.9' -> '5.9.4' and finalize branching at the beginning of January 2018 so 
there should be enough time to finalize ongoing ones in '5.9'. Target is to 
release Qt 5.9.4 ~ mid January.

br,
Jani Heikkinen
Release Manager

___
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] Qt 5.9.4 released

[Jani Heikkinen]

Hi,

We have released Qt 5.9.4 today, see 
http://blog.qt.io/blog/2018/01/23/qt-5-9-4-released/

Big thanks for everyone involved!

br,
Jani Heikkinen
Release Manager



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

[Development] Branching from 'dev' to '5.11' started

[Jani Heikkinen]

Hi,

We have now soft branched '5.11' from dev so please start using '5.11' now. Qt 
5.11 feature freeze and final downmerge from 'dev' to '5.11' will happen Wed 
31.1.2018 so there is still enough time to finalize ongoing changes in 'dev'.

And let's keep the feature freeze now, it is key enabler for us to be able to 
keep the release schedule. So it is time to check if new feature can be 
finalized early enough for the feature freeze. If not then we should just 
postpone it to Qt 5.12 instead of trying to get it in Qt 5.11. 

br,
Jani Heikkinen
Release Manager



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

[Development] New Qt snapshots available

[Jani Heikkinen]

Hi,

We have published online snapshots for Qt 5.10.1 and Qt 5.11 Alpha. You can 
find those from 'Preview' node in online installer

br,
Jani


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

[Development] Branching from '5.10' to '5.10.1' (almost) ready

[Jani Heikkinen]

Hi all,

Final downmerge from '5.10' -> '5.10.1' is now (almost) done; only webengine 
downmerge is still missing and will be done later today. So from now on '5.10' 
is for Qt 5.10.2 and all changes targeted to Qt 5.10.1 must be done in '5.10.1'.

And please remember: Target is to get Qt 5.10.1 as soon as possible so no any 
nice to haves in '5.10.1' from now on: we will accept only fixes for release 
blockers. 

br,
Jani

From: Jani Heikkinen
Sent: Monday, January 29, 2018 7:54 AM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: Branching from '5.10' to '5.10.1' started

Hi all,

We have soft branched '5.10.1' from '5.10' on Friday. Target is to do final 
downmerge from '5.10' -> '5.10.1' Friday 2.2.2018. Please finalize ongoing 
changes in '5.10' and start using '5.10.1' for new changes.
First Qt 5.10.1 snapshot is already under testing and we are targeting to get 
Qt 5.10.1 out as soon as possible after final downmerge. So please minimize 
changes for Qt 5.10.1 from now on to get it out quickly!

br,
Jani




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

Re: [Development] Final downmerge from dev to '5.11' delayed

[Jani Heikkinen]

> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: lauantai 3. helmikuuta 2018 4.33
> To: development@qt-project.org
> Subject: Re: [Development] Final downmerge from dev to '5.11' delayed
> 
> On Wednesday, 31 January 2018 02:57:21 PST Jani Heikkinen wrote:
> > Hi all,
> >
> > Most probably there is changes in 'dev' which should be in Qt 5.11 but
> > which aren't yet integrated because of CI issues recently. That's why
> > let's postpone final downmerge (and Qt 5.11 FF) to the end of this
> > week. New plan is to have final downmerge from 'dev' to '5.11' (and Qt
> > 5.11 FF) Monday
> > 5.2.2018 (morning).
> >
> > Hoping CI will behave now and you have enough time to get needed
> > changes in before final downmerge. And remember: This delay is just to
> > get changes in, not for getting extra time for new implementation!
> 
> So are we frozen?

We are kind of semi frozen :) I meant to say that please don't use that extra 
time to push some new things in anymore. If those were ready (but not in 
because of ci issues) at original FF date then it is of course OK to integrate 
those in dev now. But if not then just postpone those in Qt 5.12 instead.

Final downmerge from dev to 5.11 will happen on Monday morning so all changes 
in dev before that will end up in Qt 5.11

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

[Development] Qt branches & proposal how to continue with those

[Jani Heikkinen]

Hi,

We have currently really many branches open:
- 5.6
- 5.9
- 5.10
- 5.10.1
- 5.11
- dev

In my opinion this is too much to handle effectively, especially because there 
is many branches in stable mode (see 
http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.rst). Currently '5.6' is 
in 'strict' mode and  '5.9', 5.10' & '5.11' are in stable... I think we need to 
change that to be able to work efficiently & get releases out. 

So I am proposing following changes starting from 1st Feb 2018:

- '5.6' will move in 'very strict' mode 
- '5.9' will move in 'strict' mode. So no direct submissions anymore, just 
cherry picks from stable
- '5.10' will be closed and Qt 5.10.1 will be the final release from Qt 5.10 
series (5.6 and 5.9 are LTS branches so we shouldn't keep Qt 5.10 active too 
long)
- '5.11' will be to one and only stable branch

br,

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

[Development] Branching from '5.10' to '5.10.1' started

[Jani Heikkinen]

Hi all,

We have soft branched '5.10.1' from '5.10' on Friday. Target is to do final 
downmerge from '5.10' -> '5.10.1' Friday 2.2.2018. Please finalize ongoing 
changes in '5.10' and start using '5.10.1' for new changes. 
First Qt 5.10.1 snapshot is already under testing and we are targeting to get 
Qt 5.10.1 out as soon as possible after final downmerge. So please minimize 
changes for Qt 5.10.1 from now on to get it out quickly!

br,
Jani




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

Re: [Development] Qt branches & proposal how to continue with those

[Jani Heikkinen]

> -Original Message-
> From: Ville Voutilainen [mailto:ville.voutilai...@gmail.com]
> Sent: maanantai 29. tammikuuta 2018 9.50
> To: Jani Heikkinen <jani.heikki...@qt.io>
> Cc: development@qt-project.org
> Subject: Re: [Development] Qt branches & proposal how to continue with those
> 
> On 29 January 2018 at 08:59, Jani Heikkinen <jani.heikki...@qt.io> wrote:
> > - '5.6' will move in 'very strict' mode
> > - '5.9' will move in 'strict' mode. So no direct submissions anymore,
> > just cherry picks from stable
> > - '5.10' will be closed and Qt 5.10.1 will be the final release from
> > Qt 5.10 series (5.6 and 5.9 are LTS branches so we shouldn't keep Qt
> > 5.10 active too long)
> > - '5.11' will be to one and only stable branch
> 
> 
> The problem here is that there are bugfixes that need to go into 5.9 but 
> cannot
> go into 5.11, for a variety of reasons. We need to keep 5.9 open for direct
> submissions.

Hmm, I think putting '5.9' in cherry pick mode with this schedule is agreed way 
of working, see http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.rst 
And I don't see big issue there; amount of 5.9 specific fixes should be really 
minimal and if one really needed we can get that in without putting it first in 
stable: Cherry pick "mode" is more "way of working" & checks are included in 
sanity bot. And it can be overwritten if really needed.

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

Re: [Development] Qt branches & proposal how to continue with those

[Jani Heikkinen]

Hi,

So the decision how to proceed is done. Let's give everyone a while to finalize 
ongoing tasks and put the decision in effect after a week. 

So from 12.2.2018 ->
   - '5.9' will be in cherry-pick mode
   - '5.10' will be closed

We will make sure final merges from '5.9' -> '5.10' -> '5.11' will be done 
after that and then there will be merges only from '5.11' -> 'dev'

br,
Jani

From: Development  on 
behalf of Lars Knoll 
Sent: Monday, February 5, 2018 12:35 PM
To: Qt development mailing list
Subject: Re: [Development] Qt branches & proposal how to continue with those

Hi all,

Sorry for being a bit late with answering to this thread. Been first traveling 
and then was down with a flu last week.

Unfortunately, none of the options on the table will be 100% satisfying to 
everybody. This is basically because we have limits on how much work we can or 
should be doing getting different releases out, and different users have 
different preferences with regards to our branches.

I think that we’ll be long term best off, if we move Qt forward as quickly as 
we can. Qt 5.11 provides some significant new things over 5.10, so in the end 
we should prioritise finalising that branch and getting 5.11.0 out as quickly 
as we can. Less merging will free up people and CI capacity to focus on 5.11 
bug fixing and speed up turn around time to getting qt5.git integrations 
through.

This means we’ll go with something close to option 2b that Ossi outlined below:

* We put 5.9 in cherry-picking mode in line with QUIP 5.
* There is currently no 5.10.2 release planned. The main reason to do one would 
be to be an urgent security update. This means we also leave 5.10 branch behind 
and close it.
* If we have a larger security issue that deserves a release (and not just a 
patch) from 5.10, we can still do that from the branch on top of 5.10.1 (maybe 
doing a one time merge from 5.9 to 5.10 if we want those fixes as well)
* Instead we put our focus on getting 5.11 out as quickly as we can. Let’s 
branch now, create first alpha and then beta packages as quickly as possible. 
Not having to merge from 5.10 will ease this significantly. Getting 5.11 out 
quick will hopefully also make Webengine not fall too far/long behind upstream 
security patches.

Of course, we continue having regular releases from 5.9, but with it being in 
strict mode, the frequency of releases will maybe drop a bit (from every 6 
weeks currently to maybe every 8-10 weeks). Let’s also now plan for at least 
two patch level releases of 5.11 before 5.12 comes out.

Cheers,
Lars

> On 1 Feb 2018, at 15:53, Oswald Buddenhagen  wrote:
>
> On Thu, Feb 01, 2018 at 02:35:58PM +0100, Tuukka Turunen wrote:
>> So based on this Qt 5.9 should be in cherry pick mode next week. With
>> previous wording it should have been in cherry pick mode from 2.9.2017
>> onwards, which was way too soon (hence the change to QUIP5).
>>
> right.
>
>> What about Qt 5.10.2? This of course needs to be addressed after we
>> see how Qt 5.10.1 turns out to be. But provided Qt 5.10.1 is a good
>> release, I would like to put full focus into getting Qt 5.11.0 out
>> quickly and try to release Qt 5.11.1 in June already.
>>
> yes, but the point is that we can't change the policy retroactively. if
> 5.10.2 is an option, then 5.10 needs to stay open as the default target
> for fixes, and be forward-merged. this leaves us at two merges for a fix
> to reach dev.
> the same delay would occurr if we closed 5.10 and continued to merge
> from 5.9, which is why the discussion which one is more important
> emerged.
>
> this leaves us with three options:
> 1)
> - 5.9 goes to cherry-pick mode, essentially now.
> - 5.10 stays open until 5.11.0 is released.
>   - we should create 5.10.2 before the 5.11.0 release even if we don't
> intent to actually make a release, just so we have a mergable
> target branch (to avoid "illegal" 5.10 => 5.11.0 merges or
> cherry-picks).
> 2)
> - we just declare that there won't be 5.10.2 and close 5.10 after
>   5.10.1. potentially not user-friendly, but we've done it in the
>   past, and while releasing capacity isn't the limiting factor now,
>   forward-merging apparently is.
> 2a) we continue to forward-merge from 5.9.
> 2b) 5.9 goes to cherry-pick mode, which cuts out another merge step.
>
> note that 5.10 going to cherry-pick mode is specifically not an option,
> as stated previously.
>
> 1) seems most natural to 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 5.10.1 changes files

[Jani Heikkinen]

Hi,

Initial versions done, see 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.10.1%22+status:open,n,z

Maintainers: Please finalize & get '+2' as soon as possible

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

Re: [Development] Qt branches & proposal how to continue with those

[Jani Heikkinen]

> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Tuukka Turunen
> Sent: tiistai 30. tammikuuta 2018 23.38
> To: Konrad Rosenbaum ; development@qt-project.org
> Subject: Re: [Development] Qt branches & proposal how to continue with those
> 
> The item that has received comments both in favor and against is what to do
> with 5.10 now. I think that instead of closing 5.10, we could move it to 
> cherry
> pick mode, just like Qt 5.9 is. That allows putting the necessary fixes 
> there, but
> reduces the amount of needed merges a lot. It also allows to faster get all 
> the
> fixes merged up to dev, which is something we have struggled in the past.
> 
> With this approach we have full capability to make Qt 5.10.2 release, if one 
> is
> needed. We also continue to make Qt 5.9.x patch releases. We would have two
> branches open for direct submission: 5.11 and dev, and for each commit the
> lowest applicable branch can be chosen. For all such important fixes that need
> to be in Qt 5.9.x LTS releases or in the 5.10 branch, we use cherry picking.
> 

This is OK for me as well so +1 from my side

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

Re: [Development] Qt branches & proposal how to continue with those

[Jani Heikkinen]

> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Kevin Kofler
> Sent: maanantai 29. tammikuuta 2018 15.33
> To: development@qt-project.org
> Subject: Re: [Development] Qt branches & proposal how to continue with those
> 
> Simon Hausmann wrote:
> > In the light of that, I think it would be better to keep the LTS
> > branches open longer and stop doing patch releases for minor releases
> > that are not LTS.
> 
> -1 from a distro packager perspective. LTS just does not fit together with 
> fast-
> moving distributions, and we really need those bugfix releases for the 
> branches
> we ship.

I have to disagree there: We have already released 4 patch level releases for 
LTS 5.9 so it is actually moving quite fast.

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

[Development] Qt 5.10.1 changes files: MAINTAINERS, your action needed!

[Jani Heikkinen]

Hi,

Most of Qt 5.10.1 changes files are still under work, see 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.10.1%22,n,z

Please make sure those will be finalized & approved today; we need to get Qt 
5.10.1 final content in place now

Also please start updating known issues page for Qt 5.10.1 here: 
https://wiki.qt.io/Qt_5.10.1_Known_Issues

br,
Jani






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

[Development] Final downmerge from dev to '5.11' done

[Jani Heikkinen]

Hi!

Final downmerge from 'dev' to '5.11' is now done and Qt 5.11 FF is officially 
in effect. From now on 'dev' is for Qt 5.12 and we will continue finalizing Qt 
5.11 in '5.11'. 

Overall release schedule can be found from release wiki 
(https://wiki.qt.io/Qt_5.11_Release). Plan is to get alpha out as soon as 
possible; hoping that will happen earlier than planned. Target is to release it 
immediately after qt5.git integration succeed in '5.11' and when we have 
created and RTA tested needed packages.

Please update Qt 5.11 new features wiki 
(https://wiki.qt.io/New_Features_in_Qt_5.11) now.

br,
Jani

From: Jani Heikkinen
Sent: Wednesday, January 31, 2018 12:57 PM
To: Jani Heikkinen; development@qt-project.org
Cc: releas...@qt-project.org
Subject: Final downmerge from dev to '5.11' delayed

Hi all,

Most probably there is changes in 'dev' which should be in Qt 5.11 but which 
aren't yet integrated because of CI issues recently. That's why let's postpone 
final downmerge (and Qt 5.11 FF) to the end of this week. New plan is to have 
final downmerge from 'dev' to '5.11' (and Qt 5.11 FF) Monday 5.2.2018 (morning).

Hoping CI will behave now and you have enough time to get needed changes in 
before final downmerge. And remember: This delay is just to get changes in, not 
for getting extra time for new implementation!

br,
Jani

> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Jani Heikkinen
> Sent: torstai 25. tammikuuta 2018 8.58
> To: development@qt-project.org
> Cc: releas...@qt-project.org
> Subject: [Development] Branching from 'dev' to '5.11' started
>
> Hi,
>
> We have now soft branched '5.11' from dev so please start using '5.11' now. Qt
> 5.11 feature freeze and final downmerge from 'dev' to '5.11' will happen Wed
> 31.1.2018 so there is still enough time to finalize ongoing changes in 'dev'.
>
> And let's keep the feature freeze now, it is key enabler for us to be able to 
> keep
> the release schedule. So it is time to check if new feature can be finalized 
> early
> enough for the feature freeze. If not then we should just postpone it to Qt 
> 5.12
> instead of trying to get it in Qt 5.11.
>
> br,
> Jani Heikkinen
> Release Manager
>
>
>
> ___
> 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] Qt 5.10.1 and Qt Creator 4.5.1 released

[Jani Heikkinen]

Hi all,

We have released Qt 5.10.1 and Qt Creator 4.5.1 today, see

http://blog.qt.io/blog/2018/02/13/qt-5-10-1-released/

and

http://blog.qt.io/blog/2018/02/13/qt-creator-4-5-1-released/

Big thanks to everyone involved!

br,
Jani





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

[Development] Qt 5.11 Alpha released

[Jani Heikkinen]

Hi all,

We have release Qt 5.11 Alpha today, see 
http://blog.qt.io/blog/2018/02/20/qt-5-11-alpha-released/

Big thanks to everyone involved!

br,
Jani Heikkinen
Release Manager


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

[Development] Qt 5.11 Beta1 snapshot available

[Jani Heikkinen]

Hi,
First Qt 5.11 Beta1 snapshot available via online installer. Please take a tour 
to see what is working and what not

Have a nice weekend!

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

[Development] Branching '5.9.4' from '5.9' started

[Jani Heikkinen]

Hi all,

We have now soft branched '5.9.4' from '5.9' so please start using '5.9.4' for 
new changes targeting Qt 5.9.4 release. Target is to do final downmerge from 
'5.9' -> '5.9.4' and finalize branching at the beginning of January 2018 so 
there should be enough time to finalize ongoing ones in '5.9'. Target is to 
release Qt 5.9.4 ~ mid January.

br,
Jani Heikkinen
Release Manager

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

[Development] Qt 5.11.1 Released

[Jani Heikkinen]

Hi!

We have released Qt 5.11.1 today, see 
http://blog.qt.io/blog/2018/06/19/qt-5-11-1-released/

Big thanks to everyone involved!

br,
Jani Heikkinen
Release Manager



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

Re: [Development] Qt 5.12 feature freeze is getting closer

[Jani Heikkinen]

Hi all,

Kindly reminder: Feature freeze will be in effect after 3 weeks (20.8.2018). So 
please make sure all new features for Qt 5.12 are ready and in 'dev' early 
enough. And please notify me if there will be any new or any removed submodules 
for Qt5; at the moment i don't know any changes related to that since Qt 5.11

br,
Jani

From: Jani Heikkinen
Sent: Wednesday, June 20, 2018 1:14 PM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: Qt 5.12 feature freeze is getting closer

Hi all,

Only two months to Qt 5.12 feature freeze, see 
https://wiki.qt.io/Qt_5.12_Release. And summer vacations will take big part of 
that remaining period...

So at this point we should already know if there will be some new submodule 
modules in Qt 5.12. We are doing packaging confs etc for 5.12 now so please 
inform qt.team.relea...@qt.io (I am starting my vacation today) immediately if 
there will be some new in. And of course get the new submodule in qt5 as soon 
as possible; those really needs to be in before we start soft branching mid 
August!

br,
Jani

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

[Development] Qt 5.12 new features

[Jani Heikkinen]

Hi,

Qt 5.12 Feature Freeze will be in effect Mon 20th August and we should have 
already now pretty good understanding what is new in Qt 5.12. So please update 
5.12 new features page here: https://wiki.qt.io/New_Features_in_Qt_5.12

br,
Jani





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

Re: [Development] What are new features of Qt3D in Qt 5.12?

[Jani Heikkinen]

Hi,

As stated the page is still under construction so don't worry; I think there is 
something new in qt3d side as well

br,
Jani

From: Development  on 
behalf of Vincent Hui 
Sent: Friday, August 17, 2018 12:43 PM
To: Robert Loehning
Cc: development@qt-project.org
Subject: Re: [Development] What are new features of Qt3D in Qt 5.12?

According to https://wiki.qt.io/New_Features_in_Qt_5.12, there will be no new 
features in Qt3D?
I hope I am wrong.

Thanks,
Vincent


On Fri, 27 Jul 2018 at 18:55, Robert Löhning 
mailto:robert.loehn...@qt.io>> wrote:
Am 27.07.2018 um 05:23 schrieb Brett Gilio:
>
> Vincent Hui writes:>
>> What are new features of Qt3D in Qt 5.12? Will Rigid body and soft body
>> physics simulation be included?
>>
>> I hope there will be new features of Qt3D in Qt 5.12.
>
>
> Hello Vincent,
>
> Unless I am mistaken, there should be a Changelog available for a
> collection such modifications including feature additions available in
> the Qt3D git repository on the Qt website.
>
> Best
>
>

Hello Vincent, Brett,

these change logs do not exist yet for 5.12. They are usually written
shortly before the release.

When we will approach the release, you will find more and more
information on
https://wiki.qt.io/Qt_5.12_Release

Cheers,
Robert
___
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] Closing issues automatically with new keyword

[Jani Heikkinen]

>
>From: Development  on 
>behalf of Frederik Gladhorn 
>Sent: Tuesday, August 7, 2018 12:46 PM
>To: development@qt-project.org
>Subject: [Development] Closing issues automatically with new keyword
>
>Hi all,
>
>I've spend a bit of time writing a script that monitors gerrit and the git
>repositories to update JIRA statuses. It's not quite done yet, but getting
>there.
>Basically it should be able to set the fixed version and close tasks
>automatically.
>
>Assuming there is no major protest, I'll use "Fixes: QTBUG-123" as the keyword
>to trigger this.
>
>The plan is to update the fix versions and close the task as done when a line
>in the commit message starts with "Fixes:".
>If the issue is already closed (e.g. cherry-pick) it can add an additional fix
>version (e.g. 5.9.7).
>
>Note: Task-number will be used as before as "this is related to the issue in
>some way".
>
>Cheers,
>Frederik

Hi,

I see at least one problem there: If bug is affecting to several branches it 
will be closed when fix for first branch is done even in that case it shouldn't 
be closed until every branch has a fix...

Another concern or question is that in which phase we should close the bug; is 
it done immediately when fix is in or should it be done when fix is in the 
packages and someone can verify that fix is there and really fixes the 
problem... 

br,
Jani


___
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] Merge and Integration status report - 2018.08.13

[Jani Heikkinen]

> -Original Message-
> From: Development  project.org> On Behalf Of Liang Qi
> Sent: maanantai 13. elokuuta 2018 12.30
> To: development@qt-project.org
> Subject: [Development] Merge and Integration status report - 2018.08.13
> 
> Integrations
> 
> * qt5 5.11 integration is healthy, last one is yesterday, August 12
> 
> * qt5 dev, last one is August 11, excluding qtbase since August 8
> * * http://bugreports.qt.io/browse/QTBUG-69891
> tests/auto/quick/drawingmodes hanging
> Tor Arne is working on that. But if can't get fix soon, suggest to revert
> https://codereview.qt-project.org/#/c/235685/ for now, because there are
> about 20-30
> changes including a 5.11->dev merge in qtbase which are not integrated in
> qt5 dev yet.

As discussed earlier we should do reverts much easier to avoid blocking of 
other's work. We will start branching from 'dev' -> '5.12' today and we should 
get latest changes in qtbase as soon as possible as well.  So in my opinion we 
should just do the revert & bring the change back when fix is available.

br,
Jani



> 
> Merges - healthy!
> 
> Thanks Simon and Edward for their work during July!
> 
> -- Liang
> ___
> 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] HEADS-UP: Branching from 'dev' to '5.12' started

[Jani Heikkinen]

Hi!

We have soft branched '5.12' from 'dev' today. We are planning to have final 
downmerge and Qt 5.12 Feature Freeze Monday 20.8.2018. So there is still time 
to finalize ongoing task in 'dev' and start using '5.12' for new changes 
targeted to Qt 5.12 release.

br,
Jani Heikkinen
Release Manager



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

[Development] HEADS UP: Branching from '5.11' to '5.11.2' started

[Jani Heikkinen]

Hi,

We have soft branched '5.11.2' from '5.11' today. Target is to finalize 
branching Fri 24th August 2018. So please finalize ongoing changes in '5.11' 
and start using '5.11.2' for new changes targeted to Qt 5.11.2 release

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

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

[Jani Heikkinen]

Hi,

Branching from 'dev' to '5.12' is now complete and Qt 5.12 Feature Freeze is in 
effect. So from now on all changes for Qt 5.12 release must be done in '5.12' 
and 'dev' is for Qt 5.13.

If not already done please update Qt 5.12 new features page: 
https://wiki.qt.io/New_Features_in_Qt_5.12

Our plan is to publish Qt 5.12 alpha release as soon as possible. Alpha blocker 
list here: https://bugreports.qt.io/issues/?filter=19449

br,
Jani

From: Development  on 
behalf of Jani Heikkinen 
Sent: Tuesday, August 14, 2018 2:48 PM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: [Development] HEADS-UP: Branching from 'dev' to '5.12' started

Hi!

We have soft branched '5.12' from 'dev' today. We are planning to have final 
downmerge and Qt 5.12 Feature Freeze Monday 20.8.2018. So there is still time 
to finalize ongoing task in 'dev' and start using '5.12' for new changes 
targeted to Qt 5.12 release.

br,
Jani Heikkinen
Release Manager



___
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] Qt 5.11.2 changes files: Maintainers, Your action needed

[Jani Heikkinen]

Hi,

Initial ones here: 
https://codereview.qt-project.org/#/q/branch:5.11.2+message:%22Add+changes+file+for+Qt+5.11.2%22,n,z
Please take over and finalize those as soon as possible (during this week 
latest)

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

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

[Jani Heikkinen]

> -Original Message-
> From: Samuel Gaist 
> Sent: maanantai 20. elokuuta 2018 10.28
> To: Jani Heikkinen 
> Cc: development@qt-project.org; releas...@qt-project.org
> Subject: Re: [Development] HEADS-UP: Branching from 'dev' to '5.12' started
> 
> 
> > On 14 Aug 2018, at 13:48, Jani Heikkinen  wrote:
> >
> > Hi!
> >
> > We have soft branched '5.12' from 'dev' today. We are planning to have
> final downmerge and Qt 5.12 Feature Freeze Monday 20.8.2018. So there is
> still time to finalize ongoing task in 'dev' and start using '5.12' for new
> changes targeted to Qt 5.12 release.
> >
> > br,
> > Jani Heikkinen
> > Release Manager
> >
> >
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> 
> Hi,
> 
> I just received approval for an API addition to QTextEdit and QPlainTextEdit
> (QRegularExpression find overload).
> 
> Is it still on time for feature freeze since it happens today ?
> 
> It’s nothing vital, I just want to know whether I should change the
> documentation to 5.13 and resubmit.

Please do. We will do final downmerge soon so if the change isn't in yet it is 
better to put it in 5.13 now

br,
Jani Heikkinen
> 
> 
> Thanks
> 
> Samuel
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HEADS UP: Branching from '5.11' to '5.11.2' ready

[Jani Heikkinen]

Hi all,

Branching from '5.11' to '5.11.2' is now done and all changes for Qt 5.11.2 
must be done in '5.11.2' from now on. And as usual in release branches: No any 
nice-to-haves in anymore!

br,
Jani

> -Original Message-
> From: Development  project.org> On Behalf Of Jani Heikkinen
> Sent: perjantai 17. elokuuta 2018 18.19
> To: development@qt-project.org
> Subject: [Development] HEADS UP: Branching from '5.11' to '5.11.2' started
> 
> Hi,
> 
> We have soft branched '5.11.2' from '5.11' today. Target is to finalize
> branching Fri 24th August 2018. So please finalize ongoing changes in '5.11'
> and start using '5.11.2' for new changes targeted to Qt 5.11.2 release
> 
> br,
> Jani
> ___
> 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] Qt 5.9.4 snapshot available

[Jani Heikkinen]

Hi!

We have finally Qt 5.9.4 snapshot available in online repositories. You can 
add/update it via online installer like earlier. Please test the snapshot now & 
report all findings in Jira. And please inform me immediately if you find 
something which must block the Qt 5.9.4 release. But remember: We won't block 
release quite easily: If issue has been in Qt 5.9.3 or earlier then by default 
it won't block Qt 5.9.4.

Snapshot isn't yet final Qt 5.9.4 release but should be close: Blocker list is 
almost empty and only few already integrated changes are missing from snapshot. 
We will release Qt 5.9.4 during next week if nothing really serious reported 
from this snapshot

br,
Jani




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

[Development] Qt 5.11 beta1 released

[Jani Heikkinen]

Hi!

We have released Qt 5.11 beta1 today, see 
http://blog.qt.io/blog/2018/03/01/qt-5-11-beta-released/

You can find Qt 5.11 beta1 under 'Preview' node from Online installer. Please 
take a tour & start testing Qt 5.11 now. As earlier we will release new beta 
releases regularly until we are ready for final Qt 5.11 release. It is really 
important to recognize all blockers for the final release as soon as possible 
so please make sure all release blockers can be found from RC blocker list 
(https://bugreports.qt.io/issues/?filter=19209).

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

[Development] HEADS-UP: Branching from '5.9' to '5.9.5' started

[Jani Heikkinen]

Hi!

We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to '5.9.5' 
will happen at the beginning of week 11 (most probably Monday 12.3.2018).

Please start using '5.9.5' for new changes (cherry-picks from 5.11) targeted to 
Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!

We are targeting to release Qt 5.9.5 during March.

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

[Development] Qt API review process (was: Re: Qt 5.11 Alpha released)

[Jani Heikkinen]

Hi all,

We have API review ongoing for Qt 5.11. For me our process for that is a bit 
unclear; At which point we can say the review is really done? There are 
comments in the reviews but then pretty much nothing... At some there is -1, 
few +1 but that's it. I think we should clarify the process so that we can more 
easily see the status there. That's why I propose following:

1) API review for the module is ready when there is '+2'  (from Module/Chief 
Maintainer)
2) During the review reviewer must add 'Code Review -1/-2' if there is 
something which should be corrected before we can agree API review to be ready. 
And vice versa: if API seems to be OK +1 should be added to indicate API is 
reviewed.
3) Reviewer needs to create a bug report about the findings. That makes it 
easier to follow up & we can add needed ones in the release blocker list.
   * These bug reports should be added in review's comment field as well. And 
if one is something which really needs to be fixed before release reviewer 
should add the issue in release blocker list.
4) API review for module needs to be updated in gerrit until it gets '+2'. 
After that no more updates. That way we can link the approved review in 
releasing wiki for the evidence :D

br,
Jani 

From: Edward Welbourne
Sent: Wednesday, February 21, 2018 6:43 PM
To: development@qt-project.org
Cc: releas...@qt-project.org; Jani Heikkinen
Subject: Re: Qt 5.11 Alpha released

Jani Heikkinen (20 February 2018 11:14)
> We have release Qt 5.11 Alpha today, see 
> http://blog.qt.io/blog/2018/02/20/qt-5-11-alpha-released/

and so, of course, we also have 5.11 API reviews, vs v5.10.1:

https://codereview.qt-project.org/221039 qtbase
https://codereview.qt-project.org/221040 qtdeclarative
https://codereview.qt-project.org/221041 qtmultimedia
https://codereview.qt-project.org/221042 qttools
https://codereview.qt-project.org/221043 qtxmlpatterns
https://codereview.qt-project.org/221044 qtlocation
https://codereview.qt-project.org/221045 qtconnectivity
https://codereview.qt-project.org/221046 qtwayland
https://codereview.qt-project.org/221047 qt3d
https://codereview.qt-project.org/221048 qtserialbus
https://codereview.qt-project.org/221049 qtandroidextras
https://codereview.qt-project.org/221050 qtwebengine
https://codereview.qt-project.org/221051 qtcharts
https://codereview.qt-project.org/221052 qtgamepad
https://codereview.qt-project.org/221053 qtremoteobjects

See the review comments for guidance, consult actual source for
definitive views of code - note that these reviews are generated by a
script that filters out changes deemed boring; it has learned, on this
iteration, to not waste your time with s/Q_DECL_FINAL/final/ or
s/Q_QDOC/Q_CLANG_QDOC/ changes; and to ignore the addition of
Q_DECL_COLD_FUNCTION.  Speaking of which, please accept my apologies
for not delivering this two days ago - I got distracted by trying to
revamp the script to be a bit smarter about detecting boring changes
that add a line, among other things.

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

[Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready

[Jani Heikkinen]

Hi!

Branching from '5.9' to '5.9.5' is now competed. From now on '5.9' if for Qt 
5.9.6 and all changes targeted to Qt 5.9.5 release must be done in '5.9.5'. And 
as usual no any 'nice-to-haves' in '5.9.5' anymore!

We are targeting to get Qt 5.9.5 out as soon as possible (during March) so 
please make sure all release blockers are visible in blocker list 
(https://bugreports.qt.io/issues/?filter=19230) and all release blockers are 
fixed immediately.

br,
Jani

From: Development <development-bounces+jani.heikkinen=qt...@qt-project.org> on 
behalf of Jani Heikkinen <jani.heikki...@qt.io>
Sent: Thursday, March 1, 2018 3:07 PM
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' started

Hi!

We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to '5.9.5' 
will happen at the beginning of week 11 (most probably Monday 12.3.2018).

Please start using '5.9.5' for new changes (cherry-picks from 5.11) targeted to 
Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!

We are targeting to release Qt 5.9.5 during March.

br,
Jani
___
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] HEADS-UP: Branching from '5.9' to '5.9.5' ready

[Jani Heikkinen]

Hi!

Is there a bug report about the issue? If this is nothing new I think we can 
wait Qt 5.9.6 for that fix

br,
Jani

> -Original Message-
> From: Alexandr Akulich <akulichalexan...@gmail.com>
> Sent: keskiviikko 14. maaliskuuta 2018 16.21
> To: Jani Heikkinen <jani.heikki...@qt.io>
> Cc: development@qt-project.org; releas...@qt-project.org
> Subject: Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready
> 
> Hi Jani,
> 
> Can we please get in a compilation fix for qreal configured as float?
> There is a very small yet critical issue with qMax in QFusionStyle.
> 
> I submitted the fix [1] for 5.11 and it is approved, but I agreed to also fix 
> the
> same line coding style issue before staging the change.
> 
> I will submit the final patch for 5.11 in two hours (as soon as I'll get back 
> to my
> ssh keys) and will submit cherry-pick for 5.9 immediately after the original 
> patch
> staging.
> 
> [1] https://codereview.qt-project.org/#/c/223101/
> 
> On Wed, Mar 14, 2018 at 2:01 PM, Jani Heikkinen <jani.heikki...@qt.io> wrote:
> > Hi!
> >
> > Branching from '5.9' to '5.9.5' is now competed. From now on '5.9' if for Qt
> 5.9.6 and all changes targeted to Qt 5.9.5 release must be done in '5.9.5'. 
> And as
> usual no any 'nice-to-haves' in '5.9.5' anymore!
> >
> > We are targeting to get Qt 5.9.5 out as soon as possible (during March) so
> please make sure all release blockers are visible in blocker list
> (https://bugreports.qt.io/issues/?filter=19230) and all release blockers are 
> fixed
> immediately.
> >
> > br,
> > Jani
> > 
> > From: Development
> > <development-bounces+jani.heikkinen=qt...@qt-project.org> on behalf of
> > Jani Heikkinen <jani.heikki...@qt.io>
> > Sent: Thursday, March 1, 2018 3:07 PM
> > To: development@qt-project.org
> > Cc: releas...@qt-project.org
> > Subject: [Development] HEADS-UP: Branching from '5.9' to '5.9.5'
> > started
> >
> > Hi!
> >
> > We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to 
> > '5.9.5'
> will happen at the beginning of week 11 (most probably Monday 12.3.2018).
> >
> > Please start using '5.9.5' for new changes (cherry-picks from 5.11) 
> > targeted to
> Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!
> >
> > We are targeting to release Qt 5.9.5 during March.
> >
> > br,
> > Jani
> > ___
> > 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] Qt 5.11 beta2 released

[Jani Heikkinen]

Hi all,

We have published Qt 5.11 beta2 today. As earlier you can get it via online 
installer. Delta to beta1 attached.

Please test the packages now & report all findings to Jira. Also make sure all 
release blockers can be found from release blocker list 
(https://bugreports.qt.io/issues/?filter=19209). It is really time to test the 
packages now; even the plan is to release at the end of May we will do it 
earlier if possible.

br,
Jani
qt5.git
5bbeaf6c0d4fe3b5b81ff9003c4bdba1e4991813 Update qtwebengine only
b85b272c26810e54a4ceb0707cf4569f87517b67 Move MSVC2017 x86 builds to 64bit host 
OS
04d1ee1df4302c78be54da76826221661ff25056 Provisioning: Create symbolic for 
shasum tool on macOS for compatibility
00e3a0149a9da44a90400a232aeb481770170dea Properly download and install RHEL 
EPEL repo
9cb66c01143afa2b8115507c693a7266a31da6bb Install RHEL EPEL only once
940ef0a4cc551f31f82b99ae8adeb3544720b340 Provisioning: win8.1 - RTA required 
provisioning scripts
3410bab2783875403e43ae8875901da3605ece23 Provisioning: Fix Squish installation 
for msvc14 32-bit
95609c6657dd08cb96fadf55927f62788a56b82e Provisioning: Executequeueditems on 
Windows
3230cdb138878df7dc6daa0f44e86c565629b2f2 Provisioning: win10_x86 - Disable 
automatic updates
7a052f4183a2a115fc1246daa20b53fbd9109c9b open62541: Fix provisioning for RHEL 
7.4
bb9739773ccd2844bad5e8c0124405acb3315ecb Simplify openssl_for_android_linux 
provisioning script
52b163092ad890620c1a190f5fce404565e19e99 Add missing 08-libclang.ps1 for 
windows7 provisioning
140c6479b5916e21d6c03a94f844a0f8693af0f8 Install libusbx-devel for QDB on RHEL 
7.4
qt3d:
028c35909c38f0e47a5ab25fc1be14a4394ae4c5 visitorutils_p.h: add proper header 
guard
1efca1346faa65989e3f500e7d16dfee151dc4a4 Enable alpha blending on 
QTextureMaterial
0a9f5004691cc547b622a9c89cf217809c64e98c Don't assume position attribute uses 
default name in visitPrimitives
74c7f57f8d8c532d3074ec3a02dbd35d18a9b59f Documentation for ray casting
1de8948ff8db516e683203bcc896f931adb18cae Add more job tests for raycasting
42a27f1a9ce319393a8e10a5f91b336e69fe2eb6 Either fully qualify property types, 
or not at all
7ddb976ab22c5b75d3180e19ed4e27ff322a99af ObjGeometryLoader::doLoad(): Fix fall 
through warnings
c35f78e4e4871345fdb586c36a0e24839a243ae6 Add unit test to check memory alignment
912d3bdc6471053a61b747cac7376fba20c4e8a2 Add test to check if readding shader 
removes dna from m_pendingRemoval
f7e01ffeb3626432cabe3d1ad245827e4217375c Prevent readded shaders to be purged 
from cache
eedad5e4737072b99b112a51e08b35b4038dbf95 Doc: Fix documentation warnings for Qt 
3D Render
9f7e98db85bdd57350104eeb417233a55b4f1129 QResourcesManager: remove simd code 
from header
e1b34d6ad33ad40d727d3e02cefe8655f3ed4859 Fix SIMD related warnings
b8947197979f30d624454efe0467b151437dd9d3 simd: declare AVX2 friends only if 
__AVX2__ defined
461194b0aa6b35e7dd1c9ff411806b065f8b01f7 RenderThread: fix races with texture 
and buffer
bf0b3bdf5ab7c15bf72eced860053a611eccda4a Fix race between RenderThread and 
ShaderGathererJob
d3b6a6054ce0b322611c465643aa55f7c60a276e Fix RenderView uniform minification
6ea64e9ba9c17302c50648e4c3836a7563679f6a Load textures in a single frame
3dff7c204da1d834629544b54b9f6efaafe165e2 Revert "Keep rendering in sync with 
aspect jobs by adding barriers"
a43cf3726679704cc8c4c5a405c60c6f1c4fcfce Set mip levels correctly when having 
only texture images
qtactiveqt:
qtandroidextras:
qtbase:
1e27219968f760501c99f9f744f172d475a57162 add missing tests of rvalue overloads 
for QVarLengthArray and QVector
fee8944cbe2a976e1b4a71c5df048e84a0bc6db0 Allow use of template class instances 
inheriting from a Q_GADGET in Qml
b767c7363f7ceda88553fb8abb6d4cb70b70bd2f qxcbconnection_xi2.cpp: fix debug 
check to avoid confusing debug output
9b7809a43ee0add8c11d3387b73a01bfdedd0043 xcb: Fix FP1616 to int conversion
4d204854745f6682d9937b8c13a429890e5bc738 set attribute specifier before 
namespace name
c082d84d5d7fdbfb64de18f06a8ddbc77f2e6de4 Fix QLabel crash if buddy's lifetime 
is too short
e5a6e9bb80fb2427228f70488b8839b4aa0b4261 Doc: improve QScopedPointer::reset() 
documentation
caa5a20479bd58fda4380181691f772a1f3c1da4 Make a benchmark out of 
tst_QObjectPerformance::emitToManyReceivers
e16c6dfb7286264ccdfd37d8e74c97f13ece7835 QCocoaMenuItem: Make QCocoaNSMenu the 
item target
4dee5446bee9c7417bf6f5dc44294a0b7238a9ba Add missing rvalue overloads of 
operator+=() and operator<<()
808adeb7bc53208a1c30f425fce6359a17f00170 QSqlField: rearrange QSqlFieldPrivate 
members
80693f171c9e904007137f109a83fb456c9cae48 QStandardItem: add more sanity checks 
on insertRow(s)/Column(s)
b64f3f6ca97e299176ca8990402650552a90f704 QTabWidget: Do not add tabbar size 
during sizeHint() when it is hidden
3185b40d5de1092ed2bdd83f72478a344c5fc9e9 SQL/Postgres: Fix support for nan, inf 
and -inf
70cfe551b285b4a3e770aabbca8f8bdcfadffb09 Apple: resolve SDK version of 
QMAKE_LINK_C and QMAKE_LINK_C_SHLIB
67d5f79fe6f86726eff0461bd6f3bb928801723c logging: Clarify and 

Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready

[Jani Heikkinen]

Ok,
Then it would be good to get this fixed in Qt 5.9.5. Please remember to do the 
cherry-pick in '5.9.5', not in '5.9'

br,
Jani

From: Alexandr Akulich <akulichalexan...@gmail.com>
Sent: Thursday, March 15, 2018 10:03 AM
To: Jani Heikkinen
Cc: development@qt-project.org; releas...@qt-project.org
Subject: Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready

I thought that it is an old issue (since 5.9 to 5.11) but in fact, it
is a regression since change [1] in landed to 5.9.5.
I staged the fix for 5.11 ten minutes ago and I will submit the change
for 5.9 in two hours.

[1] https://codereview.qt-project.org/#/c/212208/

On Thu, Mar 15, 2018 at 7:56 AM, Jani Heikkinen <jani.heikki...@qt.io> wrote:
> Hi!
>
> Is there a bug report about the issue? If this is nothing new I think we can 
> wait Qt 5.9.6 for that fix
>
> br,
> Jani
>
>> -Original Message-
>> From: Alexandr Akulich <akulichalexan...@gmail.com>
>> Sent: keskiviikko 14. maaliskuuta 2018 16.21
>> To: Jani Heikkinen <jani.heikki...@qt.io>
>> Cc: development@qt-project.org; releas...@qt-project.org
>> Subject: Re: [Development] HEADS-UP: Branching from '5.9' to '5.9.5' ready
>>
>> Hi Jani,
>>
>> Can we please get in a compilation fix for qreal configured as float?
>> There is a very small yet critical issue with qMax in QFusionStyle.
>>
>> I submitted the fix [1] for 5.11 and it is approved, but I agreed to also 
>> fix the
>> same line coding style issue before staging the change.
>>
>> I will submit the final patch for 5.11 in two hours (as soon as I'll get 
>> back to my
>> ssh keys) and will submit cherry-pick for 5.9 immediately after the original 
>> patch
>> staging.
>>
>> [1] https://codereview.qt-project.org/#/c/223101/
>>
>> On Wed, Mar 14, 2018 at 2:01 PM, Jani Heikkinen <jani.heikki...@qt.io> wrote:
>> > Hi!
>> >
>> > Branching from '5.9' to '5.9.5' is now competed. From now on '5.9' if for 
>> > Qt
>> 5.9.6 and all changes targeted to Qt 5.9.5 release must be done in '5.9.5'. 
>> And as
>> usual no any 'nice-to-haves' in '5.9.5' anymore!
>> >
>> > We are targeting to get Qt 5.9.5 out as soon as possible (during March) so
>> please make sure all release blockers are visible in blocker list
>> (https://bugreports.qt.io/issues/?filter=19230) and all release blockers are 
>> fixed
>> immediately.
>> >
>> > br,
>> > Jani
>> > 
>> > From: Development
>> > <development-bounces+jani.heikkinen=qt...@qt-project.org> on behalf of
>> > Jani Heikkinen <jani.heikki...@qt.io>
>> > Sent: Thursday, March 1, 2018 3:07 PM
>> > To: development@qt-project.org
>> > Cc: releas...@qt-project.org
>> > Subject: [Development] HEADS-UP: Branching from '5.9' to '5.9.5'
>> > started
>> >
>> > Hi!
>> >
>> > We have soft branched '5.9.5' from '5.9'. Final downmerge from '5.9' to 
>> > '5.9.5'
>> will happen at the beginning of week 11 (most probably Monday 12.3.2018).
>> >
>> > Please start using '5.9.5' for new changes (cherry-picks from 5.11) 
>> > targeted to
>> Qt 5.9.5 release. And once again: No any 'nice to haves' in '5.9.5' anymore!
>> >
>> > We are targeting to release Qt 5.9.5 during March.
>> >
>> > br,
>> > Jani
>> > ___
>> > 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] Qt 5.11 Beta3 released

[Jani Heikkinen]

Hi all,

Qt 5.11 beta3 is released today. As usual you can get it via online installer. 
Delta to beta2 as an attachment.

Please test the release now. It seems we are really close to RC already so 
please make sure all release blockers are visible in RC blocker list 
(https://bugreports.qt.io/issues/?filter=19209). And also fix all blockers from 
the list immediately. We will start preparations for RC soon and I hope there 
won't be any late blocker findings at this time...

br,
Jani



qt5.git
3c23dc484635e4c3340461316454be50fe11e28f Don't require Qt Android Extras for Qt 
Purchasing
9e74a1e5b7cf5f487b77068565ba7c0671b4dcd0 Add a clean installed Win10_x86 for RTA
dbe27bc9ccb915638de06bb5a23be1a0cd4d6b9f Provisioning: Win8.1 - Add jom for RTA
9dd5f6d861a920df1d92b85593c81172ca7e0feb Add SeparateDebugInfo for linux release
a01e7f3d405484791a1e37d35f12a5e894f51007 Install an android virtual device for 
testing
8552003532ecc7d0c603c1c027378576795181b0 Reduce wget verbosity when downloading 
qnx
8197e80155a9b4d8d0fe68411b44b69576b13ebd Provisioning: Remove Java update from 
windows startup items
794913dde77e9a2918353894a33d03b16e6927c4 Install Python 2.7.13 to RHEL with pip
5085220907005503326b8d4f17d52b5e6e00d731 Provisioning: Win7_x64 - Add Squish 
6.3.0 win64 msvc12
de4e9c2169aac41db10fdff1503ad645f0a4a72a Provisioning: refactor squish install
f1eca9bbff35b4640c4779fb4b5cad25c33f7de0 Remove duplicate python-devel 
provisioning from RHEL 7.x
ab021d4bb4a92143892a68d89dbe9f3dd4e3f81f Make unzip less verbose in macOS
9ae91ae3f87fb3e3ad030410c4d313cb217f530b Update Python 3.4 to 3.6 in RHEL 7.x
418cb4c4f5b199b8a9ed71752f70c711882ad42f Provisioning: Win8.1_x64 - Add Python2 
and Python3 for RTA
b59f4207a3ab830d963eb7b977b650f0e4d6442d Add Windows 8.1 target for RTA
f6d18ec9b3e6cc65b687810f39a570a0b39439cd Disable background update checks in 
RHEL 7.x
a6feaec2877d9089d9b9ba5c934b89a4de78de42 Provisioning: Fix java installation 
for mac
1b5f8cec03297af93150537cc3c8eb0bcd01f3fc Remove try_catch.sh helper script
2f9a2f65e5497d1620aa9edbea8d4523ffe5ce89 Remove try_catch codes from macOS 
10.12 provisioning
a98b0f3d7989bedf6f0bcc1a83b52aad1d3baa3e Remove try_catch codes from common 
macOS scripts
90261c1df5cb62a47b44d2d9b84c0753d6ebf9e4 Remove try_catch codes from unix 
scripts
250dd8c84eef62fbdb51856b367225adfabd643e Remove try_catch codes from macOS 
10.11 scripts
1c6abfae014b3ece4d14d3dc7b9a22353cf18c66 Remove try_catch from common linux 
scripts
4492fd3268e575dc79d77105821839631aac998f Remove try_catch codes from Ubuntu 
16.04 scripts
5d7972b73b695e390b9bd3d82d7b6089b2ce84a2 Provisioning: Windows - Disable 
autoreboot
85f874388cad89f4b66b28d7612a7a630d78911c Revert "Provisioning: openSUSE - Set 
grub timeout to 0"
863252be498028c589c08ba23a70eb9cd92b1416 Download get-pip primarily from our 
local cache
64c79b27d6457235a30dd124382b004d37d4c089 Clean old RHEL repo data before 
fetching new data
eebc0133f00f15d6166de7fe74f0f30bc3af50a2 Disable update download in background
209cb73a363d794ad312e28f9ea38bb8ef8b47bb Use local RHEL repositories with RHEL 
7.4
23b4bcf6c5773f1499e89b132e87e4d0333676a7 Provisioning: Move http_proxy.txt 
under shared folder
237b308d47c47a6959ec559e0efd2cf1b525ba3a Provisioning: Fix adb process name for 
android sdk installation
8a47814c91828a2f1541b99b58c8ee2eb085cb51 Simplify DownloadURL
qt3d:
2a260617b96281375e2ee018af8c7547d99e4a6d Add replacement materials example
634529d899e99c2fb40429d3d0be6295aa444a40 Replace the toyplane mesh with one 
created by KDAB
c99555e476fd7be943d476c5ce4463463628e412 Doc: Add and improve examples in 
render states and material system
c5a6d31c2a40a3e1bd976ff8162238a7cbc066b4 Fix findCubicRoots for cases where 
coefficients are close to zero
2bf1f907e9e6ac87fc039d674eaca5179c5029f6 Fix race in startup/shutdown
96d7e81706114084e850f0215351d85be0486b5c ObjectPicker: remove renderer include
68bc82e3c909376198ae3c9ba4d53981f1879fe3 sendbuffercapturejob: remove non 
needed manager member
e6423c0ad0b867ecd156145a946c3a74aa26ab22 SubmissionContext: improve 
specifyAttribute
cde4f0367392eb98e49155b72af75fecd13cd766 AbstractRenderer: add entries into API 
enum
aea2931fcb10b5e724380887bd2053f7e3cdd868 Fix uninitialized value in 
updateskinningpalettejob.cpp
597bbf003c13619e63787e5df7cac2d814430b0c Fix uninitialized value in 
sendrendercapturejob
643b6f7adf579d3d1ff5b523fa8836939e9d0b64 MaterialParameterGathererJob: remove 
unneeded renderer member
5a9bc47fbec58d4289260ca8a6359ef015154fab ViewportNode: make computeViewport a 
static function
b6851eb62778c39894340dcf33feb5857bb520a6 tst_loadscenejob: remove warnings
f14ad1302da60e57abbfd43ef1a684458bc576ba AbstractRenderer: add setOpenGLContext 
method
4c3f6cb3d396d45d0a463c1222bb4185b9a015ab SendRenderCaptureJob: remove hard 
dependency to Renderer
013be08f1b5b5884922ea5723c6dc34e27179ac7 Remove QItemModelBuffer: unused and 
incomplete
4b83e2ee155c9ebf71e2fc46ab9abdb40bbb1061 RenderStates: rework to split node and 

[Development] Maintainers, your action needed: Please check if 3rd party components needs to be updated for Qt 5.11 release

[Jani Heikkinen]

Hi!

Please check if some 3rd party component needs to be updated for Qt 5.11 
release. And of course do needed updates now :D
List of 3rd party components here: 
http://doc.qt.io/qt-5/licenses-used-in-qt.html

br,
Jani

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

[Development] Qt 5.9.5 released

[Jani Heikkinen]

Hi all,

We have release Qt 5.9.5 today, see 
http://blog.qt.io/blog/2018/04/12/qt-5-9-5-released/ .

Big thanks to everyone involved!

Br,
Jani




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