From jani.heikkinen at qt.io  Tue May  8 12:06:23 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 8 May 2018 10:06:23 +0000
Subject: [Releasing] Qt 5.11.0 RC released
In-Reply-To: <AM2PR02MB08814C2B5DBEC855780108599D9A0@AM2PR02MB0881.eurprd02.prod.outlook.com>
References: <AM2PR02MB08814C2B5DBEC855780108599D9A0@AM2PR02MB0881.eurprd02.prod.outlook.com>
Message-ID: <AM2PR02MB088179B562D83299C2B8C34A9D9A0@AM2PR02MB0881.eurprd02.prod.outlook.com>

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




-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: delta_qt511-beta4-qt511-rc.txt
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20180508/6e790c31/attachment.txt>

From jani.heikkinen at qt.io  Wed May  9 08:01:11 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 9 May 2018 06:01:11 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 08.05.2018
Message-ID: <AM2PR02MB088182A78135C82C75A0C8059D990@AM2PR02MB0881.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 8th May 2018

Qt 5.11.0 status:
- RC released
- Target to release Qt 5.11.0 22.5.2018
- MSVC 2017 15.7 released, to be confirmed if 5.11.0 RC compiles ok with it
- RC2 needs to be done because of critical security fix in Chromium
   * Fix already in but we will wait a while to see if there is something else to be fixed as well

Qt 5.9.6:
- Branching from '5.9' -> '5.9.6' to be started at the beginning of next week
- Target to get release out at the beginning of June

Qt 5.6.4:
- To be discussed in ml/QtCS if release is really needed
   * But in any case possible release won't happen before summer break

Next meeting Tue 15.5.2018 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:

