From jani.heikkinen at qt.io  Wed Jan  8 07:26:33 2025
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 8 Jan 2025 06:26:33 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 07.01.2025
Message-ID: <DB4PR02MB9311B73ED0EE5BA986A600569D122@DB4PR02MB9311.eurprd02.prod.outlook.com>

Qt 6.8 status

  *   Qt 6.8.2 preparations to be started
     *   We will branch from '6.8' to '6.8.2' at the beginning of next week
     *   The target is to freeze the release content by the end of next week
     *   The target is to release Qt 6.8.2 23rd of January 2025


Qt 6.9 status

  *   Qt 6.9 Beta2 preparations are ongoing
     *   The target is to freeze the Beta2 content quite a soon; from the next successful dependency update round
     *   The target is to release Qt 6.9 Beta2 14th of January 2025
  *   Qt 6.9 API change review ongoing, see https://bugreports.qt.io/browse/QTBUG-132090
     *   The target is to add missing QML API reviews asap

Next meeting Tue 14th of January 2025 16:00 CET
br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:46] <jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso_: The-Compiler: thiago: vohi[M]: ping
[17:01:25] <frkleint> jaheikki3: pong
[17:01:58] <vohi[M]> jaheikki3: pong
[17:02:12] <akseli> jaheikki3: pong
[17:02:28] <jaheikki3> time to start qt release team meeting
[17:02:34] <jaheikki3> on agenda today:
[17:02:38] <jaheikki3> Qt 6.8 status
[17:02:49] <jaheikki3> Qt 6.9 status
[17:03:01] <jaheikki3> Any additional item to the agenda?
[17:04:36] <jaheikki3> Let's start from Qt 6.8 status
[17:04:58] <jaheikki3> Qt 6.8.2 preparations will be started soon
[17:05:11] <jaheikki3> The target is to release Qt 6.8.2 23rd of January 2025
[17:05:26] <jaheikki3> so we should start branching from '6.8' to '6.8.2' at the beginning of next week
[17:05:44] <jaheikki3> and freeze the release content by the end of next week
[17:06:16] <thiago> (got disconnected)
[17:06:21] <thiago> jaheikki3: pong
[17:06:30] <carewolf> pong too
[17:06:41] <jaheikki3> that's all about Qt 6.8 status at this time, any comments or questions?
[17:07:55] <jaheikki3> then Qt 6.9 status
[17:08:14] <jaheikki3> Qt 6.9 Beta2 preparations are started
[17:08:28] <jaheikki3> The target is to release Qt 6.9 Beta2 14th of January 2025
[17:08:57] <jaheikki3> so we need to freeze the Beta2 content soon
[17:09:18] <jaheikki3> Most probably next successful dependency update round will be the beta2
[17:09:37] <vohi[M]> haven't caught up with the feature freeze exceptions yet, we wanted those to be completed by beta2 (which implies unfinished stuff needs to be taken out of 6.9).
[17:10:19] <carewolf> we are working on integrating the chromium update, but was a bit delayed by holidays, should be done by next week
[17:10:38] <thiago> the threading fixes are in, past 6.9 integration
[17:10:46] <thiago> I need to fix the conflicts for 6.8.2
[17:10:58] <thiago> will do that today
[17:11:18] <vohi[M]> the changes we discussed for feature freeze exceptions to ApplicationWindow (https://codereview.qt-project.org/c/qt/qtdeclarative/+/605277) and ContextMenu (https://codereview.qt-project.org/c/qt/qtdeclarative/+/554020) are in; the testlib exports are not yet merged (https://codereview.qt-project.org/c/qt/qtbase/+/610419)
[17:11:44] <jaheikki3> Yeah, was just checking the same
[17:12:41] <vohi[M]> so looks like we are almost all good; and the testlib stuff in https://codereview.qt-project.org/c/qt/qtbase/+/610419 is not public API anyway
[17:12:50] <vohi[M]> (stll also after exporting the symbols)
[17:12:54] <vohi[M]> s/stll/still/
[17:13:01] <vohi[M]> * (still \intenral also after exporting the symbols)
[17:13:25] <jaheikki3> Great
[17:14:52] <jaheikki3> QT 6.9 API review is ongoing, see https://bugreports.qt.io/browse/QTBUG-132090
[17:15:44] <jaheikki3> That's all about 6.9 status at this time, any comments or questions?
[17:16:41] <vohi[M]> any ETA on completing the QML API review for all modules with QML elements?
[17:16:44] <carewolf> I honestly believe there should be a qml api review for qquickwebengine https://codereview.qt-project.org/q/topic:%22qml_api_review_6.9%22 at least with three new settings.
[17:16:47] <vohi[M]> e.g. Multimedia has QML APIs but no review
[17:17:21] <jaheikki3> vohi[M]: script is running, let's hope final problems with it is finally solved :D
[17:18:13] <jaheikki3> I am really hoping to publish updates tomorrow. Both updates to existing ones and also missing ones
[17:19:02] <jaheikki3> Ok, let's then end this meeting now & have new one Tue 14th at this same time.
[17:19:12] <jaheikki3> Thanks for your participation, bye!
[17:19:18] <vohi[M]> okidoke, thanks. bye!
[17:19:22] <thiago> bye
[17:19:23] <frkleint> bye
[17:20:04] <carewolf> bye
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20250108/b7e590eb/attachment-0001.htm>

From jani.heikkinen at qt.io  Wed Jan 15 08:11:38 2025
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 15 Jan 2025 07:11:38 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 14.01.2025
Message-ID: <AS8PR02MB93134F01FAE3932DBD984F399D192@AS8PR02MB9313.eurprd02.prod.outlook.com>

Qt 6.8 status

  *   Qt 6.8.2 preparations aren?t started yet; there has been dependency update issues in qtdeclarative#6.8
     *   The target is to start branching from ?6.8? to ?6.8.2? immediately after successful dependency update round in ?6.8?
     *   The target is to freeze the release content as soon as possible, somewhere during next week
     *   The target is to release Qt 6.8.2 by the end of January 2025


Qt 6.9 status

  *   Qt 6.9 Beta2 preparations are still ongoing
     *   The target is to freeze the Beta2 content as soon as possible; from the next successful dependency update round.
     *   The target is to release Qt 6.9 Beta2 as soon as possible
        *   most probably it will happen at the beginning of next week
  *   Qt 6.9 API change review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-132090

Next meeting Tue 21th of January 2025 16:00 CET
br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:55] <jaheikki3> alblasch: akseli: carewolf: frkleint: lars_: mapaaso_: The-Compiler: thiago: vohi[M]: ping
[17:01:38] <vohi[M]> jaheikki3: pong
[17:01:47] <frkleint> jaheikki3: pong
[17:03:22] <jaheikki3> time to start qt release team meeting
[17:03:26] <jaheikki3> On agenda today
[17:03:32] <jaheikki3> Qt 6.8 status
[17:03:35] <jaheikki3> Qt 6.9 status
[17:03:44] <jaheikki3> Any additional item to the agenda?
[17:06:00] <jaheikki3> Ok, let's start from Qt 6.8 status
[17:06:23] <jaheikki3> Actually the status is pretty much the same as in previous meeting:
[17:06:58] <jaheikki3> Qt 6.8.2 preparations not started yet. there has been dependency update issues in qtdeclarative#6.8, which has prevented us to start Qt 6.8.2 preparations
[17:07:14] <jaheikki3> Fixes should be now in and new try is ongoing
[17:07:26] <jaheikki3> The target is to start branching from ?6.8? to ?6.8.2? immediately after successful dependency update round in ?6.8?
[17:07:38] <jaheikki3> And the target is to freeze the release content as soon as possible, somewhere during next week
[17:07:47] <jaheikki3> And the target is to release Qt 6.8.2 by the end of January 2025
[17:08:18] <jaheikki3> that's all about Qt 6.8 status at this time. Any comments or questions?
[17:08:48] <thiago> jaheikki3: pong
[17:08:50] <thiago> sorry
[17:09:22] <jaheikki3> ?
[17:09:30] <jaheikki3> Then Qt 6.9 status
[17:09:38] <thiago> the QThread fixes are now in the 6.8 branch, so we're good in that direction
[17:10:05] <jaheikki3> Yeah, I restarted dependency update round there as well; hoping that succeed now
[17:10:25] <jaheikki3> Qt 6.9 status
[17:11:05] <jaheikki3> It is also pretty much the same than in previous meeting because of those dependency update round problems
[17:11:24] <thiago> also on QThread, which is fixed there too
[17:11:25] <jaheikki3> New round is ongoing in '6.9'
[17:11:42] <thiago> I think we fixed the qqmldebugjsserver issue once and for all, though
[17:12:04] <jaheikki3> yes, I think so.
[17:12:25] <thiago> reminds me to submit a patch to re-enable it on Intel Macs
[17:12:44] <jaheikki3> The target is to freeze the Beta2 content asap; from the next successful dependency update round
[17:13:06] <jaheikki3> And the target is to release Qt 6.9 Beta2 as soon as possible.
[17:13:11] <jaheikki3> most probably it will happen at the beginning of next week
[17:13:26] <jaheikki3> Qt 6.9 API change review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-132090
[17:13:43] <jaheikki3> I have updated the reviews yesterday
[17:14:32] <jaheikki3> and added missing QML ones, at least most of those. carewolf: Script didn't produce anything for WE still :(
[17:14:51] <jaheikki3> But I notice it might be because of too old nodejs
[17:15:04] <jaheikki3> I updated that and new try is ongoing
[17:15:25] <carewolf_home> jaheikki3: We managed to review without it, but we need to have the scripts fixed for next round and not just wait for them to break again
[17:15:41] <jaheikki3> yes, true. We are working on it
[17:16:17] <jaheikki3> that's all about QT 6.9 status at this time. Any comments or questions?
[17:18:19] <jaheikki3> Ok, lets end this meeting now and have new one tue 21st January at this same time
[17:18:28] <jaheikki3> thanks for your participation, bye!
[17:18:36] <frkleint> bye
[17:18:42] <carewolf_home> bye
[17:18:54] <vohi[M]> bye!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20250115/ecb6f316/attachment-0001.htm>

