[Development] Meeting minutes from Qt Release Team meeting 28.05.2024

[Jani Heikkinen]

Qt 6.8 status

  *   Platform and Module Freeze in effect
  *   Qt 6.8 feature freeze will be in effect Friday 31st of May
     *   As usual it is allowed to stage ready changes (approved latest on Friday 31st) during the weekend
  *   The target is to start branching from ‘dev’ to ‘6.8’ on Monday 3rd of June
  *   The target is to start Qt 6.8 API change review immediately after branching
  *   the target is to release Qt 6.8 Beta1 from first successful dependency update round in ‘6.8
     *   Beta1 estimation is 13th of June but hoping we can get it out earlier

Qt 6.8 FF Exception requests:

  *   SBOM (Software Bill of Materials) generation
     *   Exception granted but needs to be in by the beta2
  *   building FFmpeg as shared libraries
     *   Exception granted but needs to be in by the beta2
  *   add PDF/X-4 support (for color-managed PDFs)
     *   Exception granted but needs to be in by the beta2

Next meeting Tue 4th of June 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:13] <+jaheikki3> alblasch: akseli: carewolf: frkleint: lars__:mapaaso: The-Compiler: thiago: vohi: ping
[17:00:21] <vohi> jaheikki3: pong
[17:00:33] <frkleint> jaheikki3: pong
[17:01:16] <frkleint> mgmt is at a leadership workshop today
[17:02:00] <+jaheikki3> time to start qt release team meeting
[17:02:05] <+jaheikki3> on agenda today:
[17:02:10] <+jaheikki3> Qt 6.8 status
[17:02:17] <thiago> jaheikki3: pong
[17:02:40] <carewolf> pong
[17:02:43] <+jaheikki3> Qt 6.8 FF exceptions
[17:02:53] <+jaheikki3> Any other issues in the agenda?
[17:04:10] <+jaheikki3> Let's start from Qt 6.8 status:
[17:04:35] <+jaheikki3> Qt 6.8 Platform and Module Freeze is in effect
[17:04:49] <+jaheikki3> Qt 6.8 feature freeze will be in effect Friday 31st of May
[17:05:17] <+jaheikki3> As usual it is allowed to stage ready changes (approved latest on Friday 31st) during the weekend
[17:05:28] <+jaheikki3> The target is to start branching from ‘dev’ to ‘6.8’ on Monday 3rd of June
[17:05:43] <+jaheikki3> The target is also to start Qt 6.8 API change review immediately after branching
[17:06:20] <+jaheikki3> And the target is to release Qt 6.8 Beta1 from first successful dependency update round in ‘6.8
[17:06:52] <+jaheikki3> Beta1 estimation is 13th of June but hoping we can get it out earlier
[17:07:15] <+jaheikki3> that's all about Qt 6.8 status at this time. Any comments or questions?
[17:07:30] <vohi> somewhat meta to the exception requests regarding platform & module freeze: we need to clarify what exactly defines "module" in the context of "module freeze" milestone. We had/have a few new libraries, which are modules in the "cmake build system" context and might have a separate documentation page, but are really just a technicality
[17:08:16] <vohi> e.g. we are splitting the widget-classes in Qt Graphs out of the existing libraries now into a separate library, based on ongoing API reviews; is that a new module?
[17:09:28] <+jaheikki3> vohi: I think the intention for the module freeze milestone is to get new submodules in CI
[17:10:15] <+jaheikki3> to have some time for packaging to add those new modules packages before beta1 release
[17:11:34] <+jaheikki3> So new modules in existing submodules aren't part of module freeze
[17:11:48] <vohi> that makes sense, thanks
[17:13:17] <+jaheikki3> Then Qt 6.8 FF exceptions: There is already 3 of those sent in development ML:
[17:13:35] <+jaheikki3> - building FFmpeg as shared libraries
[17:13:49] <+jaheikki3> - SBOM (Software Bill of Materials) generation
[17:14:04] <+jaheikki3> - add PDF/X-4 support (for color-managed PDFs)
[17:14:13] <thiago_> I don't think SBOM is a feature per se
[17:14:20] <thiago_> but fair, it's excepted
[17:15:15] <carewolf> in webengine we also have a conflict between feature merging and a chromium update, we are trying to resolve the conflict and still hope to make it before FF, but might need and exception if it fails
[17:15:21] <vohi> agree that it's not a feature request per se, and also think the risk of adding this to 6.8 after branching is very low; plus it's something we need to have to be EU cyber resiliency act compliant with 6.8, which we need to be as an LTS
[17:16:36] <vohi> FFmpeg: we also need to get this done, and even cherry-pick this back into stable branches as it's currently very hard for users to deploy the FFmpeg Multimedia plugin due to static linking of an LPGL'ed 3rd party library
[17:19:27] <+jaheikki3> For me it is OK to give an exception for both of those. What about Peppe's 'add PDF/X-4 support (for color-managed PDFs)'? I don't have strong opinions to that one either.
[17:20:16] <vohi> PDF/X-4 support seems to have minimal impact on public headers and it's a leaf module, plus partially merged, so I think it's ok to give this an exception as well, as long as it gets merged by Beta 2
[17:21:37] <thiago_> on qtwebengine, since it's on-going and started work, I think it's safe to say you have the ability to finish after FF if you fail before
[17:22:48] <+jaheikki3> Ok for me. So we grant ff exeptions for all those 3 but those needs to be in by the beta2
[17:24:05] <+jaheikki3> any objections or some other comments or questions?
[17:24:45] <+jaheikki3> And we will check new exception requests (e.g. that possible we one) in next meeting
[17:24:53] <vohi> 👍
[17:25:12] <carewolf> sounds good
[17:25:39] <+jaheikki3> great! It was all at this time so let's end this meeting now & have new one tie 4th of June at this same time
[17:25:47] <+jaheikki3> thanks for your participation, bye!

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