[17:00:14] <jaheikki3_> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping 
[17:00:22] <lars> jaheikki3_: pong
[17:00:44] <thiago> jaheikki3_: pong
[17:01:29] <jaheikki3_> Time to start qt release team meeting
[17:01:34] <jaheikki3_> On agenda today:
[17:01:40] <carewolf> pong
[17:01:42] <jaheikki3_> - Qt 5.11.0 status
[17:01:47] <jaheikki3_> - Qt 5.9.6
[17:01:57] <jaheikki3_> Any additional item to the agenda?
[17:03:17] <jaheikki3_> Ok, qt 5.11.0 status:
[17:03:24] <jaheikki3_> rc released today
[17:03:42] <frkleint> jaheikki3_: pong
[17:04:01] <thiago> in the two weeks since we've last had this meeting, MSVC 2017 15.7 was released
[17:04:10] <thiago> we need to make sure that 5.11 works on it
[17:04:36] <thiago> I only installed it yesterday. I'm in the middle of compiling qtbase.
[17:04:41] <thiago> has anyone progressed further?
[17:05:00] <lars> thiago: I doubt it.
[17:05:45] <jaheikki3_> thiago: lars: if there is some issues with it I think we could wait 5.11.1 instead of delaying 5.11.0
[17:05:57] <thiago> I do not think so
[17:06:02] <jaheikki3_> 5.11.1 is targeted to happen before summer break
[17:06:06] <thiago> if there are issues, it's an FTBFS on a major platform
[17:06:28] <thiago> there is one feature I'd like to enable that can wait: -Zc:__cplusplus support
[17:07:21] <jaheikki3_> thiago: should't that kind of changes be done in 5.12 instead (meaning not evein in 5.11.1
[17:07:33] <carewolf> hopefully nothing will break, or will only be warnings that only affect some builds and are not important. 
[17:07:48] <thiago> people have complained about us not identifying the C++ level properly
[17:07:53] <lars> jaheikki3_: since we say we support 2017, we should fix those in 5.11. The only question would be 5.11.0 or later
[17:07:55] <thiago> so I don't think we can wait
[17:08:10] <thiago> the point is that 15.7 has __has_include, which is why we need to make sure everything still compiles
[17:08:25] <lars> thiago: so they finally added that?
[17:08:28] <carewolf> ah
[17:08:34] <thiago> lars: seems so
[17:08:51] <thiago> I haven't directly verified it yet. I need to compile and run some of the unit tests.
[17:09:04] <lars> thiago: well, in theory it should help us, but yes, that has the potential to break something
[17:09:22] <thiago> and that's why I am asking for someone else besides me to also test it
[17:09:49] <jaheikki3_> frkleint: do you or others in windows team have tried that?
[17:09:59] <frkleint> never heard of it,.sorry
[17:10:09] <lars> agree, that would be good. 
[17:10:13] <frkleint> ask someone to do on-demand COIN runs?
[17:10:40] <jaheikki3_> frkleint: we would need to provisioning that in coin first
[17:10:41] <thiago> so... does COIN have 15.7 installed?
[17:10:44] <lars> frkleint: I don't think we have that MSVC version available in COIN yet
[17:11:14] <lars> but yes, that would be a good way to test
[17:11:33] <jaheikki3_> lars: frkleint: no, there isn't. I'll check tomorrow with hehalmet & tosaraja if we could give a test run
[17:11:53] <frkleint> what is this exactly, some update of VS2017?
[17:11:53] <lars> jaheikki3_: sounds good. let's try to add the provisioning and see what happens :)
[17:11:59] <frkleint> is living under a rock
[17:12:24] <thiago> yes
[17:12:30] <lars> frkleint: https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
[17:12:32] <thiago> compiler version 19.14
[17:13:00] <thiago> see also https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/
[17:13:11] <frkleint> hm,ok
[17:13:26] <jaheikki3_> Ok,we will check if we can give a test run for that in coin & see what happens
[17:13:43] <frkleint> yup
[17:14:02] <frkleint> ok, have to rush, sorry
[17:14:14] <jaheikki3_> There is also couple of new changes already coming in '5.11.0', see https://codereview.qt-project.org/#/q/branch:5.11.0,n,z
[17:14:43] <jaheikki3_> I am not sure yet if we should do rc2 because of those or just wait 5.11.1
[17:15:05] <thiago> I think we need at least one more week
[17:15:17] <jaheikki3_> another one is security fixes for WE and another one is just a changes file update
[17:15:18] <carewolf> I think the update of chromium is important, it includes one security fix marked critical.
[17:15:20] <thiago> we'll see what the 15.7 build turns up
[17:15:24] <thiago> it could be nothing
[17:15:37] <jaheikki3_> that's true
[17:16:01] -*- thiago crosses finger
[17:16:01] <thiago> s
[17:16:10] <jaheikki3_> And let's see what is found during testing of rc packages
[17:16:17] <jaheikki3_> same here
[17:16:24] <lars> yes, let's check that first. hopefully things will simply work with the new compiler
[17:17:42] <jaheikki3_> carewolf: but is that really worth of rc2 alone?. because 5.11.1 is coming really soon as well? 
[17:18:11] <thiago> if it's FTBFS or something broken, it's 5.11.0
[17:18:28] <thiago> if it's a feature that was never enabled for 2017 before, 5.11.1
[17:18:37] <carewolf> let me put it this way, the only security fixes marked critical in chrome the last 3 years and have those here from chrome 66
[17:18:55] <carewolf> I don't know how it can be exploited, but 'critical' is not something they use a lot
[17:20:02] <jaheikki3_> carewolf: ok, i see your point. We have time to do rc2 even we are targeting to get final out 22nd of May
[17:20:38] <jaheikki3_> we don't need 2 weeks between rc2 and final; it is enough to have that time between rc & final
[17:20:44] <lars> jaheikki3_: agree with carewolf that we should get those in
[17:21:05] <carewolf> though, I have accepted we can wait with the same fixes in 5.9 as long as 5.9.6 is released within the 12 weeks grace we have before the details are public
[17:22:21] <jaheikki3_> yeah, let's do rc2 at least with those changes. Let's see if something else is found as well
[17:22:37] <jaheikki3_> I'll stage those changes in 
[17:22:44] <carewolf> thanks
[17:22:54] <thiago> carewolf: do you know if V8 is compiled with the spectre mitigations turned on?
[17:23:45] <carewolf> the main spectre mitigation is disabling shared-arrays, lowering timing precision and adding cryptographis noise to the timers
[17:23:48] <carewolf> we have all that.
[17:24:20] <jaheikki3_> Ok,this was all about 5.11.0 at this time
[17:24:27] <jaheikki3_> Then quickly 5.9.6:
[17:24:54] <jaheikki3_> I think we should start branching from 5.9 -> 5.9.6 at the beginning of next week
[17:25:26] <jaheikki3_> That way we could get 5.9.6 out at the beginning of June and then we would have enough time to get 5.11.1 out as well during june
[17:26:13] <jaheikki3_> Would that be OK?
[17:26:39] <carewolf> ok by me
[17:26:42] <lars> jaheikki3_: sounds good to me. how large is the delta between 5.9.5 and 5.9 currently?
[17:26:57] <lars> do we know how many patches we have in there?
[17:28:01] <jaheikki3_> lars: I haven't check detailed but qith quick look ~150 - 200 changes
[17:28:20] <lars> jaheikki3_: in qtbase alone I assume?
[17:29:25] <thiago> that's 23 in qtbase only
[17:29:45] <jaheikki3_> lars: overall. I just browse through gerrit history to see merged changes in '5.9' after 5.9.5
[17:29:59] <lars> thiago: ok, so rather small update
[17:30:38] <jaheikki3_> true. But on the other hand it should be easier to get release out when amount of changes is smaller
[17:30:59] <lars> jaheikki3_: sure, I was just curious. I think it's good that we have regular updates
[17:31:14] <jaheikki3_> agree
[17:31:41] <jaheikki3_> Ok, let's start branching from '5.9' -> '5.9.6' at the beginning of next week
[17:31:55] <jaheikki3_> It was all at this time
[17:32:07] <thiago> one more topic
[17:32:12] <jaheikki3_> ?
[17:32:12] <thiago> timeline for 5.6.4?
[17:32:22] <thiago> we're 9 months since 5.6.3
[17:32:27] <thiago> after Summer break?
[17:32:48] <jaheikki3_> At least not before. 
[17:33:10] <thiago> ok
[17:33:19] <thiago> that's all I needed
[17:33:19] <jaheikki3_> Do we really need to do it at all?
[17:33:36] <thiago> I think one more release is important
[17:34:01] <thiago> we promised 2 years of fixes and there are some pending fixes
[17:34:05] <thiago> we could make it and close the branch
[17:34:42] <jaheikki3_> lars: do you have any comments to that? 
[17:35:10] <thiago> we should discuss this in the ML. Doesn't need to be now.
[17:35:19] <thiago> I was just wondering if the timeline asked for someothing sooner.
[17:35:24] <lars> jaheikki3_: let's have a look at the fixes in 5.6 as well
[17:35:27] <thiago> we can also discuss during QtCS
[17:35:45] <lars> thiago: let's do that. currently nobody is asking for something soon
[17:36:05] <jaheikki3_> Yeah. We aren't that hurry with it. 
[17:37:08] <lars> ok, need to leave. have a good day/evening everybody :)
[17:37:49] <jaheikki3_> Same to you. Let's end this meeting now & have new one next tue (15.5.2018) at this same time
[17:38:09] <jaheikki3_> thanks for your participation. Bye!
[17:39:59] <thiago> bye

