From jani.heikkinen at qt.io  Sat Sep  2 14:23:46 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Sat, 2 Sep 2017 12:23:46 +0000
Subject: [Releasing] HEADS-UP: Branching from 'dev' to '5.10' completed
Message-ID: <HE1PR02MB31324B6B9EF3D1344C33E8999D930@HE1PR02MB3132.eurprd02.prod.outlook.com>

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.io at qt-project.org] On Behalf Of Jani Heikkinen
Sent: sunnuntai 27. elokuuta 2017 12.02
To: development at qt-project.org
Cc: releasing at 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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20170902/b8e03a43/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20170902/b8e03a43/attachment.txt>

From jani.heikkinen at qt.io  Mon Sep  4 17:55:30 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Mon, 4 Sep 2017 15:55:30 +0000
Subject: [Releasing] HEADS-UP: Branching from '5.6' to '5.6.3' completed
Message-ID: <HE1PR02MB313297EF7BD45B36A07780719D910@HE1PR02MB3132.eurprd02.prod.outlook.com>

Hi all,

We have branched '5.6.3' from '5.6' today. All changes targeted to Qt 5.6.3 release must be done in '5.6.3' and '5.6' is for Qt 5.6.4 from now on. And as usual only release team will have staging rights in '5.6.3'

br,
Jani

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20170904/19259750/attachment.html>

From jani.heikkinen at qt.io  Wed Sep  6 06:53:28 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 6 Sep 2017 04:53:28 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 05.09.2017
Message-ID: <HE1PR02MB3132A5683B71D4E2187E8DDC9D970@HE1PR02MB3132.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 5th September 2017

Qt 5.10 status:
- Branching from 'dev' to '5.10' ready
- Target to get Alpha out as soon as possible
   * first we need to get qt5.git integrated in '5.10'. Some problems there, work ongoing to fix those as soon as possible
   * Then export the src packages, run some sanity checks & if all OK publish Alpha
- Target to publish binary snapshot based on Alpha packages soon after Alpha release
- API review to be started immediately when Alpha content in place
- Target is also to get first beta out soon after the Alpha release

Qt 5.6.3 status:
- Branching from '5.6' -> '5.6.3' done
- First testing round done as well and content seems to be pretty much ok
- Change file creation still ongoing. When remaining ones in we need to direct push those in '5.6.3' 
- Then qt5.git integration in '5.6.3', packaging and final testing for the packages. And if all OK we should be ready for Qt 5.6.3 release
- ('5.6' will be closed until 5.6.3 is out.)

Qt 5.9.2 status:
- Target to start branching after qt5 merge from '5.6.3' done
- Testing also ongoing; nothing alarming reported so far.
- Change files to be created immediately after we have branched from '9.2'
   * Soft branching will be used as usual.
- Target to get release out during September

Next meeting Tue 12th September 2017 16:00 CET

br,
Jani