From jani.heikkinen at qt.io  Wed Jan 22 08:10:57 2025
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 22 Jan 2025 07:10:57 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 21.01.2025
Message-ID: <DB4PR02MB93112B9C8A4A50C733F7284D9DE12@DB4PR02MB9311.eurprd02.prod.outlook.com>

Qt 6.8 status

  *   Qt 6.8.2 preparations are ongoing
     *   Branching from '6.8' to '6.8.2' done
     *   The target is to freeze the release content by the end of this week
     *   The target is to release Qt 6.8.2 by the end of January 2025


Qt 6.9 status

  *   Qt 6.9 Beta2 packages already available, but official announcements will be sent later
  *   Updating 3rd party components for Qt 6.9.0 started, see https://bugreports.qt.io/browse/QTBUG-132849
  *   Qt 6.9 API change review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-132090

Next meeting Tue 28th of January 2025 16:00 CET
br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:19] <jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso_: The-Compiler: thiago: vohi[M]: ping
[17:00:36] <vohi[M]> jaheikki3: pong
[17:00:40] <carewolf> pong
[17:01:07] <thiago> jaheikki3: pong
[17:01:19] <jaheikki3> time to start qt release team meeting
[17:01:25] <jaheikki3> on agenda today:
[17:01:32] <jaheikki3> Qt 6.8 status
[17:01:36] <jaheikki3> Qt 6.9 status
[17:01:45] <jaheikki3> any additional item to the agenda?
[17:02:47] <jaheikki3> Let's start from Qt 6.8 status
[17:03:07] <jaheikki3> Qt 6.8.2 preparations are finally ongoing
[17:03:32] <jaheikki3> Branching from '6.8' to '6.8.2' is done and first snapshot is created. Testing is ongoing
[17:04:00] <jaheikki3> Release content will be frozen by the end of this week
[17:04:19] <jaheikki3> And the target is to release Qt 6.8.2 by the end of next week
[17:05:02] <jaheikki3> that's all about 6.8 status at this time. Any comments or questions?
[17:05:16] <thiago> jaheikki3: pong
[17:05:23] <thiago> I think we're fine for 6.8
[17:05:34] <thiago> (numlock wasn't pressed, so that pressed up for 8)
[17:06:16] <jaheikki3> great
[17:06:21] <jaheikki3> then Qt 6.9 status
[17:07:02] <jaheikki3> Qt 6.9 Beta2 almost released. It is already available from the production and final testing is ongoing
[17:07:32] <jaheikki3> Official announcements will be sent tomorrow, after all production tests are done
[17:07:50] <jaheikki3> Updating 3rd party components for Qt 6.9.0 started, see https://bugreports.qt.io/browse/QTBUG-132849
[17:08:01] <jaheikki3> and API change review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-132090
[17:09:12] <jaheikki3> Let's try to get remaining reviews completed by the Beta3, which is planned to be released ~ 3 weeks
[17:09:40] <jaheikki3> that's all about Qt 6.9 status. Any comments or questions?
[17:11:48] <jaheikki3> it was all at this time so let's end this meeting now & have new one Tue 28th January at this same time
[17:11:59] <jaheikki3> thanks for your participation, bye!
[17:12:12] <vohi[M]> Bye
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20250122/ac3966b0/attachment-0001.htm>

From jani.heikkinen at qt.io  Wed Jan 29 11:11:28 2025
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 29 Jan 2025 10:11:28 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 28.01.2025
Message-ID: <DB4PR02MB93118B20B80C30099C8C76509DEE2@DB4PR02MB9311.eurprd02.prod.outlook.com>

Qt 6.8 status

  *   Qt 6.8.2 release content is frozen and release packages are created
     *   Package testing is ongoing
  *   We will release Qt 6.8.2 later this week, if no new blockers found during the package testing
  *   The target is to release Qt 6.8.3 ~mid March, before Qt 6.9.0 release
     *   Qt 6.8.3 will be the last release before the branch enters LTS mode

Qt 6.9 status

  *   Qt 6.9 Beta2 is released
  *   Updating 3rd party components for Qt 6.9.0 proceeding well, see https://bugreports.qt.io/browse/QTBUG-132849
  *   Qt 6.9 API change review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-132090
  *   The target is to release Qt 6.9.0 Beta3 ~mid February and Qt 6.9.0 RC at the end of February



Next meeting Tue 4th of February 2025 16:00 CET
br,
Jani Heikkinen
Release Manager

irc log below:
[17:01:03] <jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso_: The-Compiler: thiago: vohi[M]: ping
[17:01:19] <vohi[M]> jaheikki3: pong
[17:01:41] <frkleint> jaheikki3: pong
[17:02:44] <jaheikki3> time to start qt release team meeting
[17:02:50] <jaheikki3> on agenda today:
[17:02:55] <jaheikki3> Qt 6.8 status
[17:02:58] <jaheikki3> Qt 6.9 status
[17:03:09] <jaheikki3> Any additional item to the agenda?
[17:04:30] <jaheikki3> Let's start from Qt 6.8 status
[17:04:43] <jaheikki3> Qt 6.8.2 release content is frozen
[17:05:00] <jaheikki3> release packages are created
[17:05:11] <jaheikki3> And package testing is ongoing
[17:05:25] <jaheikki3> We will release Qt 6.8.0 later this week, if no new blockers found during the package testing
[17:05:41] <jaheikki3> And the target is to release Qt 6.8.3 ~mid March, before Qt 6.9.0 release
[17:05:58] <jaheikki3> that's all about Qt 6.8 status at this time. Any comments or questions?
[17:07:19] <vohi[M]> So Qt 6.8.3 will be the last release before the branch enters LTS mode
[17:07:36] <jaheikki3> Yes, that's the plan
[17:08:18] <jaheikki3> Ok, then Qt 6.9 status
[17:08:40] <jaheikki3> Qt 6.9 Beta2 was released last week
[17:08:58] <jaheikki3> Updating 3rd party components for Qt 6.9.0 proceeding well, see https://bugreports.qt.io/browse/QTBUG-132849
[17:09:11] <jaheikki3> Qt 6.9 API change review is still ongoing, see https://bugreports.qt.io/browse/QTBUG-132090
[17:09:25] <jaheikki3> Let's try to finalize open reviews by beta3
[17:09:40] <jaheikki3> The target is to release Qt 6.9.0 Beta3 ~mid February
[17:09:54] <jaheikki3> and the target is to release Qt 6.9.0 RC at the end of February
[17:10:16] <jaheikki3> That's all about Qt 6.9 status at this time. Any comments or questions?
[17:11:07] <vohi[M]> Seems like the headers of every module have now been reviewed, so there should be no more new issues popping up.
[17:11:38] <jaheikki3> yeah, let's hope so.
[17:12:22] <vohi[M]> Discussions still pending by beta3 should be moved to JIRA as blockers for 6.9.0 so that we don't have to check several lists and wade through long discussion threads to see what needs to be done.
[17:13:07] <jaheikki3> yes, that's true. I have already sent one reminder about that in dev ml: see https://lists.qt-project.org/pipermail/development/2025-January/046041.html
[17:14:34] <jaheikki3> it was all at this time so let's end this meeting now and have new one Tue 4th February at this same time
[17:14:46] <jaheikki3> thanks for your participation, bye!
[17:15:39] <frkleint> bye
[17:17:50] <vohi[M]> bye!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20250129/902f8552/attachment-0001.htm>