Meeting minutes from Qt Release Team meeting Tue 28th September 2021 Qt 6.2 status: - Qt 6.2.0 RC released 16th September 2021 and RC2 24th September 2021 - Qt 6.2.0 release content frozen and packages under testing * New blocker proposal reported: https://bugreports.qt.io/browse/QTBUG-96916 ** Qt release team agreed this isn't a blocker for Qt 6.2.0 --> We will release existing packages as Qt 6.2.0 Thu 30th September as planned
Next meeting tue 5th October 2021 16:00 CET in libera.chat #qt-releases Br, Jani Heikkinen Release Manager irc log below: [17:00:56] <jaheikki3> akseli: ablasche:carewolf:larsk:thiago:ankokko:mapaaso:frkleint: ping [17:01:02] <larsk> pong [17:01:26] <frkleint> jaheikki3: pong [17:02:03] <jaheikki3> Time to start qt release team meeting [17:02:11] <jaheikki3> On agenda today: [17:02:17] <jaheikki3> Qt 6.2 status [17:02:27] <jaheikki3> Any additional item to the agenda? [17:02:54] <carewolf> pong [17:04:13] <jaheikki3> Ok, let's browse through Qt 6.2.0 status: [17:04:33] <jaheikki3> Qt 6.2.0 RC released 16th September 2021 [17:04:44] <jaheikki3> and RC2 24th September 2021 [17:05:11] <jaheikki3> Qt 6.2.0 release content already frozen and packages created for testing [17:05:36] <jaheikki3> Target is to release Qt 6.2.0 Thu 30th September as planned [17:05:51] <jaheikki3> Unfortunately new blocker proposal reported yesterday: [17:06:00] <jaheikki3> https://bugreports.qt.io/browse/QTBUG-96916 [17:06:40] <jaheikki3> So the question is can we live with it as known issue in Qt 6.2.0 or do we need to delay the release a while to get in fixed in Qt 6.2.0 ? [17:06:40] -*- thiago reads [17:06:59] <thiago> oh, that. I don't think it's a blockers [17:07:13] <larsk> The bug has been there since 6.0, which IMO speaks against it being a blocker for 6.2.0 [17:07:20] <carewolf> right so data compat [17:07:36] <larsk> We should get it fixed for 6.2.1 though IMO [17:08:07] <jaheikki3> That would be welcome [17:08:42] <larsk> But we can list it as a known issue. [17:08:43] <thiago> I don't think there's a fix. I think it's a documentation/porting guide issue [17:08:48] <thiago> and "write better code" case [17:08:52] <thiago> yes [17:09:21] <carewolf> we also have a problem with b2qt for qtwebengine, but since it apparently isn't packaged, I assume it is a non-blocker and we can fix in 6.3.2 [17:09:24] <carewolf> 6.2.1 [17:09:26] <larsk> I think we can fix it for old datastream versions. Certainly for reading, most likely also for writing. [17:09:44] <thiago> it's unfortunate that we needed the typedefs because of the comma in templates [17:10:00] <thiago> -> #qt-labs for the bug technical discussion [17:10:08] <thiago> but I agree it's not a 6.2.0 blocker either way [17:10:18] <larsk> well, for Qt 6 the issue is gone. It's only about backwards compat for QDataStream I believe. [17:10:45] <jaheikki3> carewolf: yeah, let's fix it in Qt 6.2.1 as well. Webengine should be packaged in B2Qt so please add the issue in known issues page as well (https://wiki.qt.io/Qt_6.2.0_Known_Issues) [17:10:48] <larsk> Ok, so let's remove it from the blocker list. P1 for 6.2.1 I'd say. [17:10:56] <jaheikki3> +1 [17:11:36] <jaheikki3> So let's keep the plan and release Qt 6.2.0 with existing content thu 30 Sep as planned [17:12:09] <jaheikki3> larsk: thiago: could you add something about QTBUG-96916 in known issues page as well [17:13:20] <thiago> I think we need it somewhere more permanent than the 6.2.0 Known Issues [17:13:26] <thiago> but will discuss with lars [17:14:10] <jaheikki3> thanks! [17:15:28] <jaheikki3> I think this was all at this time. Let's end this meeting now & have next one Tue 5th October at this same time [17:15:39] <jaheikki3> Thanks for your participation, bye! [17:16:41] <frkleint> bye [17:19:03] <thiago> vye _______________________________________________ Releasing mailing list Releasing@qt-project.org https://lists.qt-project.org/listinfo/releasing