irc log below:
[17:00:44] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping 
[17:00:51] <ankokko_> jaheikki3: pong
[17:00:52] <akseli> jaheikki3: pong
[17:00:54] <frkleint> jaheikki3: pong
[17:01:47] <thiago> jaheikki3: pong
[17:02:35] <jaheikki3> time to start qt release team meeting
[17:02:42] <jaheikki3> on agenda today:
[17:02:51] <jaheikki3> - Qt 5.10 status
[17:02:58] <jaheikki3> - Qt 5.6.3 status
[17:03:06] <jaheikki3> - Qt 5.9.2 status
[17:03:13] <carewolf> pong
[17:03:14] <jaheikki3> Any additional item to the agenda?
[17:04:25] <thiago> not to the agenda, but can someone post an initial schedule for 5.11 feature freeze?
[17:05:33] <jaheikki3> thiago: I'll take an action point & do it. But as with 5.9 it will be ~befinning of Feb. I will check it & sent an mail to MLs
[17:05:48] <thiago> thanks
[17:05:58] <jaheikki3> ok, lets start from Qt 5.10 status:
[17:06:09] <jaheikki3> - Branching complete
[17:06:34] <jaheikki3> - Target to get alpha out as soon as we can get qt5.git integration succeed in '5.10'
[17:07:00] <jaheikki3> unfortunately there seems to be some problems with it, see https://codereview.qt-project.org/#/c/204362/
[17:07:01] <qt_gerrit> jaheikki3: [qt/qt5/5.10] Update submodules on '5.10' in qt5 from Qt Submodule Update Bot - https://codereview.qt-project.org/204362 (INTEGRATING)
[17:07:50] <jaheikki3> thiago: your change (https://codereview.qt-project.org/#/c/204229/) seems to cause some there as well, please see JP's comments
[17:07:51] <qt_gerrit> thiago: [qt/qtbase/5.10] Make qAddPostRoutine & family thread-safe from Thiago Macieira - https://codereview.qt-project.org/204229 (MERGED)
[17:08:26] <thiago> jaheikki3: push already submitted and integrating
[17:08:39] <thiago> sheesh, that's so an hour ago :-)
[17:09:06] <frkleint> How about all those Quick Controls test errors...are they under control?
[17:09:21] <jaheikki3> great, thanks!
[17:09:33] <jaheikki3> frkleint: should be, let's see...
[17:11:12] <jaheikki3> But otherwise we should be ready for the alpha.After qt5.git integration we need just to export src packages, run some sanitychecks & if all OK publish Alpha
[17:11:25] <jaheikki3> Target is to get it out still during this week
[17:11:59] <jaheikki3> And we are planning to publish binary snapshot based on Alpha content soon as well
[17:12:42] <thiago> nice
[17:13:23] <jaheikki3> And I hope we can release Beta1 quite soon after the Alpha release. I think it should be doable & ok because target is to create several betas as with 5.9 and so on first one doesn't need to be perfect one. 
[17:13:46] <frkleint> Has Edward been poked to create Header diffs?
[17:13:46] <jaheikki3> What is mandatory things to be done before beta1 release?
[17:13:56] <frkleint> Header diffs, BIC?
[17:14:08] <frkleint> API review...
[17:14:19] <jaheikki3> frkleint: not yet. I was planning to do immediately after alpha is out
[17:14:27] <frkleint> ok, the sooner the better
[17:14:42] <thiago> API review must finish before RC
[17:14:48] <thiago> but it doesn't need to finish before the betas
[17:15:00] <jaheikki3> I agree
[17:15:35] <jaheikki3> Target is to start first round immediately after alpha but I don't think we need to complete it before beta1
[17:16:54] <jaheikki3> So is there anything which we really have to complete before first beta release? Or can we put it out when testing indicates binaries are good enough to start wider testing?
[17:19:19] <jaheikki3> Lets get back to beta1 when alpha is out & first feedback available
[17:19:29] <frkleint> [a quick sanity check for a BC break or wildly odd API would be comforting, but anyways]
[17:20:01] <thiago> the BIC check should be running
[17:20:08] <thiago> are the 5.9.0 files imported, finally?
[17:20:31] <jaheikki3> thiago: To be honest I am not sure but will check with Milla tomorrow
[17:21:01] <jaheikki3> But that is pretty much all about 5.10 at this time
[17:21:11] <jaheikki3> Then Qt 5.6.3 status:
[17:21:30] <jaheikki3> - Brabching from '5.6' -> '5.6.3' done
[17:22:01] <jaheikki3> - First testing round done as well and content seems to be pretty much ok
[17:22:37] <jaheikki3> - Change file creation still ongoing, see https://codereview.qt-project.org/#/q/message:%22Add+change+file+for%22,n,z
[17:23:04] <jaheikki3> When remaining ones in we need to direct push those in '5.6.3' 
[17:23:46] <jaheikki3> Then qt5.git integration in '5.6.3', package creation & final testing 
[17:24:06] <jaheikki3> And if all ok we should be ready for QT 5.6.3 release
[17:24:22] <jaheikki3> Any comments / questions ?
[17:24:34] <thiago> just make sure no one pushes to 5.6
[17:24:37] <fregl> sounds good for 5.6.3
[17:24:40] <thiago> only to 5.6.3 branch
[17:25:04] <jaheikki3> that's ok for me. fregl: could you disable staging in '5.6' ?
[17:25:41] <fregl> thiago: there were actually some minor things in qt5.git that went into the 5.6 branch already, they are completely insignificant infrastructure bits. not sure why they had to go there, but seems the release team is not really coordinating on this kind of thing.
[17:25:47] <fregl> jaheikki3: OK
[17:26:08] <thiago> just make one final fast-forward merge and disable
[17:26:11] <thiago> we don't need two branches
[17:27:13] <fregl> it's disabled now, but yeah, we could merge I presume
[17:28:08] <jaheikki3> fregl: that's OK as well even we don't need those changes in '5.6.3'
[17:29:00] <fregl> actually it's not ff since the submodule branches were adjusted in 5.6.3 :(
[17:29:14] <fregl> but yeah, since the changes are only for provisioning, let's ignore them
[17:29:26] <jaheikki3> And for the future should be restrict staging in '5.6' somehow? Now it seems everyone has rights...
[17:30:11] <fregl> one of them is a complete no-op anyway, not sure about the other two
[17:30:39] <fregl> jaheikki3: now nobody can stage, that includes the release team, since they were the ones dropping in stuff
[17:31:09] <fregl> and only the release team can stage in 5.6.3.
[17:31:15] <jaheikki3> fregl: yeah, and thats totally ok now;) But I meant time after 5.6.3 release
[17:31:37] <fregl> let's chat then, we can add the release team again
[17:31:39] <frkleint> Some sort of maintainer approval maybe, but we cannot decide here
[17:32:08] <fregl> considering how little change 5.6 should see, I think release team is fine then
[17:32:21] <fregl> if that doesn't scale we can discuss it on the mailing list
[17:32:34] <jaheikki3> agree
[17:33:55] <jaheikki3> But let's get back to this when Qt 5.6.3 is out & when we will enable staging again in '5.6'
[17:34:37] <thiago> yeah
[17:34:41] <jaheikki3> Then 5.9.2 status
[17:35:27] <jaheikki3> - Target to start branching after qt5 merge from '5.6.3' done
[17:36:16] <jaheikki3> - Testing also ongoing; nothing alarming reported so far. Mostly some packaging related issues which is quite trivial to be fixed
[17:36:38] <thiago> and the SHA3 thing
[17:37:45] <carewolf> change files?
[17:38:04] <jaheikki3> carewolf: Yes, those needs to be done immediately after we have branched
[17:38:27] <jaheikki3> thiago: true, is than already ok?
[17:38:41] <thiago> waiting for one final reply on whether it's opt-in or opt-out
[17:39:31] <jaheikki3> ok
[17:40:36] <jaheikki3> But overall we are quite close to release there as well. Target to get it out during September, preferrably withing coming two weeks
[17:40:44] <jaheikki3> Any other comments or questions?
[17:41:47] <thiago> September looks good
[17:42:17] <jaheikki3> I have one: Do we need to do soft branching with 5.9.2 or can we do it immediately when ready? 
[17:42:34] <thiago> 5.9 is a different case, since there are more changes
[17:42:35] <thiago> for now
[17:42:52] <thiago> maybe for later releases we'll do it differently
[17:43:17] <jaheikki3> Ok for me, let's use soft branching now as usual
[17:44:22] <jaheikki3> Ok, this was all at this time. Let's have new meeting Tue 12 Sep as planned
[17:44:33] <jaheikki3> Thanks for your participation. Bye!
[17:44:44] <ankokko_> bye
[17:46:14] <fregl> cy
[17:46:19] <fregl> cu :)

