Meeting minutes from Qt Release Team meeting Tue 21st May 2019 Qt 5.13.0 status: - We should have beta4 content in place finally * qt5.git integration is ongoing. Package creation will start immediately when qt5.git integration succeed * There were warning about some compilation issue in device creation side against that new content. But I haven't got any bug report yet so hoping that was false alarm - Target is to get beta4 out during this week - Few changes file still missing '+2', see https://codereview.qt-project.org/q/message:%2522Add+changes+file+for+Qt+5.13.0%2522+status:open - 3 issues still open in blocker list, see https://bugreports.qt.io/issues/?filter=20625 * openSSL issues only without a fix. And finally we should be close to get the update done. - Target is to put beta5 out immediately after openSSL update.
Qt 5.12.4: - Branching from '5.12' to '5.12.4' should start today ** Final downmerge will happen Monday 27th May - Initial changes files for Qt 5.12.4 will be created immediately when branching is started - Target is to create first binary snapshot for testing still during this week - Release target is 11.6.2019 * Release blocker list here: https://bugreports.qt.io/issues/?filter=21022 Next meeting Tue 28th May 2019 16:00 CET br, Jani Heikkinen Release Manager irc log below: [17:02:12] <jaheikki3_> akseli: iieklund: thiago: lars: frkleint: vladimir-m: ankokko: mapaaso:carewolf: fregl: ablasche: ping [17:02:16] <ankokko_> jaheikki3_: pong [17:02:41] <akseli1> jaheikki3_: pong [17:03:28] <jaheikki3_> time to start qt release team meeting [17:03:32] <jaheikki3_> On agenda today: [17:03:39] <jaheikki3_> Qt 5.13.0 status [17:03:47] <jaheikki3_> Qt 5.12.4 status [17:03:56] <jaheikki3_> Any additional item to the agenda? [17:04:03] <frkleint> jaheikki3_: pong [17:05:29] <jaheikki3_> Ok, let's start from 5.13.0 status [17:05:43] <jaheikki3_> We should have beta4 content in place finally [17:05:53] <jaheikki3_> qt5.git integration is ongoing [17:05:59] <jaheikki3_> package creation will start immediately when qt5.git integration succeed [17:07:06] <jaheikki3_> There were some warning from mikkog about some compilation issue in device creation side againts that new content. But I haven't got any bug report yet so hoping that was false alarm [17:08:21] <jaheikki3_> So if that was false alarm and all is now ok with that content we will release it as beta4 during this week [17:08:38] <jaheikki3_> Few changes file still missing '+2', see https://codereview.qt-project.org/q/message:%2522Add+changes+file+for+Qt+5.13.0%2522+status:open [17:08:52] <jaheikki3_> and 3 issues still open in blocker list, see https://bugreports.qt.io/issues/?filter=20625 [17:08:55] <The-Compiler> maybe https://wiki.qt.io/Qt_5.13_Release should be updated with new dates for Beta4/RC/final? [17:09:42] <jaheikki3_> The-Compiler: yes, true. I'll do the update. I'll update rc & final dates after beta4 is out [17:10:18] <jaheikki3_> Related to those open issues: There is still that openSSL update under work [17:10:43] <jaheikki3_> According to hehalmet we should be finally close to get that done [17:12:38] <jaheikki3_> But if there is still some new issues can we do the .0 release without doing openSSL update everywhere? according to comments in QTBUG-71391 we have to do it for Android but can we do the update for desktop targest later? [17:12:38] <qt_gerrit> jaheikki3_: Android: Use OpenSSL 1.1 for Android SDK - https://bugreports.qt.io/browse/QTBUG-71391 (Open) [17:12:57] <jaheikki3_> Any opinions? [17:13:25] <frkleint> jaheikki3_: Off the top of my head I would say this is a security issue [17:13:42] <frkleint> jaheikki3_: So, we should have up to date OpenSSL everywhere [17:13:54] <jaheikki3_> lars: Do you have any opinion? [17:13:58] <The-Compiler> what frkleint says, and I also think a mayor OpenSSL version bump in a dot release might be a bit weird? [17:14:16] <lars> jaheikki3_: sorry, was distracted, let me read up... [17:15:24] <jaheikki3_> The-Compiler: well yes and no :D We will do that update for 5.12 series as well [17:15:55] <lars> jaheikki3_: I'd very much prefer if we did the bump with 5.13.0 on all platforms. [17:17:15] <jaheikki3_> yeah, I prefer that as well. Just wondering that if there is still issues are we ready to delay the release more... [17:19:51] <jaheikki3_> Ok, it seems we have to do the update in .0 Let's hope there isn't new suprises anymore there [17:20:43] <jaheikki3_> So the plan forward will be [17:20:54] <jaheikki3_> 1. We will release beta4 with content we are integrating in qt5.git now (if all is ok) [17:21:37] <jaheikki3_> 2. We will release beta5 immediately after openSSL update is done. Hoping that will happen during next week already [17:23:00] <ankokko_> sounds good to me [17:23:34] <jaheikki3_> That was all about 5.13.0 status at this time. Any other comments or questions? [17:25:03] <jaheikki3_> Ok, then quick status update for Qt 5.12.4: [17:25:57] <jaheikki3_> Branching from '5.12' to '5.12.4' should start today [17:26:13] <jaheikki3_> And final downmerge will happen Monday 27th May [17:26:26] <jaheikki3_> Initial changes files for Qt 5.12.4 will be created immediately when branching is started [17:26:36] <jaheikki3_> Target is to create first binary snapshot for testing still during this week [17:26:57] <jaheikki3_> Release target is 11.6.2019, blocker list here: https://bugreports.qt.io/issues/?filter=21022 [17:27:24] <jaheikki3_> That's pretty much all about 5.12.4 status at this time. Any comments or questions? [17:30:37] <frkleint> not from my side... [17:30:49] <jaheikki3_> ok, it was all at this time. Let's end this meeting now & have new one tue 28th May as planned [17:31:00] <ankokko_> bye [17:31:02] <jaheikki3_> Thanks for your participation, bye _______________________________________________ Releasing mailing list Releasing@qt-project.org https://lists.qt-project.org/listinfo/releasing
