From jani.heikkinen at qt.io  Wed Apr 10 07:16:17 2024
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 10 Apr 2024 05:16:17 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 09.04.2024
Message-ID: <DB4PR02MB931125593AB1CD3D2C53FE719D062@DB4PR02MB9311.eurprd02.prod.outlook.com>

Qt 6.7 status:

  *   Qt 6.7.0 released Tue 2nd of April 2024
  *   Target is to start branching from 6.7 to '6.7.1' Mon 22nd of April and release Qt 6.7.1 Fri 3rd of May
Qt 6.8 status:

  *   Qt 6.8 feature freeze will be in effect 31st of May and platform and module freeze already 17th of May
     *   if there will be some new modules in Qt 6.8 it would good to start adding those in binary packages as soon as possible
     *   how about the change to build with VS2022?
        *   see https://lists.qt-project.org/pipermail/development/2024-February/044929.html
  *   Snaphot available in the production but not updated lately
     *   The target is to update the snapshot immediately after successful dependency update round in 'dev'
Next meeting Tue 23rd  April 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:16] <jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: The-Compiler: thiago: vohi: ping
[17:00:25] <vohi> jaheikki3: pong
[17:00:35] <akseli> jaheikki3: pong
[17:01:01] <thiago> jaheikki3: pong
[17:01:25] <jaheikki3> time to start qt release team meeting
[17:01:34] <jaheikki3> on agenda today:
[17:01:39] <jaheikki3> Qt 6.7 status
[17:01:42] <jaheikki3> QT 6.8 status
[17:01:52] <jaheikki3> Any additional item to the agenda?
[17:03:30] <jaheikki3> let's start from Qt 6.7 status
[17:03:46] <jaheikki3> Qt 6.7.0 was released Tue 2nd of April
[17:04:33] <jaheikki3> at least one severe regression already reported: https://bugreports.qt.io/browse/QTBUG-123997 (binary break in qtmultimedia)
[17:05:00] <jaheikki3> so let's do the Qt 6.7.1 release a bit earlier than originally planned
[17:05:17] <vohi> agree :)
[17:05:21] <jaheikki3> new target is to start branching from 6.7 to '6.7.1' Mon 22nd of April and release Qt 6.7.1 Fri 3rd of May
[17:05:59] <jaheikki3> that's actually all about Qt 6.7 status at this time. Any comments or questions?
[17:06:30] <krop> I'm not sure if it's considered bic, but I received this report: https://bugzilla.suse.com/show_bug.cgi?id=1222514
[17:06:42] <vohi> wouldn't we usually branch on a Friday and release on a Monday?
[17:06:50] <krop> pyqt build failure with 6.7 likely due to https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7a3fed3f
[17:08:36] <jaheikki3> vohi: true. But I am on vacation 17.4 - 21.4 and CI maintenance break is 6th May
[17:09:31] <jaheikki3> and with patch level releases it doesn't actually matter that much, we can just agree the dates & try to keep those
[17:09:54] <jaheikki3> krop: thanks, I'll check this with Ivan
[17:09:58] <vohi> ack
[17:10:42] <jaheikki3> Then Qt 6.8 status
[17:11:19] <jaheikki3> just a reminder: Qt 6.8 feature freeze will be in effect 31st of May and platform and module freeze already 17th of May
[17:12:01] <thiago> ok
[17:12:16] <jaheikki3> so if there will be some new modules in Qt 6.8 it would good to start adding those in binary packages as soon as possible
[17:12:36] <jaheikki3> a snapshot is already available in the online installer but it hasn't been updated lately
[17:12:59] <jaheikki3> we will update the snapshot after next successful dependency update round in 'dev'
[17:13:39] <jaheikki3> that's all about 6.8 status at this time. Any comments or questions?
[17:13:43] <thiago> how about the change to build with VS2022?
[17:14:42] <jaheikki3> thiago: good point, I think we didn't agree that in the ML last time. I actually have asked that lately from Oliver and Vladimir but didn't get any reply yet
[17:15:17] <jaheikki3> I'll discuss with them soon & let's agree that in ML as soon as possible
[17:15:40] <thiago> I think we need to, because 6.9 is LTS and you'll be reticent to change then
[17:15:49] <thiago> and if you don't, then you're stuck with 2019
[17:16:00] <jaheikki3> true
[17:18:01] <jaheikki3> ok, let's end this meeting now and have new one tue 23rd of April at this same time.
[17:18:14] <jaheikki3> thanks for your participation, bye!
[17:26:44] <vohi> thanks, bye!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20240410/d7ae7fa7/attachment-0001.htm>