From jani.heikkinen at qt.io  Wed Sep 13 08:19:45 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 13 Sep 2017 06:19:45 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 12.09.2017
Message-ID: <HE1PR02MB3132B5D16B19EBCE9F1677759D6E0@HE1PR02MB3132.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 12th September 2017

Qt 5.10 status:
- Alpha content finally in place
- RTA for src packages ongoing
- We will release these packages as Qt 5.10 Alpha Wed 13th September 2017 (if nothing serious found during RTA)

Qt 5.6.3 status:
- Qt 5.6.3 content in place, qt5.git integration ongoing
- Target to create Qt 5.6.3 packages immediately after qt5.git integration succeed
- We will release those packages as Qt 5.6.3 (if nothing really serious found during final testing)
   * Target: Beginning of week 38

Qt 5.9.2 status:
- Branching not started yet
   * We will get merge from '5.6.3' in '5.9' first & start branching after that
- Target is to get Qt 5.9.2 out during September

Next meeting Tue 26th September 2017 16:00 CET

br,
Jani

irc log below:
[17:00:11] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping
[17:00:20] <akseli> jaheikki3: pong
[17:00:27] <thiago> jaheikki3: pong
[17:00:59] <frkleint> jaheikki3:pong
[17:01:02] <jaheikki3> Time to start qt release team meeting
[17:01:08] <jaheikki3> On agenda today:
[17:01:16] <jaheikki3> Qt 5.10 status
[17:01:22] <jaheikki3> Qt 5.6.3 status
[17:01:27] <jaheikki3> Qt 5.9.2 status
[17:01:35] <jaheikki3> Any additional item to the agenda?
[17:03:26] <carewolf> pong
[17:03:27] <jaheikki3> Ok, lets starts from 5.10 status:
[17:03:40] <jaheikki3> - We have alpha content finally in place
[17:04:12] <jaheikki3> qt5.git integration succeed & we have created alpha src packages
[17:04:27] <jaheikki3> RTA for src packages ongoing
[17:05:02] <jaheikki3> If nothing really serious found we will release these src packages as Qt 5.10 Alpha tomorrow
[17:05:15] <thiago> great
[17:05:19] <thiago> gj
[17:06:21] <jaheikki3> I have also asked eddy to start API review
[17:07:21] <jaheikki3> And target is to get first beta snapshot out quite soon and as discussed last time get first beta out within coming weeks
[17:07:33] <jaheikki3> Any comments or questions?
[17:07:45] <carewolf> sounds good
[17:09:06] <jaheikki3> Thats all about 5.10 at this time. Then Qt 5.6.3 status:
[17:09:36] <jaheikki3> We should have Qt 5.6.3 content in place now; last fix went in today
[17:09:44] <jaheikki3> qt5.git integration is ongoing
[17:10:39] <jaheikki3> When it succeed we will create final packages for final testing and if all goes OK plan is to release those packages as Qt 5.6.3
[17:11:32] <jaheikki3> Most probably release will be at the beginning of next week; there isn't enough time to get all done so that we could get release out still during this week
[17:11:47] <jaheikki3> Any comments / questions?
[17:13:17] <jaheikki3> Ok, thats all about 5.6.3. Then Qt 5.9.2 status:
[17:13:24] <jaheikki3> Branching not started yet
[17:13:54] <jaheikki3> We will get merge from '5.6.3' in '5.9' first & start branching after that
[17:14:18] <jaheikki3> Then create packages for testing & start change file creation 
[17:14:49] <jaheikki3> And target is to get Qt 5.9.2 out during September
[17:16:10] <jaheikki3> Any comments or questions?
[17:16:49] <akseli> sounds like a plan
[17:17:13] <jaheikki3> It was all at this time. let's skip next weeks meeting & have new one Tue 26 September. OK?
[17:17:29] <akseli> +1
[17:17:42] <thiago> ok
[17:18:06] <jaheikki3> great. thanks for your participation. Bye!
[17:18:11] <frkleint> byew
[17:18:19] <akseli> bye
[17:18:37] <carewolf> bye






