[Development] Meeting minutes from Qt Release Team meeting 17.09.2024

[Jani Heikkinen]

Qt 6.7 status

  *   All known Qt 6.7.3 release blockers fixed
  *   The target is to have release packages for testing Wed 18th September
  *   The target is to release Qt 6.7.3 as soon as possible, hoping already Friday 20th of September

Qt 6.8 status

  *   Qt 6.8 RC preparations are ongoing
     *   Branching from '6.8' to '6.8.0' is done
     *   Qt 6.8 RC content not frozen yet; unfortunately there are couple of blockers still open in the blocker list https://bugreports.qt.io/issues/?filter=26320
     *   The target is to freeze Qt 6.8.0 RC content immediately after all blockers are fixed
     *   Hoping we can get RC out at the beginning of next week

Next meeting Tue 24th of September 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:51] <+jaheikki3> akseli: alblasch: carewolf: frkleint: lars__: mapaaso_: The-Compiler: thiago: vohi: ping
[17:01:05] <akseli> jaheikki3: pong
[17:01:10] <vohi> jaheikki3: pong
[17:02:39] <+jaheikki3> Time to start qt release team meeting
[17:02:44] <+jaheikki3> on agenda today:
[17:02:48] <+jaheikki3> Qt 6.7 status
[17:02:53] <+jaheikki3> Qt 6.8 status
[17:03:03] <+jaheikki3> Any additional item to the agenda?
[17:04:10] <carewolf> pong
[17:05:01] <+jaheikki3> Ok, let's start from 6.7 status
[17:05:43] <+jaheikki3> All known Qt 6.7.3 blockers should have a fix in place & integration ongoing.
[17:05:52] <+jaheikki3> Dependency update round also ongoing
[17:06:01] <+jaheikki3> The target is to have release packages tomorrow morning
[17:06:18] <+jaheikki3> and the target is to release Qt 6.7.3 as soon as possible, hoping already Friday 20th of September
[17:07:36] <+jaheikki3> But that remains to be seen, Qt 6.7.3 will have lower prio than Qt 6.8 RC and so on we will put the effort to release Qt 6.8.0 RC when packages available
[17:08:05] <+jaheikki3> that's actually all about Qt 6.7 status, any comments or questions?
[17:10:01] <+jaheikki3> ok, next Qt 6.8 status
[17:10:16] <+jaheikki3> Qt 6.8 RC preparations are ongoing
[17:10:28] <+jaheikki3> Branching from '6.8' to '6.8.0' is done
[17:10:45] <+jaheikki3> Qt 6.8 RC content not frozen yet; unfortunately there is couple of blockers still open in the blocker list https://bugreports.qt.io/issues/?filter=26320
[17:11:07] <+jaheikki3> The target is to freeze Qt 6.8.0 RC content immediately after all blockers are fixed
[17:11:19] <+jaheikki3> Hoping we can get RC out at the beginning of next week
[17:11:48] <+jaheikki3> that's actually all about Qt 6.8 status at this time. Any comments or questions?
[17:12:57] <vohi> both 6.8 blockers are in progress with change in review, but the change addressing the issue in Qt3D doesn't have any pick-to targets...
[17:14:44] <vohi> i.e. https://codereview.qt-project.org/c/qt/qtquick3d-assimp/+/591420; but that's our assimp fork, so perhaps the submodule bump in https://codereview.qt-project.org/c/qt/qt3d/+/591462 takes care of that?
[17:14:52] <vohi> will comment on the changes
[17:14:57] <+jaheikki3> vohi: Actually that assimp one doesn't need to be picked anywhere; both qt3d and qtquick3d are using that same repo and branch as a submodule
[17:15:20] <+jaheikki3> e.g https://codereview.qt-project.org/c/qt/qt3d/+/591490 updates the submodule
[17:15:28] <+jaheikki3> so all is OK related to that
[17:15:46] <vohi> yep; ok, then that one is closed, cherry-pick into dev is still pending but 6.8.0 is merged
[17:16:08] <+jaheikki3> yeah
[17:16:36] <+jaheikki3> It was all at this time so let's end this meeting now & have new one Tue 24th September at this same time
[17:16:50] <+jaheikki3> thanks for your participation, bye!
[17:16:51] <vohi> ok, thanks!
[17:16:55] <carewolf> bye

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20240918/bd0c39bb/attachment-0001.htm>