[Releasing] Meeting minutes from Qt Release Team meeting 18.4.2017

[Jani Heikkinen]

Meeting minutes from Qt Release Team meeting 18th April 2017

Qt 5.9 status:
- Target to get beta2 out during this week
   * testing already ongoing
- Soft string freeze this week, official string freeze at the end of next week
- Header diff needs to be started now to be able to execute it & fix possible findings early enough
- Branching from '5.9' to '5.9.0' at the beginning of may -> Soft branching starts already next week

Qt 5.10 initial schedule:
- Qt 5.10 Feature Freeze: 8.8.2017
- Qt 5.10 Alpha Release: 31.8.2017
- First Qt 5.10 Beta Release 5.10.2017
- Qt 5.10 RC 16.11.2017
- Qt 5.10 final release 30.11.2017

Initial schedule for coming patch level releases:
- Branch '5.6.3' from '5.6' at the end of May/beginning of June, 5.6.3 release target August 2017
- Branch '5.9.1' from '5.9' at the end of July/beginning of August, 5.9.1 release target September 2017
- Branch '5.9.2' from '5.9' Nov 2017
- Branch '5.6.4' from '5.6' Jan 2018

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:02] <jaheikki3> akseli: iieklund: thiago: fkleint: ZapB: tronical:vladimirM: aholza: peter-h: mapaaso: ankokko: fkleint: carewolf: fregl:ablasche:ping
[17:00:24] <akseli> jaheikki3: pong
[17:01:51] <jaheikki3> time to start qt release team meeting
[17:02:01] <jaheikki3> on agenda today:
[17:02:08] <fkleint> jaheikki3L: pong
[17:02:15] <jaheikki3> Qt 5.9 status
[17:02:29] <jaheikki3> Qt 5.10, 5.9.1 & 5.6.3 schedule proposal
[17:02:41] <jaheikki3> Any additional item to the agenda?
[17:04:20] <jaheikki3> let's start from 5.9 status
[17:04:46] <jaheikki3> we are targeting to have beta2 release during this week
[17:05:50] <jaheikki3> content is under smoke testing atm & if all ok we will put it visible & announce Qt 5.9 beta2 release later this week
[17:06:51] <jaheikki3> Soft string freeze will be at the end of this week, official string freeze at the end of next one
[17:07:33] <jaheikki3> And we need to start header review now to be able to execute it & fix possible issues early enough
[17:08:38] <jaheikki3> We should also branch '5.9.0' from '5.9' at the beginning of may to be able to keep the original schedule (see https://wiki.qt.io/Qt_5.9_Release)
[17:09:05] <jaheikki3> So soft branching needs to be started already next week
[17:09:58] <jaheikki3> Any comments or questions?
[17:12:37] <jaheikki3> Ok, it was all about 5.9 at this time. Then schedules of next releases after Qt 5.9
[17:13:49] <jaheikki3> I have sent proposals for coming 5.10, 5.6.x and 5.9.x release schedules last week, see http://lists.qt-project.org/pipermail/development/2017-April/029434.html & http://lists.qt-project.org/pipermail/development/2017-April/029489.html 
[17:16:14] <jaheikki3> there weren't that much comments (yet), one related 5.8.1 and another one if we could do 5.6.3 already during h1/2017
[17:17:14] <jaheikki3> 5.8.1 won't happen as decided earlier
[17:18:36] <jaheikki3> And we need to secure Qt 5.9 plan and so on we cannot start preparations for Qt 5.6.3 early enough to be able to release it still during h1/2017 
[17:19:16] <fkleint> hm
[17:20:11] <jaheikki3> Unfortunately proposed plan seems to be the best we can do. And it will be tight to get all that out in time
[17:21:18] <jaheikki3> Of course we can update the plan later if it seems we can do something earlier or if we need to delay something,
[17:21:49] <jaheikki3> Any comments or questions?
[17:24:22] <akseli> +1 .. and otherwise silence equals approval as usual ;)
[17:24:35] <jaheikki3> yeah, thanks!
[17:24:52] <fkleint> ;-) 
[17:25:07] <jaheikki3> I think this was all at this time so let's end the meeting now & have new one next week as planned
[17:25:18] <jaheikki3> thanks for your participation, bye!
[17:25:36] <akseli> bye
[17:25:38] <fkleint> bye