From edward.welbourne at qt.io  Wed Sep 13 10:54:12 2017
From: edward.welbourne at qt.io (Edward Welbourne)
Date: Wed, 13 Sep 2017 08:54:12 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting
 05.09.2017
In-Reply-To: <HE1PR02MB3132A5683B71D4E2187E8DDC9D970@HE1PR02MB3132.eurprd02.prod.outlook.com>
References: <HE1PR02MB3132A5683B71D4E2187E8DDC9D970@HE1PR02MB3132.eurprd02.prod.outlook.com>
Message-ID: <VI1PR02MB3264F403E3BAAA44AF6515F1876E0@VI1PR02MB3264.eurprd02.prod.outlook.com>

Jani Heikkinen (6 September 2017 06:53)
> Meeting minutes from Qt Release Team meeting 5th September 2017
>
> Qt 5.10 status:
[...]
> - API review to be started immediately when Alpha content in place

No API changes found in:
qtsvg, qtactiveqt, qtscript, qttools, qtxmlpatterns, qtsensors,
qtimageformats, qtgraphicaleffects, qtquickcontrols, qtserialport,
qtmacextras, qtwinextras, qtwebsockets, qtwebchannel, qtcanvas3d,
qtwebview, qtquickcontrols2, qtpurchasing, qtcharts, qtdatavis3d,
qtvirtualkeyboard, qtgamepad, qtspeech.

If you believe there have been changes to APIs in these modules, between
v5.9.0 and the 5.10 branch, please bring them to my attention.