From jani.heikkinen at qt.io  Wed May  9 13:00:51 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 9 May 2018 11:00:51 +0000
Subject: [Releasing] HEADS UP: Branching from '5.9' to '5.9.6' started
Message-ID: <AM2PR02MB0881242E9729CE5189ABBCD89D990@AM2PR02MB0881.eurprd02.prod.outlook.com>

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




From jani.heikkinen at qt.io  Tue May 15 16:19:59 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 15 May 2018 14:19:59 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 15.05.2018
Message-ID: <AM2PR02MB088166F035BE8C45D9C1BC279D930@AM2PR02MB0881.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 15th May 2018

Qt 5.11.0 status:
- RC2 content in place
   * qt5.git integration done, packaging just started
- Target is to get RC2 out tomorrow & do final testing
- RC2 content will be released as Qt 5.11.0 Tue 22nd May (if nothing new & really serious found from packages)

Qt 5.9.6 status:
- Branching ongoing, will be finalized 22nd May
- Blocker list here: https://bugreports.qt.io/issues/?filter=19339
   * Only one item open in the list atm
- Target is still to get the release out at the beginning of June

Next meeting Tue 29th May 16:00 CET

br,
Jani

irc log below
[16:59:44] <jaheikki3_> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping 
[16:59:48] <ankokko__> jaheikki3_: ping
[16:59:50] <akseli> jaheikki3_: pong
[16:59:51] <lars> pong
[16:59:56] <thiago> jaheikki3_: pong
[17:00:47] <jaheikki3_> time to start qt release team meeting
[17:00:57] <jaheikki3_> on agenda today:
[17:01:01] <jaheikki3_> Qt 5.11.0 status
[17:01:09] <jaheikki3_> Qt 5.9.6 status
[17:01:18] <jaheikki3_> Any additional item to the agenda?
[17:02:07] <frkleint> jaheikki3_: pong
[17:02:21] <jaheikki3_> Let's start from 5.11.0 status
[17:03:01] <jaheikki3_> all know blockers fixed & RC2 content is in place now
[17:03:15] <jaheikki3_> ~10 changes after rc1
[17:03:20] <frkleint> has a vision of release cake
[17:03:36] -*- thiago can't eat cake
[17:03:56] <jaheikki3_> :D Ice cream then...
[17:04:05] <jaheikki3_> qt5.git integration done, packaging just started
[17:04:12] <jaheikki3_> Target to get RC2 out tomorrow
[17:04:34] <jaheikki3_> Then some testing still & final out Tue 22nd may
[17:05:18] <jaheikki3_> And target is to keep RC2 content as it is for final
[17:05:27] <jaheikki3_> Any comments or questions?
[17:07:14] <jaheikki3_> That's all about 5.11.0. Then Qt 5.9.6 status:
[17:07:40] <jaheikki3_> Branching from '5.9' -> '5.9.6' ongoing
[17:08:23] <jaheikki3_> Only one item open in the release blocker list at the moment, see https://bugreports.qt.io/issues/?filter=19339
[17:09:09] <jaheikki3_> Target is to finalize branching tue 22nd May & create a rc for testing as soon as possible after it
[17:09:37] <jaheikki3_> And the target is to get release out at the beginning of June 
[17:09:57] <jaheikki3_> That's all about 5.9.6 at this time. Any comments or questions?
[17:11:15] <thiago> no
[17:11:21] <thiago> I think this was a uick meeting like that
[17:11:45] <lars> jaheikki3_: sounds all good :)
[17:11:47] <frkleint> jaheikki3_: Are there any plans about 5.6.X?
[17:12:33] <jaheikki3_> frkleint: we shortly discussed it at last time & agreed to discuss it further in ML/QtCS
[17:13:25] <frkleint> Ah,ok
[17:13:34] <jaheikki3_> It was all at this time. I think we can skip nextweeks meeting in case Qt 5.11.1 will be released as planned & have new one Tue 29th May at this same time
[17:14:09] <akseli> sounds good
[17:14:22] <jaheikki3_> Thanks for your participation. Bye!
[17:14:34] <akseli> bye
[17:14:36] <ankokko__> bye
[17:15:15] <frkleint> bye






