From jani.heikkinen at qt.io  Wed Oct  4 09:11:22 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 4 Oct 2017 07:11:22 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 3.10.2017
Message-ID: <HE1PR02MB3132EC3D1C0A2594A25CBDB29D730@HE1PR02MB3132.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 3rd October 2017

Qt 5.9.2 status:
- We should finally have final content in place
- Target to get final packages for sanity checking Wed 4th October & get the release out during this week if nothing really serious found.

Qt 5.10 status:
- Creating new binary snapshot ongoing
   * should contain fixes for almost all beta 1 blockers; only couple of Qt QuickControls2 issues still open see https://bugreports.qt.io/issues/?filter=18949
      ** Discussion ongoing if we should block beta1 because of those or not
- Target is to run RTA for snapshot & check if snapshot is well enough for Qt 5.10 Beta 1 or not
- If snapshot is good enough we are targeting to release beta 1 on Friday or latest at the beginning of next week

Next meeting Tue 17th October 16:00 CET

br,
Jani

irc log below:
[17:00:35] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping
[17:02:06] <jaheikki3> Time to start qt release team meeting
[17:02:12] <jaheikki3> on agenda today
[17:02:26] <jaheikki3> Qt 5.9.2 status
[17:02:30] <jaheikki3> Qt 5.10 status
[17:02:40] <jaheikki3> Any additional item to the agenda?
[17:04:11] <jaheikki3> Ok, lets start from Qt 5.9.2 status:
[17:04:25] <jaheikki3> We should finally have final content in place
[17:04:49] <jaheikki3> fix for last blocker now in & qt5.git integration ongoing
[17:05:54] <jaheikki3> hoping qt5.git integration succeed now at once and we could create final packages for satity checking tomorrow morning
[17:06:16] <jaheikki3> Then we could get release out still during this week
[17:06:40] <jaheikki3> That's all about 5.9.2 status. Any comments or questions?
[17:08:34] <jaheikki3> Ok, then Qt 5.10 status
[17:08:51] <jaheikki3> Creating new binary snapshot ongoing
[17:11:32] <jaheikki3> it should contain fixes for almost all beta 1 blockers; only couple of Qt QuickControls2 issues still open see https://bugreports.qt.io/issues/?filter=18949
[17:11:53] <jaheikki3> Discussion ongoing if we should block beta1 because of those or not
[17:13:02] <jaheikki3> Target is to run RTA for that snapshot & then agree if snapshot is well enough for Qt 5.10 Beta 1 or not
[17:14:01] <jaheikki3> If snapshot is good enough we are targeting to release beta 1 on Friday or latest at the beginning of next week
[17:14:13] <jaheikki3> Any comments or questions`?
[17:16:40] <jaheikki3> Ok, it was all at this time. Let's skip next weeks meeting (because of contributor summit) and have new  meeting tue 17th October at this same time
[17:16:49] <jaheikki3> Bye!


From jani.heikkinen at qt.io  Fri Oct  6 11:12:27 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Fri, 6 Oct 2017 09:12:27 +0000
Subject: [Releasing] Qt 5.9.2 and Qt Creator 4.4.1 released
Message-ID: <HE1PR02MB31323688BC6A0B3081314CEC9D710@HE1PR02MB3132.eurprd02.prod.outlook.com>

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







From edward.welbourne at qt.io  Tue Oct 10 19:17:05 2017
From: edward.welbourne at qt.io (Edward Welbourne)
Date: Tue, 10 Oct 2017 17:17:05 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting
 05.09.2017
In-Reply-To: <VI1PR02MB3264F403E3BAAA44AF6515F1876E0@VI1PR02MB3264.eurprd02.prod.outlook.com>
References: <HE1PR02MB3132A5683B71D4E2187E8DDC9D970@HE1PR02MB3132.eurprd02.prod.outlook.com>,
	<VI1PR02MB3264F403E3BAAA44AF6515F1876E0@VI1PR02MB3264.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB326089F724E4DFE8F757D74187750@HE1PR02MB3260.eurprd02.prod.outlook.com>

Back on 13 September 2017 at 10:54 I announced:
> 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

I've just updated these (it's been four weeks).

Back then, I mentioned:

> 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).

The script now groks these changes in #endif comments, too; with any
luck, your new patch sets shall omit some boring #endif changes.

	Eddy.


From jani.heikkinen at qt.io  Wed Oct 18 06:41:44 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 18 Oct 2017 04:41:44 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 17.10.2017
Message-ID: <HE1PR02MB31328ADCBAC4ADAD8F96E0079D4D0@HE1PR02MB3132.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 17th October 2017

Qt 5.10 status:
- Beta 1 released a week ago
- Target to get beta 2 out as soon as possible. Unfortunately we haven't been able to get qt5.git integrated since beta1
   * Remaining issue: QTBUG-63724 QtMultimedia build failed because of 'virtual memory range for PCH exceeded' during qt5.git integration in '5.10'
      ** This is only known blocker for beta2
      ** Fix proposal available (https://codereview.qt-project.org/#/c/208497/)
- Target is to announce soft string freeze during this week and have official string freeze a week after that
- Target start branching from '5.10' -> 5.10.0 quite soon, current estimate at the beginning of November
- API review fixes are in progress; needs to be in before RC
   * RC blocker list here: https://bugreports.qt.io/issues/?filter=18957

Next meeting Tue 31st October 16:00 CET

Br,
Jani

irc log below:
[17:00:06] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping
[17:00:46] <thiago> jaheikki3: pong
[17:01:39] <jaheikki3> Time to start Qt release team meeting
[17:01:48] <jaheikki3> On agenda today:
[17:01:52] <jaheikki3> Qt 5.10 status
[17:02:00] <jaheikki3> Any additional item to the agenda?
[17:03:20] <jaheikki3> Ok, let's browse through the Qt 5.10 status now:
[17:03:33] <jaheikki3> Beta 1 released a week ago
[17:03:48] <jaheikki3> target to get beta 2 out as soon as possible
[17:04:17] <jaheikki3> Unfortunately we haven't been able to get qt5.git integrated since beta1 content
[17:04:46] <jaheikki3> Remaining issue: QTBUG-63724 QtMultimedia build failed because of 'virtual memory range for PCH exceeded' during qt5.git integration in '5.10' 
[17:04:47] <qt_gerrit> jaheikki3: QtMultimedia build failed because of 'virtual memory range for PCH exceeded' during qt5.git integration in '5.10' - https://bugreports.qt.io/browse/QTBUG-63724 (Open)
[17:05:21] <jaheikki3> Fix proposal available (https://codereview.qt-project.org/#/c/208497/). verification ongoing if it is really proper one
[17:05:22] <qt_gerrit> jaheikki3: [qt/qt5/5.10] Provisioning: Adjust Virtual Memory Page File from Heikki Halmet - https://codereview.qt-project.org/208497 (NEW)
[17:05:54] <jaheikki3> And it is only known blocker for beta2
[17:06:49] <jaheikki3> And to be able to release Qt 5.10 final at the end we should start string freeze soon
[17:07:22] <jaheikki3> Target is to announce soft string freeze during this week and have official string freeze a week after that
[17:08:48] <jaheikki3> We should also start branching from '5.10' -> 5.10.0 quite soon, i would say at the beginning of November
[17:08:58] <frkleint> thiago: Has this move of qStartsWIth & etc into a namespace been sorted?
[17:09:14] <thiago> frkleint: no
[17:09:37] <thiago> I've been busy with QRandomGenerator API
[17:09:42] <frkleint> that would be a  a blocker for branching 5.10.0
[17:09:44] <frkleint> ?
[17:10:17] <frkleint> ok, so to speak, API is still in flux
[17:10:23] <frkleint> for various classes
[17:10:32] <thiago> yes
[17:10:40] <thiago> API review fixes are in progress
[17:10:56] <jaheikki3> ok, that should be sorted out quite soon
[17:11:00] <thiago> thanks for reminding of the qstringfunctions.h one
[17:11:05] -*- thiago starts a change so he won't forget
[17:11:07] <frkleint> np ;-) 
[17:11:19] <thiago> qstringalgorithsm.h
[17:11:20] <jaheikki3> thanks thiago and frkleint!
[17:12:06] <jaheikki3> ongoing API review fixes aren't blocking beta n but are blocking RC of course
[17:12:44] <jaheikki3> There is already few issues in RC blocker list as well, see https://bugreports.qt.io/issues/?filter=18957
[17:13:51] <jaheikki3> It was pretty much all about Qt 5.10 status now. Any other comments or questions?
[17:14:36] <frkleint> Will this WEbKit be part of the official release -
[17:14:43] <frkleint> we had some unclarity  here...
[17:14:59] <jaheikki3> frkleint: no, webkit isn't part of release
[17:15:03] <frkleint> ok
[17:16:15] <jaheikki3> Ok, this was all at this time. Let's skip meeting next week & have next one Tue 31 October
[17:16:37] <frkleint> Public holiday in Germany, but I guess it does not matter much
[17:16:50] <frkleint> 500 anniversary of Reformation
[17:16:55] <frkleint> (Martin Luther)
[17:17:57] <jaheikki3> frkleint: ahh, ok.
[17:18:18] <jaheikki3> I think we others can have short status meeting even you are on holiday ;)
[17:19:08] <frkleint> sure
[17:19:19] <jaheikki3> Let's end this meeting now. Thanks for your participation!
[17:19:22] <jaheikki3> bye
[17:19:24] <thiago> bye
[17:19:30] <frkleint> expects to read "5.10 rolling" on the Wednesday after ;-) 
[17:19:31] <frkleint> byhe


From jani.heikkinen at qt.io  Thu Oct 19 11:39:23 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Thu, 19 Oct 2017 09:39:23 +0000
Subject: [Releasing] HEADS UP : Qt 5.10 soft string freeze
Message-ID: <HE1PR02MB3132E37FB78CC258D35399489D420@HE1PR02MB3132.eurprd02.prod.outlook.com>

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






From jani.heikkinen at qt.io  Wed Oct 25 13:37:21 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 25 Oct 2017 11:37:21 +0000
Subject: [Releasing] Qt 5.10 Beta2 available
In-Reply-To: <HE1PR02MB31323A255AC969ED946D766E9D440@HE1PR02MB3132.eurprd02.prod.outlook.com>
References: <HE1PR02MB31323A255AC969ED946D766E9D440@HE1PR02MB3132.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB3132E63EC05DA4C7857918849D440@HE1PR02MB3132.eurprd02.prod.outlook.com>

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




-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt5.10-beta1-delta-beta2-commits
Type: application/octet-stream
Size: 25627 bytes
Desc: qt5.10-beta1-delta-beta2-commits
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20171025/8b5bc71c/attachment.obj>

From jani.heikkinen at qt.io  Fri Oct 27 13:22:11 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Fri, 27 Oct 2017 11:22:11 +0000
Subject: [Releasing] HEADS UP : Qt 5.10 string freeze
In-Reply-To: <HE1PR02MB3132E37FB78CC258D35399489D420@HE1PR02MB3132.eurprd02.prod.outlook.com>
References: <HE1PR02MB3132E37FB78CC258D35399489D420@HE1PR02MB3132.eurprd02.prod.outlook.com>
Message-ID: <HE1PR02MB3132F3B91420CBE17E6F9D489D5A0@HE1PR02MB3132.eurprd02.prod.outlook.com>

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: localization at qt-project.org
Cc: development at qt-project.org; releasing at 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






From jani.heikkinen at qt.io  Tue Oct 31 16:40:51 2017
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Tue, 31 Oct 2017 15:40:51 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 31.10.2017
Message-ID: <HE1PR02MB3132E90837381C5800D7D3159D5E0@HE1PR02MB3132.eurprd02.prod.outlook.com>

Meeting minutes from Qt Release Team meeting 31st October 2017

Qt 5.10 status:
- String freeze in effect 
- Beta 2 released 25.10
- Beta3 will be released during this week
- API review changes still ongoing
   * Not blocking beta3
   * Changes should be done by the end of the week
- Target to get RC out latest 16.11.2017 -> We need to start branching from '5.10' to '5.10.0' during this week
   * Soft branching is used -> branching will be finalized after a week
   * All RC blockers needs to be fixed as soon as possible. Blocker list here: https://bugreports.qt.io/issues/?filter=18957
      ** Make sure all blockers are visible in the blocker list!

Qt 5.9.3 status
- Creating first binary snapshot ongoing
- Couple of issues in blocker list, see https://bugreports.qt.io/issues/?filter=18995
- Branching needs to be started now to get 5.9.3 out early enough and not risk Qt 5.10 schedule
   * Target to start soft branching Wed 1.11
   * Creating change files to be started immediately after branching

Next Meeting Tue 7.11.2017 16:00 CET

br,
Jani

irc log below:
[17:00:54] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping 
[17:01:01] <thiago> jaheikki3: pong
[17:01:05] <akseli> jaheikki3: pong
[17:01:51] <jaheikki3> Time to start qt release team meeting
[17:01:59] <jaheikki3> On agenda today:
[17:02:04] <jaheikki3> Qt 5.10 status
[17:02:09] <jaheikki3> Qt 5.9.3 status
[17:02:21] <jaheikki3> Any additional item to the agenda?
[17:03:35] <jaheikki3> Lets start from 5.10 status
[17:03:46] <jaheikki3> String freeze in effect 
[17:03:59] <jaheikki3> Beta 2 released 25.10
[17:04:13] <thiago> API changes still going
[17:04:32] <thiago> waiting for qt5 5.10 integration to happen so I can merge in the last batch
[17:04:41] <jaheikki3> Yeah, I heard that from lars
[17:04:57] <thiago> should be done by the end of the week
[17:05:09] <jaheikki3> ok
[17:05:40] <lars> thiago: sounds good. I'll help staging once qt5.git is updated
[17:05:49] <jaheikki3> But that doesn't block beta3, which is planned to happen this week
[17:06:43] <thiago> you've already approved all the changes
[17:07:11] <thiago> I do expect that the actual changes to qtbase will need at least one more round of updates, as the CI finds stuff
[17:07:26] <thiago> correct
[17:07:35] <lars> thiago: probably
[17:07:43] <thiago> beta3 will contain the QString/QByteArray API update
[17:07:45] <lars> but I can help get the changes to the other repo's in
[17:10:21] <thiago> I don't expect there to be trouble with most of them
[17:10:38] <lars> yep, neither do I :)
[17:10:46] <jaheikki3> thiago: lars: We should start branching from '5.10' -> '5.10.0' soon to be able to keep the RC schedule (RC target 16.11) . Could we start branching already this week & finalize it next week after API changes are in?
[17:11:35] <jaheikki3> We need ~week for soft barching period so that's why would be good to start it already during this week...
[17:12:02] <thiago> sure, so long as you can still fast-forward qtbase into that
[17:12:14] <thiago> hopefully it won't take long to integrate the changes
[17:12:33] <jaheikki3> great.
[17:13:31] <lars> on CI: fregl and nierob are currently working on fixing it. hopefully up and running again in the next 2-3 hours
[17:15:26] <jaheikki3> hoping so. Let's keep fingers crossed...
[17:15:38] <lars> yep
[17:16:35] <jaheikki3> And for RC: We need to get all RC blockers visible in blocker list & fix those as soon as possible. Blocker list here: https://bugreports.qt.io/issues/?filter=18957
[17:17:18] <jaheikki3> But that's all about 5.10 at the moment. Any comments or questions?
[17:19:11] <jaheikki3> Then Qt 5.9.3 status: 
[17:19:22] <jaheikki3> Creating first binary snapshot ongoing
[17:19:36] <jaheikki3> Couple of issues in blocker list, see https://bugreports.qt.io/issues/?filter=18995
[17:20:09] <jaheikki3> Branching needs to be started now to get 5.9.3 out early enough (not to risk Qt 5.10 schedule)
[17:21:11] <jaheikki3> So let's start soft branching from '5.9' -> '5.9.3' tomorrow
[17:22:02] <jaheikki3> And let's start creating change files for 5.9.3 immediately after branching. As usual we will offer initial ones for maintainers
[17:22:19] <jaheikki3> Any comments?
[17:24:54] <jaheikki3> Ok, it was all at this time
[17:25:28] <jaheikki3> Let's end the meeting now & have new one Tue 7th Nov 16:00 CET 
[17:25:42] <jaheikki3> Thanks for your participation. Bye!
[17:25:51] <lars> jaheikki3: btw, can you remember to ping me for the meetings as well, please?
[17:26:15] <jaheikki3> lars: Sure. I'll add you in my ping list
[17:26:59] <lars> jaheikki3: thanks
[17:27:15] <thiago> thanks