From jani.heikkinen at qt.io  Wed Apr 24 06:29:13 2024
From: jani.heikkinen at qt.io (Jani Heikkinen)
Date: Wed, 24 Apr 2024 04:29:13 +0000
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 23.04.2024
Message-ID: <DB4PR02MB93113E012CFEA851608BB15C9D102@DB4PR02MB9311.eurprd02.prod.outlook.com>

Qt 6.7 status

  *   Qt 6.7.1 preparations started
     *   First internal snapshot done, new one coming. The target is to make it publicly available later this week
     *   Branching from '6.7' to '6.7.1' delayed , the target is to do the branching Wed 24th of April
     *   The target is still to release Qt 6.7.1 Fri 3rd of May
Qt 6.8 status

  *   The target is to update the snapshot in the production later this week
  *   Qt 6.8 platform and module freeze will be in effect 17th of May
     *   No new modules known so far
     *   MSVC2022 will replace MSVC2019
     *   Target is to add windows on Arm build & packages from 6.8 ->
Next meeting Tue 30th  April 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:33] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: The-Compiler: thiago: vohi: ping
[17:00:47] <akseli> jaheikki3: pong
[17:01:31] <vohi> jaheikki3: pong
[17:01:40] <thiago> jaheikki3: pong
[17:01:53] <+jaheikki3> time to start qt release team meeting
[17:02:00] <+jaheikki3> on agenda today:
[17:02:04] <+jaheikki3> Qt 6.7 status
[17:02:08] <+jaheikki3> Qt 6.8 status
[17:02:16] <+jaheikki3> Any additional item to the agenda?'
[17:03:51] <+jaheikki3> Ok, let's start from Qt 6.7 status
[17:03:55] <carewolf-work> pong
[17:04:11] <+jaheikki3> Qt 6.7.1 preparations started
[17:04:28] <+jaheikki3> First snapshot done, new one coming
[17:04:44] <+jaheikki3> Target is to make snapshot publicly available later this week
[17:05:34] <+jaheikki3> The target was to branch 6.7.1 from 6.7 Monday 22nd of April but that didn't happen yet
[17:05:58] <+jaheikki3> I was waiting successful dependency update round at first
[17:06:16] <+jaheikki3> It is now done so I'll do the branching tomorrow morning
[17:06:26] <vohi> ah, was about to ask whether I had missed the announcement :)
[17:07:03] <+jaheikki3> Target is still to release Qt 6.7.1 at the beginning of May (3rd of May)
[17:07:24] <+jaheikki3> That's all about 6.7 status at this time. Any comments or questions?
[17:08:37] <+jaheikki3> Ok, the Qt 6.8 status
[17:09:54] <+jaheikki3> dependency round in 'dev succeed last thusday & new round is in its final steps
[17:10:16] <+jaheikki3> target is to update public snapshot this week
[17:10:47] <+jaheikki3> Platform and module freeze will be in effect 17th of May so only a bit more than 3 weeks for this first milestone
[17:11:05] <+jaheikki3> No new modules known so far
[17:11:27] <+jaheikki3> But MSVC2022 will replace MSVC2019 from 6.8 ->
[17:12:04] <+jaheikki3> And we are also adding windows on arm build & packages from 6.8 ->
[17:12:24] <+jaheikki3> that's all about 6.8 status at this time. Any comments or questions?
[17:13:58] <+jaheikki3> ok, lets then end this meeting now & have new meeting tue 30th of April at this same time.
[17:14:10] <+jaheikki3> Thanks for your participation, bye!
[17:14:14] <frkleint> bye
[17:14:19] <carewolf-work> sounds good
[17:14:22] <carewolf-work> bye
[17:14:29] <vohi> bye
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20240424/b10cbdc4/attachment-0001.htm>