From jani.heikkinen at qt.io  Fri May 18 11:26:23 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Fri, 18 May 2018 09:26:23 +0000
Subject: [Releasing] Qt 5.11.0 RC2 out
In-Reply-To: <AM2PR02MB08817DCDB1C1A2860954BAFE9D900@AM2PR02MB0881.eurprd02.prod.outlook.com>
References: <AM2PR02MB08817DCDB1C1A2860954BAFE9D900@AM2PR02MB0881.eurprd02.prod.outlook.com>
Message-ID: <AM2PR02MB0881D7C8717D2B3833FE5FD89D900@AM2PR02MB0881.eurprd02.prod.outlook.com>

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
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: delta_qt511-rc-qt511-rc2.txt
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20180518/c7c90630/attachment.txt>

From jani.heikkinen at qt.io  Tue May 22 12:09:30 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 22 May 2018 10:09:30 +0000
Subject: [Releasing] Qt 5.11.0 released
In-Reply-To: <DB5PR02MB0888FA21DED7C4024AE2F40B9D940@DB5PR02MB0888.eurprd02.prod.outlook.com>
References: <DB5PR02MB0888FA21DED7C4024AE2F40B9D940@DB5PR02MB0888.eurprd02.prod.outlook.com>
Message-ID: <AM2PR02MB0881625723F0409E332F0F7E9D940@AM2PR02MB0881.eurprd02.prod.outlook.com>

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


