[Development] Meeting minutes from Qt Release Team meeting 19.11.2024

[Jani Heikkinen]

Qt 6.8 status

  *   Qt 6.8.1 preparations are still ongoing
     *   The release content isn’t frozen yet, hoping we can freeze it by the end of this week
        *   Few issues are still open in Qt 6.8.1 release blocker list: https://bugreports.qt.io/issues/?filter=26752
     *   New target for the Qt 6.8.1 is 29th of November
Qt 6.9 status

     *   No public snapshot from dev yet. Previous snapshot was quite badly broken and that’s why it wasn’t published.
        *   Fixes should be in place but the dependency update round is blocked again.
        *   The target is to create new snapshot for testing when full dependency update round in dev succeed. And publish it if it works well enough.
  *   Qt 6.9 platform and module freeze will be in effect this Friday (22nd November)
     *   In practice this means no provisioning or platform configuration changes to the dev before Qt 6.9 Beta1 is released
        *   Fixes for Feature Freeze or Beta1 blockers are of course an exception.

Next meeting Tue 26th of November 2024 16:00 CET
br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:35] <jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso: The-C0mpiler: thiago: vohi[M]: ping
[17:00:41] <vohi[M]> jaheikki3: pong
[17:00:49] <frkleint> jaheikki3: pong
[17:01:45] <jaheikki3> time to start qt release team meeting
[17:01:51] <jaheikki3> On agenda today:
[17:01:56] <jaheikki3> qt 6.8 status
[17:02:03] <jaheikki3> qt 6.9 status
[17:02:09] <thiago> jaheikki3: pong
[17:02:12] <jaheikki3> any additional item to the agenda?
[17:02:47] <carewolf> pong
[17:03:07] <jaheikki3> Let's start from qt 6.8 status
[17:03:20] <jaheikki3> Qt 6.8.1 preparations are still ongoing
[17:03:35] <jaheikki3> Release content isn't frozen yet
[17:03:55] <jaheikki3> hoping we can freeze it by the end of this week
[17:04:21] <jaheikki3> but there is stil few issues still open in Qt 6.8.1 release blocker list so let's see
[17:04:43] <jaheikki3> New target for Qt 6.8.1 is Fri 29th of November
[17:05:04] <jaheikki3> that's all about qt 6.8 status at this time. Any comments or questions?
[17:06:13] <vohi[M]> can you share a link to the release blocker list?
[17:06:24] <frkleint> which is the last public release of 6.8? 6.8.2?
[17:06:36] <frkleint> or 6.8.3?
[17:06:52] <jaheikki3> vohi[M]: Qt 6.8.1 blocker list here: https://bugreports.qt.io/issues/?filter=26752
[17:07:57] <thiago> frkleint: depends on when 6.9 gets released, but likely 6.8.3
[17:08:41] <jaheikki3> frkleint: the target is release Qt 6.8.2 by the end of January 2025 and Qt 6.8.3 ~ mid March 2025 and 6.8.3 is planned to be the last public release from Qt 6.8 series, see https://wiki.qt.io/Qt_6.8_Release
[17:08:57] <frkleint> ok, thx
[17:09:13] <jaheikki3> Ok, then Qt 6.9 status
[17:09:16] <vohi[M]> jaheikki3: thanks; some of those don't seem to be regressions from 6.8.0; unless they are, they shouldn't block the 6.8.1 patch release IMHO.
[17:09:36] <vohi[M]> (but I'm not expecting jaheikki3 to figure that out)
[17:10:34] <thiago> FTBFS needs to be fixed
[17:10:34] <jaheikki3> vohi[M]: yes, that's true. I checked the list earlier today & all of those were regressions but it might be there is some new ones already in the list
[17:11:56] <jaheikki3> now qt 6.9 status
[17:12:17] <jaheikki3> No public snapshot from dev yet
[17:12:56] <jaheikki3> Previous snapshot was quite badly broken and that's why it isn't published. Fixes should be in place but dependency update round is blocked again
[17:13:54] <jaheikki3> The target is to create new snapshot for testing when full dependency update round in dev succeed
[17:14:08] <jaheikki3> and publish it if it works well enough
[17:14:22] <thiago> still pending 3 changes for moc before I can fix qtdeclarative and qtactiveqt
[17:14:48] <thiago> I hadn't compiled the qtdeclarative tests since... well, forever, so I didn't know there was a problem
[17:15:04] <jaheikki3> thiago: ok, good to know
[17:15:21] <jaheikki3> Qt 6.9 platform and module freeze will be in effect this Friday (22nd November)
[17:15:31] <vohi[M]> I'd be very happy if changes to moc would only be staged once all necessary follow-up changes in submodules are approved, so that we don't end up with a long time of limbo.
[17:16:00] <vohi[M]> that of course requires building the whole world a lot, and I'm not asking Thiago to do all of that himself
[17:16:28] <vohi[M]> but maybe some reviewers of these changes are reading this ;)
[17:16:53] <jaheikki3> vohi[M]: Yeah :)
[17:16:53] <thiago> well, the issue is I didn't know there was a breakage
[17:17:19] <thiago> I'd have done things differentlyif I had known that there was this one test that looks into the moc internals
[17:17:24] <thiago> not even tst_moc does that
[17:19:46] <jaheikki3> In practice platform and module freeze means no qt5.git changes to the dev before Qt 6.9 Beta1 release, but most probably we need to take some provisioning related fixes in
[17:20:25] <thiago> I don t think that's a good idea
[17:20:50] <jaheikki3> thiago: which one?
[17:21:40] <vohi[M]> fixing provisioning scripts to address e.g. deployment- or dependency-related issues we might find out about during beta should definitely be allowed
[17:22:51] <thiago> releasing beta without all the moc changes
[17:22:56] <thiago> or a submodule update
[17:24:23] <jaheikki3> ahh, of course we will do submodule updates as often as it is possible. But we don't allow provisioning or platform configuration related changes (if not necessarily needed to fix some blocking issues)
[17:26:35] <jaheikki3> I think it was all about 6.9 status at this time. Is there more comments or questions?
[17:28:28] <jaheikki3> Ok, let's end this meeting now & have new one Tue 26th of November as planned.
[17:28:30] <jaheikki3> Thanks for your participation, bye!
[17:28:39] <carewolf> bye
[17:29:01] <thiago> bye
[17:29:23] <vohi[M]> bye
[17:30:11] <frkleint> bye
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20241120/2c3f61c7/attachment-0001.htm>