From jani.heikkinen at qt.io Tue Apr 10 10:56:35 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 10 Apr 2018 08:56:35 +0000 Subject: [Releasing] Qt 5.11 Beta3 released In-Reply-To: References: Message-ID: 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 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: delta_qt511-beta2-qt511-beta3_changes.txt URL: From jani.heikkinen at qt.io Tue Apr 10 16:48:20 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 10 Apr 2018 14:48:20 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 10.4.2018 Message-ID: Meeting minutes from Qt Release Team meeting 10th April 2018 Qt 5.9.5: - Content was ready but new release blocker reported from testing * Fix available. When fix in QtWE then new qt5.git integration + packaging round - Target is to get release out at the end of this week Qt 5.11: - Beta3 released today - RC coming closer, only few blocker without a fix in blocker list (https://bugreports.qt.io/issues/?filter=19209) - Target to start branching from 5.11 -> 5.11.0 during this week & finalize it at the end of week 16. And get RC(1) out at the end of April Qt 5.12 - FF & schedule to be agree * FF should be on August to be able to get final out at the end of November * Jani to clarify branching capability etc on August & sent schedule proposal to ML during this week br, Jani irc log below: [17:01:10] > akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping [17:01:15] jaheikki3_: pong [17:01:27] jaheikki3_: pong [17:01:40] jaheikki3_: pong [17:02:19] Time to start qt release team meeting [17:02:29] On agenda today: [17:02:35] Qt 5.9.5 status [17:02:41] Qt 5.11 status [17:02:48] Any additional item to the agenda? [17:03:55] Lets start from 5.9.5 status: [17:03:58] do we have a 5.12 fature freeze? [17:04:01] date [17:04:35] thiago: Yeah, let's discuss that as well [17:05:05] So 5.9.5: Content was ready but new release blocker reported from testing [17:05:28] huih..which one? [17:05:45] QTBUG-67577 [17:05:46] jaheikki3_: [REG 5.9.4 -> 5.9.5] qt.io shows warning about Certificate Transparency - https://bugreports.qt.io/browse/QTBUG-67577 (In Progress) [17:05:50] hm [17:06:11] We discussed about it with Kai & it is quite visible regression [17:06:53] kakoehne is pretty confoident that he will get a fix/workaround soon [17:07:44] So when we get the fix in then new qt5.git integration + packaging round [17:07:58] Target is still to get release out during this week [17:08:30] Any comments / questions? [17:08:41] what's a certificate transparency problem? [17:09:34] webengine apps (simplebrowser example e.g) throws sertificate error [17:09:55] thiago: ^ [17:10:09] in windows. Linux and mac seems to work OK [17:10:13] the browser thinks it is too old for the certificate or sth [17:11:32] I undersand they do [17:11:35] the question is what that error means [17:11:47] Actually it seems we have a fix already: https://codereview.qt-project.org/#/c/225687/ [17:11:48] jaheikki3_: [qt/qtwebengine-chromium/56-based] [BACKPORT] Certificate Transparency: Generate the known logs list from JSON from Kai Koehne - https://codereview.qt-project.org/225687 (MERGED) [17:12:54] -*- thiago finds https://www.certificate-transparency.org/ [17:13:19] carewolf: Any comments to the issue above? [17:14:28] thiago: The culprit is Qt WebEngine / Chromium enforcing Certificate Transparency for some root certificates by Symantec . And because the list of Certificate Sources we had so far is outdated, some certificates now generate a warning. [17:14:53] ok, thanks [17:15:38] kkoehne_: Thanks. So now QtWE update etc [17:16:04] kkoehne_: or is https://codereview.qt-project.org/#/c/225687/ enough? [17:16:08] kkoehne_: [qt/qtwebengine-chromium/56-based] [BACKPORT] Certificate Transparency: Generate the known logs list from JSON from Kai Koehne - https://codereview.qt-project.org/225687 (MERGED) [17:16:33] jaheikki3_: No, this submodule needs now be updated in qtwebengine.git, and then updated in qt5.git :) [17:18:27] kkoehne_: yes, i understood that :D I was just thinking if that one change is enough for fix the issue or not because thete is comment in the bug report 'https://codereview.qt-project.org/#/c/225687/1 and following patch seems to fix it for me.' [17:18:27] kkoehne_: [qt/qtwebengine-chromium/56-based] [BACKPORT] Certificate Transparency: Generate the known logs list from JSON from Kai Koehne - https://codereview.qt-project.org/225687 (MERGED) [17:20:26] Ok, hoping that fix is enough [17:20:58] That's all about 5.9.5 at this time. Let's get the fix in & get the release out finally... [17:21:10] Then Qt 5.11 status: [17:21:27] Beta3 released today [17:22:06] It seems we are already quite close to RC; there is only few blockers open without a fix in blocker list, see https://bugreports.qt.io/issues/?filter=19209 [17:23:36] So we should start soft branching already during this week [17:23:49] To be ready for RC when all blockers are fixed [17:24:28] It seems we could get RC out at the end of April if nothing new & really serious found anymore [17:24:40] Any comments or questions? [17:27:46] Ok, that's all about 5.11 now [17:27:59] Then Qt 5.12 FF date & overall schedule [17:29:06] To be able to release Qt 5.12 latest at the end of November we need to have FF for it on August like we had with 5.10 and 5.8 [17:29:53] August is not a good FF date [17:30:11] people out in Summer vacations means we don't have reviewers [17:30:40] more importantly, are the people responsible for the branching available? [17:33:23] thiago: well, I need to figure it out. Our mgmt and I as well want to get release out well before Christmas time and that's why end of November is good target (as earlier) [17:34:03] And that's why we need to have FF during August to be able to reach that [17:35:27] I'll check branching capability etc next & sent a proposal in ML during this week. So let's get back to this on next meeting. OK? [17:36:11] ok [17:36:12] thanks [17:37:01] Ok, it was all at this time. Let's end the meeting now & have next one Tue 17.4 at this same time [17:37:17] Thanks for your participation! bye [17:37:41] bye From jani.heikkinen at qt.io Thu Apr 12 10:42:29 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Thu, 12 Apr 2018 08:42:29 +0000 Subject: [Releasing] Qt 5.12 schedule proposal & proposal for release process change In-Reply-To: References: Message-ID: Hi, It is time to start freezing Qt 5.12 schedule. We have the same "limitation" as earlier; we should get the release out well before Christmas time. And it seems we can't cut the time needed from FF to final release that much. It seems we aren't necessarily needing those 17 weeks as before but quite close. So here is my proposal for the schedule: - Soft branching from 'dev' to '5.12' starts 13.8.2018 - Qt 5.12 Feature freeze & finalize branching 20.8.2018 - Final release 29.11.2018 And at this same time I want to propose that we stop delivering alpha or beta releases and just do snapshots instead. Publishing regular snapshots should be done until we are ready for RC. That because I don't see that much need for those anymore. Those are nowadays kind of milestones and in my opinion makes whole process a bit unclear/difficult (we don't have very good definitions for Alpha and Beta releases). So my proposal is: - We start creating (regular) snapshots for Qt 5.12 as soon as possible & continue to publish those until we are ready for RC. - When branching from 'dev' to '5.12' is ready FF is in effect. As earlier new features can't go in after this & we are focusing to fix the bugs & maturing the release - We do API review for release immediately after FF. Discussion about API review process here: http://lists.qt-project.org/pipermail/development/2018-March/032338.html - String freeze will be in effect few weeks (4?) after FF - We keep release blocker list as earlier and when list is clear we branch from 5.12 -> 5.12.0 and do the first RC from release branch - If RC isn't good enough for the final release we just fix those remaining issues and do new RC(s) until we are ready for final release br, Jani Heikkinen Release Manager From edward.welbourne at qt.io Thu Apr 12 12:25:11 2018 From: edward.welbourne at qt.io (Edward Welbourne) Date: Thu, 12 Apr 2018 10:25:11 +0000 Subject: [Releasing] [Development] Maintainers, your action needed: Please check if 3rd party components needs to be updated for Qt 5.11 release In-Reply-To: References: Message-ID: Jani Heikkinen (12 April 2018 11:18) > Please check if some 3rd party component needs to be updated for Qt 5.11 release. There is a new release of CLDR, version 33 (and we've missed version 32, in fact). Whether we *need* to update it, however, is an open question ... We're currently on v31.0.1, Eddy. From lars.knoll at qt.io Thu Apr 12 12:29:55 2018 From: lars.knoll at qt.io (Lars Knoll) Date: Thu, 12 Apr 2018 10:29:55 +0000 Subject: [Releasing] [Development] Maintainers, your action needed: Please check if 3rd party components needs to be updated for Qt 5.11 release In-Reply-To: References: Message-ID: > On 12 Apr 2018, at 12:25, Edward Welbourne wrote: > > Jani Heikkinen (12 April 2018 11:18) >> Please check if some 3rd party component needs to be updated for Qt 5.11 release. > > There is a new release of CLDR, version 33 (and we've missed version 32, in fact). > Whether we *need* to update it, however, is an open question ... > We're currently on v31.0.1, We’ve done a larger upgrade of all other unicode related things for 5.11, so adding this would round in principle off the whole thing. But I don’t think there’s a huge need to do the update, so I propose we do it for 5.12, ideally combined with an upgrade to Unicode 11 (once it’s released). Cheers, Lars From jani.heikkinen at qt.io Thu Apr 12 13:46:46 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Thu, 12 Apr 2018 11:46:46 +0000 Subject: [Releasing] Qt 5.9.5 released In-Reply-To: References: Message-ID: 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 From edward.welbourne at qt.io Thu Apr 12 14:48:48 2018 From: edward.welbourne at qt.io (Edward Welbourne) Date: Thu, 12 Apr 2018 12:48:48 +0000 Subject: [Releasing] [Development] Maintainers, your action needed: Please check if 3rd party components needs to be updated for Qt 5.11 release In-Reply-To: References: , Message-ID: Jani Heikkinen (12 April 2018 11:18) prompted: >>> Please check if some 3rd party component needs to be updated for Qt 5.11 release. On 12 Apr 2018, at 12:25, Edward Welbourne wrote: >> There is a new release of CLDR, version 33 (and we've missed version 32, in fact). >> Whether we *need* to update it, however, is an open question ... >> We're currently on v31.0.1, Lars Knoll (12 April 2018 12:29) > We’ve done a larger upgrade of all other unicode related things for > 5.11, so adding this would round in principle off the whole thing. But > I don’t think there’s a huge need to do the update, so I propose we do > it for 5.12, ideally combined with an upgrade to Unicode 11 (once it’s > released). OK, duly rescheduled to dev rather than 5.11: * https://bugreports.qt.io/browse/QTBUG-67654 for anyone interested. I'll leave the Unicode 11 work for someone else to plan ... Eddy. From jani.heikkinen at qt.io Thu Apr 12 15:52:53 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Thu, 12 Apr 2018 13:52:53 +0000 Subject: [Releasing] HEADS-UP: Branching '5.11.0' from '5.11' started Message-ID: Hi all, We have soft branched '5.11.0' from '5.11'. Please start using '5.11.0' for new changes targeted to Qt 5.11.0 release. Final downmerge from '5.11' to '5.11.0' will happen Thursday 19th April so there should be enough time to finalize ongoing changes in '5.11' and start using '5.11.0' for new ones. We are targeting to release Qt 5.11.0 rc before end of April so please make sure all blockers are fixed immediately. Qt 5.11.0 RC blocker list here: https://bugreports.qt.io/issues/?filter=19209 br, Jani Heikkinen Release Manager From jani.heikkinen at qt.io Tue Apr 17 16:19:41 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 17 Apr 2018 14:19:41 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 17.4.2018 Message-ID: Meeting minutes from Qt Release Team meeting 17th April 2018 Qt 5.11: - Branching from 5.11 -> 5.11.0 ongoing, target is to finalize branching at the end of this week - Target is to get beta4 out during this week - Target to get RC out at the end of this month * Blocker list https://bugreports.qt.io/issues/?filter=19209 Qt 5.12 initial schedule - FF & Alpha release 20.8.2018 - Beta1 18.9.2018 - RC 15.11.2018 - Final release 29.11.2018 Next meeting Tue 24.4.2018 16:00 CET br, Jani irc log below: [17:00:43] akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping [17:00:49] jaheikki3_: pong [17:03:05] Time to start qt release team meeting [17:03:11] On agenda today: [17:03:18] Qt 5.11 status [17:03:23] Qt 5.12 initial schedule [17:03:31] Any additional item to the agenda [17:03:36] ? [17:04:36] jaheikki3_: pong [17:05:28] Let's start from 5.11 status: [17:05:54] Branching from 5.11 -> 5.11.0 ongoing. [17:06:02] Target to finalize branching at the end of this week [17:06:28] Target is to get beta4 out during this week as well [17:07:04] And target is to get RC out at the end of this month [17:07:18] RC blocker list here: Blocker list https://bugreports.qt.io/issues/?filter=19209 [17:08:25] 7 open at the moment but ~ half of those has a fix already available [17:09:04] That's all about 5.11 status at this time. Any comments or questions? [17:09:32] plan sounds good to me [17:10:11] Ok, then Qt 5.12 initial schedule: [17:10:39] Proposal sent to ML last week [17:11:22] No comments to schedule but active discussion related to my proposal for process change [17:11:47] Conclusion seems to be that we shouldn't change the process and that's OK for me as well [17:12:07] So here are initial schedule for Qt 5.12: [17:12:26] FF and Alpha release 20.8.2018 [17:12:38] Beta1 18.9.2018 [17:12:45] RC 15.11.2018 [17:12:55] Final release 29.11.2018 [17:13:41] Any comments or questions? [17:14:16] no [17:14:44] Great. This was all at this time. [17:15:07] Let's have new meeting Tue 24th April as planned [17:15:18] Thanks for your participation. Bye! [17:15:25] thanks, bye [17:15:26] oki [17:15:26] bye From jani.heikkinen at qt.io Fri Apr 20 11:02:37 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Fri, 20 Apr 2018 09:02:37 +0000 Subject: [Releasing] Qt 5.11 Beta4 released In-Reply-To: References: Message-ID: Hi all, Qt 5.11 beta4 is released today. As usual you can get it via online installer. Delta to beta3 as an attachment. We are planning to release RC at the end of April 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 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: delta_qt511-beta3-qt511-beta4.txt URL: From jani.heikkinen at qt.io Fri Apr 20 12:28:58 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Fri, 20 Apr 2018 10:28:58 +0000 Subject: [Releasing] HEADS-UP: Branching '5.11.0' from '5.11' completed In-Reply-To: References: Message-ID: Hi! Branching from '5.11' to '5.11.0' is now ready. From now on '5.11' is for Qt 5.11.1 and all changes targeted to Qt 5.11.0 release must be done in '5.11.0'. And remember: We are trying to get RC out at the end of April so no any nice-to-haves in anymore. As usual release team will create initial changes files for Qt 5.11.0 as soon as possible. Please make sure you will do needed modifications there without any delay br, Jani ________________________________________ From: Development on behalf of Jani Heikkinen Sent: Thursday, April 12, 2018 4:52 PM To: development at qt-project.org Cc: releasing at qt-project.org Subject: [Development] HEADS-UP: Branching '5.11.0' from '5.11' started Hi all, We have soft branched '5.11.0' from '5.11'. Please start using '5.11.0' for new changes targeted to Qt 5.11.0 release. Final downmerge from '5.11' to '5.11.0' will happen Thursday 19th April so there should be enough time to finalize ongoing changes in '5.11' and start using '5.11.0' for new ones. We are targeting to release Qt 5.11.0 rc before end of April so please make sure all blockers are fixed immediately. Qt 5.11.0 RC blocker list here: https://bugreports.qt.io/issues/?filter=19209 br, Jani Heikkinen Release Manager _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development From edward.welbourne at qt.io Fri Apr 20 16:22:40 2018 From: edward.welbourne at qt.io (Edward Welbourne) Date: Fri, 20 Apr 2018 14:22:40 +0000 Subject: [Releasing] Qt 5.11 Alpha released In-Reply-To: References: , , Message-ID: 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/ I wrote (21 February 2018 17:43) > and so, of course, we also have 5.11 API reviews, vs v5.10.1: and while eight of these are resolved, https://codereview.qt-project.org/221041 qtmultimedia https://codereview.qt-project.org/221043 qtxmlpatterns https://codereview.qt-project.org/221045 qtconnectivity https://codereview.qt-project.org/221048 qtserialbus https://codereview.qt-project.org/221049 qtandroidextras https://codereview.qt-project.org/221051 qtcharts https://codereview.qt-project.org/221052 qtgamepad https://codereview.qt-project.org/221053 qtremoteobjects seven remain unresolved. I've updated these to the 5.11.0 branch, to pick up any changes since my last update: https://codereview.qt-project.org/221039 qtbase https://codereview.qt-project.org/221040 qtdeclarative https://codereview.qt-project.org/221042 qttools https://codereview.qt-project.org/221044 qtlocation https://codereview.qt-project.org/221046 qtwayland https://codereview.qt-project.org/221047 qt3d https://codereview.qt-project.org/221050 qtwebengine Please take a look at those and deal with any outstanding issues - sooner rather than later. Please file sub-tasks of QTBUG-67191 for any issues you raise: it should raise their visibility, as this task is a P1 blocker for the release ! Eddy. From jani.heikkinen at qt.io Tue Apr 24 16:13:31 2018 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Tue, 24 Apr 2018 14:13:31 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 24.4.2018 Message-ID: Meeting minutes from Qt Release Team meeting 24th April 2018 Qt 5.11 status: - Beta4 released - Branching completed - Initial changes files created, work ongoing to finalize those * https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.11.0%22,n,z * We need to get all those in Wed EOB to be able to get RC out as planned - 8 blockers open in the blocker list, see https://bugreports.qt.io/issues/?filter=19209 * Only one issue without a fix (proposal) - Target is still to get RC out at the end of April Next meeting Tue 8.5.2018 16:00 CET br, Jani irc log below: [17:00:26] akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:lars: ping [17:00:28] jaheikki3_: pong [17:00:38] jaheikki3_: pong [17:00:47] poing [17:01:12] Time to start Qt release team meeting [17:01:16] On agenda today: [17:01:23] - Qt 5.11 status [17:01:29] jaheikki3_: pong [17:01:33] Any additional item to the agenda? [17:01:46] jaheikki3_: pong [17:02:51] Ok, let's browse through 5.11 status [17:03:04] Beta4 released [17:03:10] branching complete [17:03:27] Initial changes files created, work ongoing to finalize those. See https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.11.0%22,n,z [17:03:54] We need to get all those in Wed EOB to be able to get RC out as planned. I'll stage all approved one later today [17:04:10] 8 blockers open in the blocker list, see https://bugreports.qt.io/issues/?filter=19209 [17:04:23] Luckily only one without a fix [17:05:02] So pretty good situation atm [17:05:30] Target is stil lto get RC out at the end of this month; lets see if that will happen [17:05:59] But that's all about the status at this time. Any comments or questions? [17:06:04] looks like we're on track [17:08:53] Ok, it was all at this time. Next Tue (1st of May) is holiday at least in Finland so let's skip the meeting then & have next one Tue 8.5.2018 [17:09:30] sounds good [17:10:07] Great. Thanks for your participation. [17:10:10] Bye! [17:10:13] bye [17:10:49] bye