Note that the introduction of QStringView is in this review.
I was surprised to find qtbase/src/3rdparty/zlib/ contributing; but it
is indeed mentioned in sync.profile, so got included.

Change reviews generated:

https://codereview.qt-project.org/205317 -- qtbase
https://codereview.qt-project.org/205318 -- qtdeclarative
https://codereview.qt-project.org/205319 -- qtmultimedia
https://codereview.qt-project.org/205320 -- qtlocation
https://codereview.qt-project.org/205321 -- qtconnectivity
https://codereview.qt-project.org/205322 -- qtwayland
https://codereview.qt-project.org/205323 -- qt3d
https://codereview.qt-project.org/205324 -- qtserialbus
https://codereview.qt-project.org/205325 -- qtx11extras
https://codereview.qt-project.org/205326 -- qtandroidextras
https://codereview.qt-project.org/205327 -- qtwebengine
https://codereview.qt-project.org/205328 -- qtscxml
https://codereview.qt-project.org/205329 -- qtnetworkauth
https://codereview.qt-project.org/205330 -- qtremoteobjects

Please note that the API review, though presented as a change to 5.10,
is in fact a simplified diff between v5.9.0 and the current 5.10 branch,
in which certain kinds of "boring" change are ignored.  This can lead to
the end-state you're shown not matching what you know the code currently
says; this is just because the script tried to leave out irrelevant
differences between 5.9.0 and 5.10, so that you can focus on how the API
and ABI might have changed.

I've restored constexpr changes to being shown - allegedly we can't
retract those once added.  I believe Q_INVOKABLE is also genuinely
API-relevant, so it is also not filtered.  Should Q_DECL_CONST_FUNCTION
changes be ignored ?  Q_NORETURN ?  The currently aren't.

I have arranged for the script to ignore #if QT_CONFIG(token) replacing
#ifndef QT_NO_TOKEN (complete with the various ways that can be spelt,
but without the matching handling of #endif comments).  There were a lot
of those in this review, otherwise; likewise for while (0) being turned
into while (false).

	Eddy.


From jani.heikkinen at qt.io  Wed Sep 13 11:24:32 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 13 Sep 2017 09:24:32 +0000
Subject: [Releasing] Qt 5.10 Alpha released
Message-ID: <HE1PR02MB31328D8F16DB730516D929319D6E0@HE1PR02MB3132.eurprd02.prod.outlook.com>

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





From jani.heikkinen at qt.io  Wed Sep 20 12:51:56 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 20 Sep 2017 10:51:56 +0000
Subject: [Releasing] HEADS-UP: Branching '5.9.2' from '5.9' started
Message-ID: <HE1PR02MB31327192687991404F1184099D610@HE1PR02MB3132.eurprd02.prod.outlook.com>

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






From jani.heikkinen at qt.io  Thu Sep 21 12:11:11 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 21 Sep 2017 10:11:11 +0000
Subject: [Releasing] Qt 5.6.3 released
In-Reply-To: <HE1PR02MB3132E4597788F5F1C4F2B21B9D660@HE1PR02MB3132.eurprd02.prod.outlook.com>
References: <HE1PR02MB3132E4597788F5F1C4F2B21B9D660@HE1PR02MB3132.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB3132078E3737A2538C4C23DD9D660@HE1PR02MB3132.eurprd02.prod.outlook.com>

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



From jani.heikkinen at qt.io  Mon Sep 25 19:34:20 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Mon, 25 Sep 2017 17:34:20 +0000
Subject: [Releasing] HEADS-UP: Branching '5.9.2' completed
Message-ID: <AM4PR02MB31228FCE9A7A0283481BDA609D7A0@AM4PR02MB3122.eurprd02.prod.outlook.com>

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 at qt-
> project.org] On Behalf Of Jani Heikkinen
> Sent: keskiviikko 20. syyskuuta 2017 13.52
> To: development at qt-project.org
> Cc: releasing at 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 at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


From jani.heikkinen at qt.io  Wed Sep 27 08:25:55 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 27 Sep 2017 06:25:55 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 26.09.2017
Message-ID: <HE1PR02MB31326BF2D8AB506D50A208249D780@HE1PR02MB3132.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 26th September 2017

Qt 5.9.2 status:
- Creating new binary snapshot ongoing
   * Target to start testing Wed 27th September
