[Releasing] Meeting minutes from Qt Release Team meeting 27.08.2024

[Jani Heikkinen]

Qt 6.8 status

  *   Beta4 content is frozen, packages are created and testing is ongoing
     *   The target is to release Qt 6.8.0 Beta4 later this week
  *   Qt 6.8.0 String Freeze is in effect now, see https://lists.qt-project.org/pipermail/localization/2024-August/000606.html
  *   Branching from '6.8' to '6.8.0' is delayed until API reviews are done & needed changes are in '6.8'
     *   https://codereview.qt-project.org/q/(topic:%22qml_api_review_6.8%22+and+status:open)+or+(topic:%22api-change-review-6.8%22+and+status:open)
     *   Qt 6.8 RC target is still 11th of September but this may be delayed because of delays in API reviews and branching
     *   RC blocker list here: https://bugreports.qt.io/issues/?filter=26320

Next meeting Tue 10th of September 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:06] <+jaheikki3> ablasche: akseli: carewolf: frkleint: lars__: mapaaso: The-Compiler: thiago: vohi: ping
[17:00:16] <vohi> jaheikki3: pong
[17:00:27] <akseli> jaheikki3: pong
[17:02:06] <thiago> jaheikki3: pong
[17:02:09] <+jaheikki3> Time to start qt release team meeting
[17:02:15] <+jaheikki3> on agenda today:
[17:02:20] <+jaheikki3> Qt 6.8 status
[17:02:26] <+jaheikki3> Any additional item to the agenda?
[17:03:56] <+jaheikki3> Ok, let's browse through the 6.8 status
[17:04:18] <+jaheikki3> Qt 6.8.0 Beta4 content is frozen
[17:04:27] <+jaheikki3> packages are created and testing ongoing
[17:04:44] <+jaheikki3> The target is to release Qt 6.8.0 Beta4 later this week
[17:05:00] <+jaheikki3> Qt 6.8.0 String Freeze is in effect now, see https://lists.qt-project.org/pipermail/localization/2024-August/000606.html
[17:05:33] <+jaheikki3> Target is to  branch from '6.8' to '6.8.0' this Friday (30th of August)
[17:05:44] <vohi> I'm worried about the amount of changes and discussions we have now wrt Qt Core APIs (and some discussions around design principles), and the amount of work that's still going on in Qt HttpServer.
[17:06:26] <+jaheikki3> vohi: yeah, API review is still ongoing...
[17:07:05] <+jaheikki3> But if we want to keep the release schedule, we need to start branching as planned
[17:07:10] <vohi> Qt GRPC header review also still has a lot of open comments
[17:07:30] <+jaheikki3> true
[17:08:09] <+jaheikki3> vohi: what's your proposal?
[17:08:31] <vohi> well, keeping the release schedule is hopefully not a goal in itself; if we move the timeline by two weeks and don't end up with a ton of changes made after 6.8.0 has been branched off (resulting in double the CI load), then we are better off
[17:10:14] <vohi> perhaps some of the work can be done, and discussions concluded, by sitting down together face to face next week at Qt CS
[17:11:06] <+jaheikki3> perhaps.. And we need to find a way to complete this API/Header review stuff quicker than nowdays
[17:11:06] <vohi> in which case branching off in the week after Qt CS (ie. Sept 13th) might make sense?
[17:11:50] <thiago> that might give us the time to do some of the work at QtCS
[17:12:24] <+jaheikki3> vohi: I wouldn't decide the hard delay for the schedule but would it be good to say ' We will do the branching after API reviews are done & needed changes are in '6.8''
[17:13:09] <vohi> that is practical; branching off 6.8.0 and building a RC while we know that changes are still likely to come in makes little sense at least.
[17:13:17] <+jaheikki3> Agree that
[17:14:15] <vohi> having a deadline and target schedule is important as well, but good to be flexible about it if reality is not working along
[17:15:22] <+jaheikki3> Exactly
[17:15:50] <vohi> and yes to findings ways to speed up header/API review; we have tried several things, but so far, none of them seem to have made a significant difference
[17:16:51] <+jaheikki3> that's something we can discuss again in CS; hoping we can find a way to improve that for the future
[17:18:55] <+jaheikki3> ok, so the branching will be delayed until API reviews are done & needed changes are in '6.8'. In practice this means also RC and final releases are delayed, but it remains to be seen how long.
[17:19:46] <+jaheikki3> RC blocker list here: https://bugreports.qt.io/issues/?filter=26320
[17:20:04] <+jaheikki3> I think it was all at this time. Any comments or questions?
[17:20:26] <vohi> for Qt Core we have to get the reviews done and changes merged; if Qt HttpServer ends up delaying the release, then we can decide to leave it as tech -preview, or document selected APIs as "subject to change"
[17:21:49] <+jaheikki3> Yes, agree
[17:22:50] <+jaheikki3> What's your opinion: Should we have meeting normally next week or skip because of CS?
[17:23:35] <thiago> skip
[17:23:49] <thiago> we'll be seeing each other the next day
[17:24:24] <vohi> I'll be unavailable next Tuesday, so skipping and taking things up face-to-face works for me
[17:24:41] <thiago> at this time next week I'll already be aboard my first flight
[17:25:00] <+jaheikki3> Yeah, let's skip next meeting & have next one Tue 10th of September at this same time
[17:25:20] <vohi> ack
[17:25:21] <+jaheikki3> Thanks for your participation! And see you in CS next week
[17:25:43] <carewolf_work> cya
[17:26:28] <vohi> Bye, see you next week!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20240828/c43d76fb/attachment-0001.htm>