From jani.heikkinen at qt.io  Tue May 22 15:29:43 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 22 May 2018 13:29:43 +0000
Subject: [Releasing] HEADS UP: Branching from '5.9' to '5.9.6' completed
Message-ID: <DB5PR02MB08880F94C856C3C4B01BC1749D940@DB5PR02MB0888.eurprd02.prod.outlook.com>

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 at qt-
> project.org> On Behalf Of Jani Heikkinen
> Sent: keskiviikko 9. toukokuuta 2018 14.01
> To: development at qt-project.org
> Cc: releasing at 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 at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


From pasi.keranen at qt.io  Fri May 25 09:56:58 2018
From: pasi.keranen at qt.io (=?utf-8?B?UGFzaSBLZXLDpG5lbg==?=)
Date: Fri, 25 May 2018 07:56:58 +0000
Subject: [Releasing] Qt 3D Studio 2.0 BETA 2 released
Message-ID: <8BF31690-A700-4DF8-9593-8D3A6A69EA13@contoso.com>

Hi,

We have released Qt 3D Studio 2.0 BETA2 today. It is available as both commercial and open sourceversions from online and offline installers.

For instructions on how to get started and install everything correctly, see Laszlo’s excellent blog on the subject for BETA1 here:
http://blog.qt.io/blog/2018/05/18/get-started-qt-3d-studio-2-0-beta-1/

Regards,
Pasi Keränen
Senior Manager, 3D Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20180525/7fe65978/attachment.html>

From jani.heikkinen at qt.io  Tue May 29 16:26:41 2018
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 29 May 2018 14:26:41 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 29.05.2018
Message-ID: <AM2PR02MB088197E214788B90E2C38A6D9D6D0@AM2PR02MB0881.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 29th May 2018

Qt 5.9.6:
- Branching finalized
- Changes file creation ongoing, see https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.6%22,n,z
   * Please finalize changes files now to make sure there won't be delays for the release