- Content should be already quite close to final release
   * Some change files still missing (see https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.2%22,n,z )
   * At least one fix for open blocker needed (see https://bugreports.qt.io/issues/?filter=18736)
   --> One qt5.git update needed before we have final packages available
- Target is to test packages, fix possible new blockers and release Qt 5.9.2 as soon as possible
   * Current target for Qt 5.9.2 release; week 40

Qt 5.10 status:
- Target to get new binary snapshot for testing as soon as possible
   * Unfortunately we still use old macOS 10.10 in packaging builds and that's why qtwebengine cannot be compiled in '5.10'.  fix is already coming in (start using macOS 10.12)
- Beta 1 blocker list here: https://bugreports.qt.io/issues/?filter=18949
   * Currently 2 issues open
- Target to get Beta 1 out during next week (week 40)

Next meeting Tue 3rd October 16:00 CET

br,
Jani

irc log below:
[17:00:37] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping 
[17:00:57] <akseli> jaheikki3: pong
[17:01:14] <frkleint> jaheikki3: pong
[17:01:44] <jaheikki3> Time to start qt release team meeting
[17:01:49] <jaheikki3> On agenda today:
[17:01:59] <jaheikki3> Qt 5.9.2 release status
[17:02:02] <jaheikki3> Qt 5.10 status
[17:02:11] <jaheikki3> Any additional item to the agenda?
[17:03:35] <jaheikki3> Ok, let's start from Qt 5.9.2 status:
[17:03:50] <jaheikki3> Creating new binary snapshot ongoing
[17:04:15] <jaheikki3> We should be able to start testing it tomorrow
[17:05:22] <jaheikki3> Content should be already quite close to final release; Some change files still missing + fix for one open blocker (see https://bugreports.qt.io/issues/?filter=18736)
[17:05:44] <jaheikki3> So at least one qt5.git update needed before we have final packages available
[17:06:31] <jaheikki3> Target is to test packages, fix possible new blockers and release Qt 5.9.2 as soon as possible
[17:07:03] <jaheikki3> I hope we could get release out during next week
[17:07:22] <jaheikki3> Any comments or questions
[17:08:49] <jaheikki3> Ok, that was all about Qt 5.9.2 at the moment
[17:09:01] <jaheikki3> Then Qt 5.10 status:
[17:09:47] <jaheikki3> We are targeting to get binary snapshot for testing as soon as possible
[17:10:44] <jaheikki3> Unfortunately we still use old macOS 10.10 in packaging builds and that's why qtwebengine cannot be compiled in '5.10'
[17:11:00] <jaheikki3> fix is already coming in (start using masOS 10.12)
[17:11:21] <jaheikki3> so we should be able to create binary packages for testing still during this week
[17:12:30] <jaheikki3> Let's see if we found new beta 1 blockers when testing the snapshot... At the moment there is couple of open ones in blocker list (see https://bugreports.qt.io/issues/?filter=18949)
[17:12:54] <jaheikki3> I am hoping we could get beta 1 out during next week as well
[17:13:02] <jaheikki3> Any comments or questions?
[17:13:27] <frkleint> API review/BIC checks in progress?
[17:13:40] <jaheikki3> frkleint: yes
[17:13:59] <jaheikki3> Eddy started it immediately after Alpha
[17:14:46] <thiago> API review is in progress
[17:14:53] <thiago> we've already fixed a number of things
[17:15:00] <thiago> QNativeGestureEvent BC break is not yet fixed
[17:15:09] <frkleint> Huh,did I miss sth..
[17:16:17] -*- thiago can't search for "API review" in his gerrit emails because all emails have "review"
[17:16:44] <frkleint> WIP: API comparison from v5.9.0 to 5.10, found it
[17:17:33] <jaheikki3> But this was all about the status at this time
[17:17:55] <jaheikki3> Lets have new meeting Tue 3.10 as planned
[17:18:18] <jaheikki3> Thanks for your participation. Bye



From jani.heikkinen at qt.io  Wed Sep 27 13:47:07 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 27 Sep 2017 11:47:07 +0000
Subject: [Releasing] Qt 5.9.2 snapshot for testing
Message-ID: <HE1PR02MB3132880C718BA339B0C1CFAD9D780@HE1PR02MB3132.eurprd02.prod.outlook.com>

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