- Release target: Beginning of June
   * As earlier no manual test round before release, just RTA
   * Target to create "RC" for RTA testing as soon as possible
      ** When all changes files are in
      ** And blockers list (https://bugreports.qt.io/issues/?filter=19339) is empty

Qt 5.11.1:
- Target to get release out before summer vacation period 
   * Release target 19.6.2018
--> We need to start branching from '5.11' to '5.11.0' at the end of this week & finalize it at the end of next week to be able to keep the plan
- Release blocker list here: https://bugreports.qt.io/issues/?filter=19372
   * Blocker list should be short; if some issue isn't fixed in time fix will be then in 5.11.2

Next meeting Tue 5.6.2018 16:00 CET

br,
Jani 

irc log below:

[17:01:11] <jaheikki3_> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping 
[17:01:43] <frkleint> jaheikki3_: pong
[17:01:46] <akseli> jaheikki3_: pong
[17:02:04] <jaheikki3_> Time to start Qt release team meeting
[17:02:12] <jaheikki3_> On agenda today:
[17:02:22] <jaheikki3_> Qt 5.9.6 status
[17:02:30] <jaheikki3_> Qt 5.11.1
[17:02:38] <jaheikki3_> Any additional item to the agenda?
[17:04:43] <jaheikki3_> Ok, let's start from Qt 5.9.6 status:
[17:04:50] <thiago> Trying Web IRC
[17:05:04] <jaheikki3_> - Brancing from 5.9 -> 5.9.6 finalized
[17:05:20] <jaheikki3_> Changes file creation ongoing, see https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.6%22,n,z
[17:05:48] <jaheikki3_> Please do needed modifications asap to make sure there won't be delays for the release
[17:06:06] -*- thiago will review on the flight now
[17:06:20] <jaheikki3_> Thanks!
[17:06:26] <jaheikki3_> Target is still to get release out at the beginning of June
[17:07:10] <jaheikki3_> And as earlier we will trust RTA to test release packages -> no official manual test round before release
[17:07:22] <jaheikki3_> Target to create "RC" for RTA testing as soon as possible
[17:07:56] <jaheikki3_> (after all changes files are in and when blcoker list is empty, see https://bugreports.qt.io/issues/?filter=19339)
[17:08:16] <jaheikki3_> That's all about 5.9.6 at this time. Any comments or questions?
[17:10:51] <akseli> sounds like a plan
[17:11:14] <jaheikki3_> Great. Then Qt 5.11.1
[17:11:52] <jaheikki3_> Target is to get first patch release for Qt 5.11 series before summer break
[17:11:56] <thiago> Suggestion: fairly quick, as we have some nasty issues in 5.11.0
[17:12:39] <jaheikki3_> That is my proposal also. I am staring my summer holidays 21.6 and I hope we can get the release out before that
[17:13:06] <jaheikki3_> So I propose to have release target 19.6
[17:13:27] <jaheikki3_> That means we need to start branching from 5.11 -> 5.11.1 at the end of this week
[17:13:59] <jaheikki3_> & finalize the branching at the end of next week
[17:14:20] <jaheikki3_> Blocker list for 5.11.1 here: https://bugreports.qt.io/issues/?filter=19372
[17:14:34] <thiago> Sounds good
[17:15:02] <jaheikki3_> But as usual there shouldn't be that many blockers for 5.11.1 because we will put 5.11.2 out soon after summer break
[17:15:02] <frkleint> thiago: Is this qrc:/ abs path crap fixed ?
[17:15:17] <frkleint> looks for EddyQt...
[17:15:32] <jaheikki3_> frkleint: do you have a bugid for that?
[17:15:37] <frkleint> one sec
[17:16:13] <thiago> frkleint: I was thinking of QSettings not being able to save on Android. 
[17:16:49] <frkleint> hm , no one around,
[17:16:53] <jaheikki3_> thiago: yeah, that is one important issue to be fixed in 5.11.1
[17:17:15] <thiago> It's already fixed. 
[17:17:24] <jaheikki3_> I know
[17:17:59] <The-Compiler> +1 for a quick .1 FWIW, QtWebEngine has some pretty bad bugs too
[17:18:36] <frkleint> hm, can't find it
[17:19:37] <jaheikki3_> Yeah. let's do quick .1 now. We have a plan for it & it should be doable. Hoping we can get most urgent issues fixed there. But for those which can't fixed in time there will be .2 soon as well
[17:20:20] <jaheikki3_> That's was all at this time. Let's have new meeting tue 5.6 as planned
[17:20:55] <jaheikki3_> Thanks for your participation, bye!
[17:20:56] <frkleint> misread Qt 5.6 is planned
[17:21:07] <frkleint> bye
[17:21:19] <thiago> Bye