[Development] Qt 6.8.0 RC released

[Jani Heikkinen via Development]

Hi all!

We have released the Qt 6.8.0 RC.  As earlier you can get it via online 
installer. Src packages are also available in the Qt Account and 
download.qt.io. Delta to the beta4 attached.

Please test the RC now to see if it is OK for the final Qt 6.8.0 release and 
report all findings in Jira. Please also make sure all blockers for Qt 6.8.0 
release are visible in Qt 6.8.0 blocker list 
(https://bugreports.qt.io/issues/?filter=26320)

Target is to release Qt 6.8.0 Tue 8th October 2024.



br,

Jani Heikkinen

Release Manager

qt5.git
f43651e4d82e20412767d7eba4ecb494d565f2a7 platform_configs: try to use lld 
linker on u24.04 arm64
5d95de4451671b41818df9afe999c75ea79fb0a9 Ubuntu 24.04 arm64: enable the usage 
of sccache
a521c4d920474284989434da20afb18f464b2007 Provisioning: Install nodejs to Ubuntu 
24.04 arm64
6cc4ed9a9b90b583e39ea4ed45e333c9b55a656a sccache: Add arm linux support
63fdac3852a11acc6d814588c5876eb684c2dc5f Adjust submodule branches
f9f017bf5a1cd772bfaca7260dc5ece06e64ce6f Update Mimer SQL macOS binaries
72a484279668a62b75bf4655a5394d5a96895b51 Add the missing provisioning of 
protobuf on the Ubuntu 24.04 aarch64 machine
0da50b756265fe2339865ca7ea8907629e859d47 Move static test build from msvc2019 
to msvc2022
5b09ad616e55ed69d797b80ce550966e251529e6 COIN/QtCreator: Use MSVC2022
15179451a1768c178c6a2b1d29b27e70fed32e29 Provisioning: Add ICU to Ubuntu 24.04 
arm64
cc79b9ec5d94eecf8695e0aa711d792934b67929 CMake: Generate SBOM for more 
platforms tagged with Packaging
e7345107cb517a52520e462d7f752682524ac81e platform_configs: remove 
qtbase-linux-arm64-offscreen.yaml
7562d37e666729e9c504f75b05c35d6a08fc583f platform_configs: remove a few configs 
in qtwayland.yaml
e4defad5e2acf11c4851f5a21588c773507cda3d Provisioning: Build FFmpeg for Windows 
ARM64 in ARM64 host
a24acb5375a63097debb7e6752eaedeb0fcbde4c Restore WoA cross-compile build
ccca79aa5ec39e122cd806c37586b60d1cfe54a4 platform_configs: drop 3 tests configs 
on debian-11 arm64
9bc2004e5cff31a0a621123920e78149d3edbf69 platform_configs: remove 
InsignificantTests for u2404 arm64 offscreen
e1718735144139ec34c1eaf95d5cb8964443fb07 platform_configs: move QtLite to 
Ubuntu 24.04 arm64
qt3d:
a2f8b66f611f5c6d24fc3688c2f66fc7658f3b79 Update assimp to remove non 
distributable models
d55c9c7b25ec2c04c5c795e3bafd96c9ae6cf6e1 Update assimp to 5.4.3
a8aa65a1c48c65aece26319f40395ee4134e7d02 Fix compile warnings
3d46f8cce1ceb370a9ae93667c37064513379bb9 Doc: Replace \instantiates with 
\nativetype
qt5compat:
qtactiveqt:
41de08dda0625cde2e5c75b67b7f241abe2c4f11 CMake: Fix build with CMake 3.16 on 
Windows
a63f62b043b12c364d06d4fef9651af3ed10d906 Correct license in test directory
0ad0716d5cbc5c4db788f7a83c511265aab07f48 Doc: Fix typo
qtbase:
e8122a0a9c6090c8ebe26d5d12320da3267a87c0 QUrl/QDir: revert all recent changes 
to path normalization
c023016ffdda9e2a27c2257ca85a8ffd384e8c08 Revert "QUrl::resolved: switch to 
using qt_normalizePathSegments"
50933122a226a76f10a0a3997337c0f46a0e9313 Doc: Specify correct 
target_link_libraries item for QRhi
0d6b20457300edab9f4d802d0abbb82c229a2374 wasm: Fix missing header files
339feefc5c8854fdc696846d6b78de7b503ba7c4 Update bundled libpng to version 1.6.44
214fbc658bc78ad39e0fb33daf2a3a3fa621b02b QUrl::resolved: switch to using 
qt_normalizePathSegments
e4b298316dda300c7ec722399df88ea77ed7fa00 QUrl::toString: fix using of 
NormalizePathSegments and RemoveFilename
492c646735faa2cad6d0459066dfd723b7ee99b0 Replace qt_normalizePathSegments 
algorithm with QUrl's removeDotsFromPath
804b0996746daae9cf3c901ce353261e1edd7728 QUrl::resolved: remove the lambda in 
removeDotsFromPath()
e4576684681df8fe6d65a2f72379968c187db108 QUrl::resolved: avoid detaching from 
paths that don't have dot segments
8fcfd1a8352233c2d2a668258bc56f3873081777 Coin: Fix Windows aarch64 cross 
compile conditions
bc59c88186e06f2ef0b9e3ea7bf579acef6e52ca Update to Harfbuzz 9.0.0
4e66be84bec20f657c2b5083881eb15d4f553a10 Android: Return QAndroidApplication 
instance via nativeInterface() getter
8f5b06f97723604cbb350c9738a9c265fab7af28 a11y: Use desktop file name as app's 
accessible ID
6a9ee6eb6844c870dc2958961c6f6dd015cb2395 Android: bump AGP to 8.6.0 which 
supports Android 15
893dc6d772f53d8ba44165397d79a2dbc762a6a7 Revert "QGuiApplication: don't send 
pointer events to windows other than the active popup"
10680554db85ba3c5290e9c7dee3cc20c45b0414 qtbase build should't fail with 
-DFEATURE_process=OFF option
2987e96a6c2c8e6fecac70f6ee5bccebb0d483e3 Examples/Sql/Masterdetail: Fix 
deleting rows
05c0ce01fbef7edaf979b4e3d3e2b12aee7101b1 QSqlRelationalTableModel: properly 
clear relational dictionary
2f4680d14308e02bd52abbb81b6c9ae68febe818 Disable q(u)int128 for Clang with 
MSVC's STL
81e6ede3a8256cc92bb6dea37f8cbadf24bbc21e Don't mark 
Q{Explicitly.}SharedDataPointer as Qt_6_PRIVATE_API
998bffecc25dd735175d296303d18ed0df1f9651 Fix warning/crash for MSVC ARM64 mode
10397e53515

[Development] HEADS-UP: Qt 6.7.3 release note review

[Jani Heikkinen via Development]

Hi!

Here is Qt 6.7.3 release note draft: 
https://codereview.qt-project.org/c/qt/qtreleasenotes/+/592425

Please review it asap; we need to finalize it before official release which is 
planned to happen this Friday (27th June)

br,
Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 24.09.2024

[Jani Heikkinen via Development]

Qt 6.7 status

  *   Qt 6.7.3 release content frozen & packages mostly created
  *   The target is to release Qt 6.7.3 Friday 27th of September
 *   Qt 6.7.3 will be the last release from Qt 6.7 series
 *   '6.7' branch will be closed after Qt 6.7.3 is released

Qt 6.8 status

  *   Qt 6.8 RC publicly available
 *   Official release communication will happen Wed 25th September , after 
RTA production tests are done
  *   Target is to release Qt 6.8.0 final release Tue 8th October
 *   blocker list here https://bugreports.qt.io/issues/?filter=26320

Next meeting Tue 8th of October 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:22] <+jaheikki3> akseli: alblasch: carewolf: frkleint: lars__: mapaaso_: 
The-Compiler: thiago: vohi: ping
[17:00:33]  jaheikki3: pong
[17:00:40]  jaheikki3: pong
[17:01:10]  jaheikki3: pong
[17:01:43] <+jaheikki3> Time to start qt release team meeting
[17:01:51] <+jaheikki3> On agenda today
[17:01:55] <+jaheikki3> Qt 6.7 status
[17:01:58] <+jaheikki3> Qt 6.8 status
[17:02:07] <+jaheikki3> Any additional item to the agenda?
[17:03:22] <+jaheikki3> Let's start from Qt 6.7 status
[17:03:42] <+jaheikki3> Qt 6.7.3 release content is frozen
[17:04:09] <+jaheikki3> And packages mostly created, b2qt needed an update & 
new packages coming
[17:04:34] <+jaheikki3> Package testing will start tomorrow
[17:04:50] <+jaheikki3> and the target is to release Qt 6.7.3 this Friday
[17:05:10] <+jaheikki3> and as earlier said it will be the last release from Qt 
6.7 series
[17:05:33] <+jaheikki3> That's all about Qt 6.7 status at this time. Any 
comments or questions?
[17:05:52]  jaheikki3: Sounds good. Cherry-pick bot still complains 
about 6.7 missing in a 'pick-to: 6.8 6.5' line; I guess that will stop once 
6.7.3 has been released?
[17:06:44] <+jaheikki3> Yes, we will close '6.7' after Qt 6.7.3 is closed and 
after that bot should stop complaining about missing Pick-to: 6.7
[17:07:02] <+jaheikki3> after Qt 6.7.3 is released I meant
[17:08:15] <+jaheikki3> Ok, then Qt 6.8 status
[17:08:54] <+jaheikki3> Qt 6.8.0 RC content is frozen, packages are created and 
tested
[17:09:16] <+jaheikki3> and those are already publicly available and production 
testing is ongoing
[17:10:06] <+jaheikki3> so in practise Qt 6.8.0 RC is released today but 
official announcements will be done tomorrow morning, after all production 
tests are done and results verified
[17:10:30] <+jaheikki3> The target is to release Qt 6.8.0 Final release Tue 8th 
September
[17:10:38] <+jaheikki3> blocker list here 
https://bugreports.qt.io/issues/?filter=26320
[17:10:48]  8th October?
[17:11:08] <+jaheikki3> Yes, 8th of October. Thanks frkleint!
[17:11:41] <+jaheikki3> In the blocker list there is already couple of new 
issues and those will be fixed between RC and final
[17:12:10] <+jaheikki3> That's all about 6.8 status. Any comments or questions?
[17:14:17] <+jaheikki3> Ok, let's end this meeting now & have new one Tue 8th 
October at this same time (we have team meeting next Tue and that's why we need 
to skip meeting tue 1st of October)
[17:14:37] <+jaheikki3> thanks for your participation, bye!
[17:14:57]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 17.09.2024

[Jani Heikkinen via Development]

Qt 6.7 status

  *   All known Qt 6.7.3 release blockers fixed
  *   The target is to have release packages for testing Wed 18th September
  *   The target is to release Qt 6.7.3 as soon as possible, hoping already 
Friday 20th of September

Qt 6.8 status

  *   Qt 6.8 RC preparations are ongoing
 *   Branching from '6.8' to '6.8.0' is done
 *   Qt 6.8 RC content not frozen yet; unfortunately there are couple of 
blockers still open in the blocker list 
https://bugreports.qt.io/issues/?filter=26320
 *   The target is to freeze Qt 6.8.0 RC content immediately after all 
blockers are fixed
 *   Hoping we can get RC out at the beginning of next week

Next meeting Tue 24th of September 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:51] <+jaheikki3> akseli: alblasch: carewolf: frkleint: lars__: mapaaso_: 
The-Compiler: thiago: vohi: ping
[17:01:05]  jaheikki3: pong
[17:01:10]  jaheikki3: pong
[17:02:39] <+jaheikki3> Time to start qt release team meeting
[17:02:44] <+jaheikki3> on agenda today:
[17:02:48] <+jaheikki3> Qt 6.7 status
[17:02:53] <+jaheikki3> Qt 6.8 status
[17:03:03] <+jaheikki3> Any additional item to the agenda?
[17:04:10]  pong
[17:05:01] <+jaheikki3> Ok, let's start from 6.7 status
[17:05:43] <+jaheikki3> All known Qt 6.7.3 blockers should have a fix in place 
& integration ongoing.
[17:05:52] <+jaheikki3> Dependency update round also ongoing
[17:06:01] <+jaheikki3> The target is to have release packages tomorrow morning
[17:06:18] <+jaheikki3> and the target is to release Qt 6.7.3 as soon as 
possible, hoping already Friday 20th of September
[17:07:36] <+jaheikki3> But that remains to be seen, Qt 6.7.3 will have lower 
prio than Qt 6.8 RC and so on we will put the effort to release Qt 6.8.0 RC 
when packages available
[17:08:05] <+jaheikki3> that's actually all about Qt 6.7 status, any comments 
or questions?
[17:10:01] <+jaheikki3> ok, next Qt 6.8 status
[17:10:16] <+jaheikki3> Qt 6.8 RC preparations are ongoing
[17:10:28] <+jaheikki3> Branching from '6.8' to '6.8.0' is done
[17:10:45] <+jaheikki3> Qt 6.8 RC content not frozen yet; unfortunately there 
is couple of blockers still open in the blocker list 
https://bugreports.qt.io/issues/?filter=26320
[17:11:07] <+jaheikki3> The target is to freeze Qt 6.8.0 RC content immediately 
after all blockers are fixed
[17:11:19] <+jaheikki3> Hoping we can get RC out at the beginning of next week
[17:11:48] <+jaheikki3> that's actually all about Qt 6.8 status at this time. 
Any comments or questions?
[17:12:57]  both 6.8 blockers are in progress with change in review, but 
the change addressing the issue in Qt3D doesn't have any pick-to targets...
[17:14:44]  i.e. 
https://codereview.qt-project.org/c/qt/qtquick3d-assimp/+/591420; but that's 
our assimp fork, so perhaps the submodule bump in 
https://codereview.qt-project.org/c/qt/qt3d/+/591462 takes care of that?
[17:14:52]  will comment on the changes
[17:14:57] <+jaheikki3> vohi: Actually that assimp one doesn't need to be 
picked anywhere; both qt3d and qtquick3d are using that same repo and branch as 
a submodule
[17:15:20] <+jaheikki3> e.g 
https://codereview.qt-project.org/c/qt/qt3d/+/591490 updates the submodule
[17:15:28] <+jaheikki3> so all is OK related to that
[17:15:46]  yep; ok, then that one is closed, cherry-pick into dev is 
still pending but 6.8.0 is merged
[17:16:08] <+jaheikki3> yeah
[17:16:36] <+jaheikki3> It was all at this time so let's end this meeting now & 
have new one Tue 24th September at this same time
[17:16:50] <+jaheikki3> thanks for your participation, bye!
[17:16:51]  ok, thanks!
[17:16:55]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.8' to '6.8.0' done

[Jani Heikkinen via Development]

Hi!



We have branched '6.8.0' from '6.8' now. So from now on all changes targeted to 
Qt 6.8.0 release must have 'Pick-to: 6.8.0' and '6.8' is for Qt 6.8.1. But 
remember, please do not try to add anything nice-to-haves in '6.8.0' anymore; 
we will take in only fixes for release blockers (+ of course documentation and 
example improvements). As usual, staging will be restricted for release team 
only in '6.8.0'. We will monitor changes and stage clear ones in automatically.


Target is to release Qt 6.8.0 RC Thu 20th of September and Qt 6.8.0 final 
release at the beginning of October. Qt 6.8.0 release blocker list is here: 
https://bugreports.qt.io/issues/?filter=26320. Please make sure all release 
blockers are visible in the blocker list and are fixed immediately.





br,

Jani Heikkinen

Release Manager


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 10.09.2024

[Jani Heikkinen via Development]

Qt 6.7 status

  *   Branching from '6.7' to '6.7.3' is done
  *   Target is to release Qt 6.7.3 Thu 19th September
 *   Qt 6.7.3 will be the last release from Qt 6.7 series


Qt 6.8 status

  *   Qt 6.8 Beta4 is released
  *   Qt 6.8 API review is done
  *   Qt 6.8 RC preparations are ongoing
 *   Branching from '6.8' to '6.8.0' will happen Wed 11th September
 *   Qt 6.8 RC target is 20th of September
 *   RC blocker list here: https://bugreports.qt.io/issues/?filter=26320

Qt 6.9 Initial schedule

  *   Platform and Module freeze 22.11.2024
  *   Feature freeze 6.12.2024
  *   Beta1 19.12.2024
  *   RC: 28.02.2025
  *   Final 18.03.2025


Next meeting Tue 17th of September 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:09] <+jaheikki3> akseli: alblasch: carewolf: frkleint: lars__: mapaaso_: 
The-Compiler: thiago: vohi: ping
[17:01:32]  jaheikki3: pong
[17:02:05] <+jaheikki3> time to start qt release team meeting
[17:02:12] <+jaheikki3> on agenda today:
[17:02:16] <+jaheikki3> Qt 6.7 status
[17:02:21] <+jaheikki3> Qt 6.8 status
[17:02:33] <+jaheikki3> Qt 6.9 Initial schedule
[17:02:46] <+jaheikki3> Any additional item to the agenda?
[17:04:56] <+jaheikki3> Let's start from Qt 6.7 status
[17:05:16] <+jaheikki3> Branching from '6.7' to '6.7.3' is done
[17:05:36] <+jaheikki3> Current target is to release Qt 6.7.3 Thu 19th September
[17:05:57] <+jaheikki3> And as already earlier said Qt 6.7.3 will be the last 
release from Qt 6.7 series
[17:06:19] <+jaheikki3> that's actually all about Qt 6.7 status at this time. 
Any comments or questions?
[17:07:38] <+jaheikki3> ok, then Qt 6.8 status:
[17:08:04] <+jaheikki3> Qt 6.8 Beta4 is released and Qt 6.8 RC preparations are 
ongoing
[17:08:36] <+jaheikki3> Qt 6.8 API review is finally completed, big thanks to 
all your effort here!
[17:09:33] <+jaheikki3> Dependency update round it almost done & it is 
including the last API review related changes
[17:09:51] <+jaheikki3> So branching from '6.8' to '6.8.0' will happen tomorrow 
morning
[17:10:11] <+jaheikki3> And new RC target is 20th of September
[17:10:19] <+jaheikki3> RC blocker list here: 
https://bugreports.qt.io/issues/?filter=26320
[17:11:33] <+jaheikki3> And final release will happen ~2 weeks after RC, at the 
beginning of October
[17:11:46] <+jaheikki3> that's all about Qt 6.8 status. Any comments or 
questions?
[17:12:57]  sounds good
[17:13:16] <+jaheikki3> great! then the Qt 6.9 initial schedule:
[17:13:45] <+jaheikki3> Proposal sent to ML 
(https://lists.qt-project.org/pipermail/development/2024-September/045607.html) 
~ a week ago.
[17:13:55] <+jaheikki3> no obejctions or comments so Qt 6.9 initial schedule 
will be:
[17:14:02] <+jaheikki3> Platform and Module freeze 22.11.2024
[17:14:10] <+jaheikki3> Feature freeze 6.12.2024
[17:14:16] <+jaheikki3> Beta1 19.12.2024
[17:14:22] <+jaheikki3> RC: 28.02.2025
[17:14:29] <+jaheikki3> Final 18.03.2025
[17:15:09] <+jaheikki3> any comments or questions?
[17:15:35]  I think that's good
[17:15:45]  that means any features I work over Christmas are 6.10
[17:15:48]  but ok
[17:17:07] <+jaheikki3> great! It was all at this time so let's end this 
meeting now & have new one Tue 17th September at this same time
[17:17:17] <+jaheikki3> thanks for your participation, bye!
[17:17:22]  thanks, bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Qt 6.9.0 initial schedule

[Jani Heikkinen via Development]

Hi!

It is again time to agree initial schedule for Qt 6.9.0.

Here is the proposal:


  *   Platform and Module freeze 22.11.2024
  *   Feature freeze 6.12.2024
  *   Beta1 19.12.2024
  *   RC: 28.02.2025
  *   Final 18.03.2025

Any comments? As usual it is based on Qt 6.7.0 initial schedule...

br,
Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 27.08.2024

[Jani Heikkinen via Development]

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]  jaheikki3: pong
[17:00:27]  jaheikki3: pong
[17:02:06]  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]  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]  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]  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]  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]  in which case branching off in the week after Qt CS (ie. Sept 
13th) might make sense?
[17:11:50]  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]  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]  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]  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]  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]  skip
[17:23:49]  we'll be seeing each other the next day
[17:24:24]  I'll be unavailable next

[Development] HEADS UP : Qt 6.8 string freeze

[Jani Heikkinen via Development]

Hi all,



String freeze for Qt 6.8 is in effect now.



br,

Jani


From: Jani Heikkinen
Sent: keskiviikko 21. elokuuta 2024 8.05
To: localizat...@qt-project.org; development@qt-project.org; 
releas...@qt-project.org
Subject: HEADS UP : Qt 6.8 soft string freeze


Hi all,

First beta releases from Qt 6.8 are out and it is time to start keeping 
translatable strings as it is. The official string freeze for Qt 6.8 will be in 
effect Tue 27th of August 2024.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS UP : Qt 6.8 soft string freeze

[Jani Heikkinen via Development]

Hi all,

First beta releases from Qt 6.8 are out and it is time to start keeping 
translatable strings as it is. The official string freeze for Qt 6.8 will be in 
effect Tue 27th of August 2024.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 20.08.2024

[Jani Heikkinen via Development]

Qt 6.8 status

  *   Qt 6.8 Beta3 is released
  *   Qt 6.8 Beta4 preparations are started
 *   The target is to release Qt 6.8 Beta4 during next week
*   Beta4 should be the last beta release from Qt 6.8
  *   Qt 6.8.0 string freeze will be in effect Tue 27th August
  *   Qt 6.8 RC target is 11th of September
 *   RC blocker list here: https://bugreports.qt.io/issues/?filter=26320
  *   Qt 6.8 API change review is still ongoing, see 
https://codereview.qt-project.org/q/topic:%22qml_api_review_6.8%22+or+topic:%22api-change-review-6.8%22+status:open
  *   New Qt 6.8 FF exception request for VwWorks input handling: 
https://lists.qt-project.org/pipermail/development/2024-August/045522.html
 *   Decision: It is ok to get this into 6.8 (once it has gone into dev).


Next meeting Tue 27th of August 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:30]  akseli: alblasch: carewolf: frkleint: lars__: mapaaso_: 
The-Compiler: thiago: vohi: ping
[17:00:47]  jaheikki3_: pong
[17:02:38]  time to start qt release team meeting
[17:02:44]  on agenda today:
[17:02:48]  jaheikki3_: pong :)
[17:02:53]  Qt 6.8 status
[17:03:07]  Any additional item to the agenda?
[17:03:14]  jaheikki3_: pong
[17:04:28]  Ok, let's browse through the Qt 6.8 status
[17:04:47]  Qt 6.8.0 Beta3 released last week
[17:04:58]  beta4 preparations are started
[17:05:13]  Target is to release Qt 6.8 Beta4 during next week
[17:05:29]  Beta4 should be the last beta release from Qt 6.8.0
[17:06:38]  Qt 6.8.0 string freeze will be in effect next Tue 27th 
August
[17:07:03]  and the target is to release Qt 6.8.0 RC 11th of 
September
[17:07:14]  RC blocker list here: 
https://bugreports.qt.io/issues/?filter=26320
[17:07:28]  Qt 6.8 API change review is still ongoing, see 
https://codereview.qt-project.org/q/topic:%22qml_api_review_6.8%22+or+topic:%22api-change-review-6.8%22+status:open
[17:08:06]  We should get critical API review findings in blocker 
list asap
[17:08:35]  uh, this blocker list ignores P1s with "fix version 6.8 RC", 
for instance
[17:09:10]  ixVersion ~ "6.8.0*"
[17:09:33]  vohi: It shouldn't. Or it would if there would be such 
a version but there isn't; it is 6.8.0 RC
[17:09:39]  change it to 6.8* and you get more
[17:09:52]  it's what's there
[17:10:00]  I'm seeing 12 issues
[17:10:16]  ah, right; "6.8.0 RC" is there, but P1's with "fix version 
6.8*" gives 37
[17:10:17]  carewolf: I tried it but noticed there is quite a much 
issues having 6.8 in fix versions.
[17:10:37]  yeah 37. Not sure how many would be blockers
[17:11:13]  And based on discussions with developers they aren't 
proposing those to be a blocker for 6.8.0 but a plan to fix those in some Qt 
6.8.x release
[17:11:36]  That's why I use 6.8.0*
[17:11:51]  ok
[17:12:10]  there's a wrong parenthesis set
[17:12:39]  thiago: where?
[17:12:40]  ah, no
[17:12:44]  Great :D
[17:12:58]  I'd rather have more potential blockers than fewer, at this 
point of the release cycle
[17:13:42]  it's tedious to discuss them of course, but that's still 
better than releasing with a bunch of paper-bag issues that we didn't see 
because we filtered too many things out
[17:15:34]  vohi: agree & actually checked those '6.8' ones 
already. Almos all of those were from fabian or ulf and I checked from them 
what was their intention and the reply was that it doesn't mean those are 
blockers for 6.8.0
[17:15:59]  but then the right thing to do is to clear the fix-version, 
isn't it?
[17:17:00]  vohi: well, they want to use that to indicate the issue 
is something to be fixed in Qt 6.8.x
[17:17:15]  but I agree it is a bit confusing
[17:17:30]  I can live with it
[17:18:45]  Ok, but back to agenda. We got an Qt 6.8 FF exception 
request for VwWorks input handling: 
https://lists.qt-project.org/pipermail/development/2024-August/045522.html
[17:18:57]  Any opinions for that?
[17:19:48]  well it doesnt' affect out API? I guess vxworks wasn't 
working before?
[17:19:58]  I think implementing support for functionality that work on 
other platforms is not a feature; but the change should not introduce risks to 
other platforms, and the VxWorks specific implementation should be isolated
[17:20:01]  I don't consider that a new feature
[17:20:10]  catching up with existing functionality on a currently 
non-functional port
[17:21:02]  Agree
[17:22:17]  so, ok to get this into 6.8 (once it has gone into dev); the 
patches might not be as clean as they could be, but generally all the changes 
are behind "#ifdef Q_OS_VXWORKS" flags or in a separate translation unit
[17:22:37]  Yeah
[17:23:00]  Laszlo has some comments on the second patch in their chain 
in that respect, his privilege to approve or reject anyway. But no reason to 
worry about feature freeze.
[17:24:39]  I think it was all at this time so let'

[Development] Meeting minutes from Qt Release Team meeting 06.08.2024

[Jani Heikkinen via Development]

Qt 6.8 status

  *   Qt 6.8.0 Beta2 is released, beta3 preparations are started
 *   The goal is to release beta3 from the next successful dependency 
update round in the '6.8' branch
 *   The target is to publish Beta3 Tue 13th of August.
  *   Qt 6.8 API change review is still ongoing, see 
https://codereview.qt-project.org/q/topic:%22qml_api_review_6.8%22+or+topic:%22api-change-review-6.8%22+status:open
  *   Updating 3rd party components for Qt 6.8.0 is also ongoing, see 
https://bugreports.qt.io/browse/QTBUG-126058

Next meeting Tue 13th of August 2024 16:00 CET

br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:06]  alblasch: akseli: carewolf_work: frkleint: lars__: 
mapaaso_: The-Compiler: thiago: vohi: ping
[17:01:03]  jaheikki3_: pong
[17:01:48]  time to start qt release team meeting
[17:01:58]  on agenda today:
[17:02:02]  Qt 6.8 status
[17:02:10]  Any additional item to the agenda?
[17:03:16]  ok, let's browse through the Qt 6.8 status
[17:03:49]  Qt 6.8.0 Beta2 released a while ago and Qt 6.8.0 beta3 
preparations started
[17:04:22]  The goal is to release beta3 from the next successful 
dependency update round in the '6.8' branch (which is actually just started)
[17:04:37]  and the target is to publish Beta3 Tue 13th of August
[17:04:58]  Qt 6.8 API change review is still ongoing, see 
https://codereview.qt-project.org/q/topic:%22qml_api_review_6.8%22+or+topic:%22api-change-review-6.8%22+status:open
[17:05:14]  Please check if you can help to proceed with those
[17:05:57]  We should finalize API reviews in beta phase so latest 
by the end of August
[17:06:06]  Updating 3rd party components for Qt 6.8.0 is also 
still ongoing, see https://bugreports.qt.io/browse/QTBUG-126058
[17:06:35]  That's actually all about Qt 6.8 status at this time
[17:06:42]  any comments or questions?
[17:08:19]  it was all at this time so let's end this meeting now & 
have new one Tue 13th Aug at this same time
[17:08:32]  Thanks for your participation, bye!
[17:08:46]  thanks

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.7.2 release note review

[Jani Heikkinen via Development]

Hi!

Here is Qt 6.7.2 release note draft: 
https://codereview.qt-project.org/c/qt/qtreleasenotes/+/567597

Please review it asap; we need to finalize it before official release which is 
planned to be happen this Friday (14th June)

br,
Jani
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS-UP: Qt 6.8 API change review

[Jani Heikkinen via Development]

Hi!

I think the reason for this is that v6.7.0 is the API which is reviewed last 
time. Using it as a base ensures that API changes in 6.7.x release will be 
reviewed as well

br,
Jani

> -Original Message-
> From: Volker Hilsheimer 
> Sent: perjantai 7. kesäkuuta 2024 17.13
> To: Jani Heikkinen 
> Cc: development@qt-project.org
> Subject: Re: [Development] HEADS-UP: Qt 6.8 API change review
> 
> >
> > On 4 Jun 2024, at 09:29, Jani Heikkinen via Development  project.org> wrote:
> >
> > Hi!
> >  Qt 6.8 API Change Review is started, see
> https://bugreports.qt.io/browse/QTBUG-125859
> > generated diffs are here:
> > • https://codereview.qt-project.org/q/topic:api-change-review-6.8
> > • https://codereview.qt-project.org/q/topic:qml_api_review_6.8
> >  Please review the diffs as soon as possible.
> >  br,
> > Jani
> 
> 
> Is there a good reason for comparing 6.7.0 to 6.8, rather than 6.7 to 6.8? I 
> see a
> few differences that shouldn’t be there (or should be … different), because 
> the
> respective patch have also been cherry-picked to 6.7. E.g. qtmultimedia fixes 
> to
> the BiC bug.
> 
> 
> Volker
> 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.7' to '6.7.2' done

[Jani Heikkinen via Development]

Hi!



We have branched '6.7.2' from '6.7' now. So from now on all changes targeted to 
Qt 6.7.2 release must have 'Pick-to: 6.7.2' and '6.7' is for Qt 6.7.3. And 
please remember: We need to get Qt 6.7.2 released really quickly, before summer 
holiday season starts, so do not try to add anything nice-to-haves in '6.7.2' 
anymore; we will take in only fixes for release blockers (+ of course 
documentation and example improvements).



As usual, staging will be restricted for release team only in '6.7.2'. We will 
monitor changes and stage clear ones in automatically.



The target is to release Qt 6.7.2 Fri 14th June.





br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Meeting minutes from Qt Release Team meeting 04.06.2024

[Jani Heikkinen via Development]

Hi!

After discussing with the different stakeholders the plan is to do a pretty 
quick Qt 6.7.2 release
- Branching from '6.7' to '6.7.2' today
- Release target 14th June

And all this means the Qt 6.7.2 content is pretty much frozen, only fixes for 
real showstoppers will be taken in '6.7.2'

And this accelerated Qt 6.7.2 plan also means we won't do hotfix release for Qt 
6.7.2 during the summer time; if it will be badly broken will have to live with 
it or hide whole Qt 6.7.2 release.
br,
Jani

From: Releasing  On Behalf Of Jani Heikkinen 
via Releasing
Sent: keskiviikko 5. kesäkuuta 2024 6.52
To: releas...@qt-project.org; development@qt-project.org
Subject: [Releasing] Meeting minutes from Qt Release Team meeting 04.06.2024

Qt 6.8 status

  *   Qt 6.8 feature freeze is in effect
  *   Branching from 'dev' to '6.8' is done
  *   Qt 6.8 API change review is started, see 
https://lists.qt-project.org/pipermail/development/2024-June/045374.html
  *   Qt 6.8 Beta1 preparations are started

 *   Dependency update round in '6.8' succeed so Qt 6.8 Beta1 content 
should be in place
 *   Packaging ongoing, some updates still needed to the packaging configs 
for Qt 6.8.0
 *   Target is to release Qt 6.8 Beta1 as soon as possible, latest Thu 13th 
of June

New Qt 6.8 FF Exception requests:

 *   QtAbstractItemModel, QtModelIndex and QtAbstactListModel:

*   Exception not needed, finishing those features by writing 
tests/documentation/examples does not require an exception
Qt 6.7 status

  *   Some quite critical regressions reported from Qt 6.7.1. Jani to check & 
decide if it is still possible to release Qt 6.7.2 by the end of June (without 
causing too much hassle with other releases etc.)

Improve release note & process

  *   Jani will sent release note review request to dev ML immediately when 
note available.

Next meeting Tue 11th of June 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:55] <+jaheikki3> akseli: alblasch: carewolf: frkleint: lars__:mapaaso: 
The-Compiler: thiago: vohi: ping
[17:01:03]  jaheikki3: pong
[17:01:05]  jaheikki3: pong
[17:02:04]  jaheikki3: pong
[17:02:57] <+jaheikki3> time to start qt release team meeting
[17:03:06] <+jaheikki3> on agenda today:
[17:03:07]  jaheikki3: pong
[17:03:14] <+jaheikki3> Qt 6.8 status
[17:03:27] <+jaheikki3> Qt 6.8 FF exceptions
[17:03:37] <+jaheikki3> Any additional item to the agenda?
[17:04:06]  one thing to discuss, wrt the "release notes" thread on the 
mailing list: what can we improve, and avoid that we claim BC if the change log 
later on says it's not :)
[17:04:19]  (which are perhaps two things)
[17:04:53]  is there any hope for a 6.7.1.1 release.. we have a kind 
of facepalm bug in Qt Designer ( https://bugreports.qt.io/browse/QTBUG-125983 )
[17:05:03]  6.7.2
[17:05:04]  just in case some other bug shows up../
[17:05:09]  we're not running out of numbers
[17:05:16] <+jaheikki3> vohi: maybe that's something which needs a bit longer 
discussion than this meeting
[17:06:03] <+jaheikki3> But we can start the discussion here
[17:06:29]  ack
[17:06:45] <+jaheikki3> and we can discuss about 6.7.2 plans as well
[17:07:01] <+jaheikki3> But let's start from Qt 6.8 status
[17:07:23] <+jaheikki3> Qt 6.8 feature freeze is in effect now (as planned)
[17:07:42] <+jaheikki3> Branching from 'dev' to '6.8' is also done
[17:08:05] <+jaheikki3> And Qt 6.8 Beta1 preparations are started
[17:08:35] <+jaheikki3> Dependency update round in '6.8' succeed already and so 
on we should have Qt 6.8 Beta1 content is in place
[17:09:25] <+jaheikki3> Qt 6.8 Beta1 packaging ongoing but some updates still 
needed to configs before we can start testing beta1
[17:09:50] <+jaheikki3> The target is to release Qt 6.8 Beta1 as soon as 
possible, latest thu 13th of June
[17:10:18] <+jaheikki3> That's all about Qt 6.8 status at this time. Any 
comments or questions?
[17:12:34] <+jaheikki3> Ok, then new Qt 6.8 FF exceptions:
[17:12:53] <+jaheikki3> In the ML there isn't any new FF exceptions, right?
[17:13:11]  There was "Feature freeze exception: QtAbstractItemModel, 
QtModelIndex and QtAbstactListModel"
[17:13:40]  but I agree with Ulf that finishing those features by writing 
tests/documentation/examples does not require an exception
[17:13:54] <+jaheikki3> That's true and I agree
[17:14:11]  no other exception requests that I am aware of so far
[17:14:30] <+jaheikki3> In addition to that there might be the webengine one we 
shortly discussed last week, carewolf:?
[17:14:56] <+jaheikki3> (at least alblasch chatted me about that yesterday)
[17:16:41] <+jaheikki3> It seems carewolf isn't here now so I think we need to 
handle that later i

[Development] Meeting minutes from Qt Release Team meeting 04.06.2024

[Jani Heikkinen via Development]

Qt 6.8 status

  *   Qt 6.8 feature freeze is in effect
  *   Branching from 'dev' to '6.8' is done
  *   Qt 6.8 API change review is started, see 
https://lists.qt-project.org/pipermail/development/2024-June/045374.html
  *   Qt 6.8 Beta1 preparations are started
 *   Dependency update round in '6.8' succeed so Qt 6.8 Beta1 content 
should be in place
 *   Packaging ongoing, some updates still needed to the packaging configs 
for Qt 6.8.0
 *   Target is to release Qt 6.8 Beta1 as soon as possible, latest Thu 13th 
of June

New Qt 6.8 FF Exception requests:

 *   QtAbstractItemModel, QtModelIndex and QtAbstactListModel:
*   Exception not needed, finishing those features by writing 
tests/documentation/examples does not require an exception
Qt 6.7 status

  *   Some quite critical regressions reported from Qt 6.7.1. Jani to check & 
decide if it is still possible to release Qt 6.7.2 by the end of June (without 
causing too much hassle with other releases etc.)

Improve release note & process

  *   Jani will sent release note review request to dev ML immediately when 
note available.

Next meeting Tue 11th of June 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:55] <+jaheikki3> akseli: alblasch: carewolf: frkleint: lars__:mapaaso: 
The-Compiler: thiago: vohi: ping
[17:01:03]  jaheikki3: pong
[17:01:05]  jaheikki3: pong
[17:02:04]  jaheikki3: pong
[17:02:57] <+jaheikki3> time to start qt release team meeting
[17:03:06] <+jaheikki3> on agenda today:
[17:03:07]  jaheikki3: pong
[17:03:14] <+jaheikki3> Qt 6.8 status
[17:03:27] <+jaheikki3> Qt 6.8 FF exceptions
[17:03:37] <+jaheikki3> Any additional item to the agenda?
[17:04:06]  one thing to discuss, wrt the "release notes" thread on the 
mailing list: what can we improve, and avoid that we claim BC if the change log 
later on says it's not :)
[17:04:19]  (which are perhaps two things)
[17:04:53]  is there any hope for a 6.7.1.1 release.. we have a kind 
of facepalm bug in Qt Designer ( https://bugreports.qt.io/browse/QTBUG-125983 )
[17:05:03]  6.7.2
[17:05:04]  just in case some other bug shows up../
[17:05:09]  we're not running out of numbers
[17:05:16] <+jaheikki3> vohi: maybe that's something which needs a bit longer 
discussion than this meeting
[17:06:03] <+jaheikki3> But we can start the discussion here
[17:06:29]  ack
[17:06:45] <+jaheikki3> and we can discuss about 6.7.2 plans as well
[17:07:01] <+jaheikki3> But let's start from Qt 6.8 status
[17:07:23] <+jaheikki3> Qt 6.8 feature freeze is in effect now (as planned)
[17:07:42] <+jaheikki3> Branching from 'dev' to '6.8' is also done
[17:08:05] <+jaheikki3> And Qt 6.8 Beta1 preparations are started
[17:08:35] <+jaheikki3> Dependency update round in '6.8' succeed already and so 
on we should have Qt 6.8 Beta1 content is in place
[17:09:25] <+jaheikki3> Qt 6.8 Beta1 packaging ongoing but some updates still 
needed to configs before we can start testing beta1
[17:09:50] <+jaheikki3> The target is to release Qt 6.8 Beta1 as soon as 
possible, latest thu 13th of June
[17:10:18] <+jaheikki3> That's all about Qt 6.8 status at this time. Any 
comments or questions?
[17:12:34] <+jaheikki3> Ok, then new Qt 6.8 FF exceptions:
[17:12:53] <+jaheikki3> In the ML there isn't any new FF exceptions, right?
[17:13:11]  There was "Feature freeze exception: QtAbstractItemModel, 
QtModelIndex and QtAbstactListModel"
[17:13:40]  but I agree with Ulf that finishing those features by writing 
tests/documentation/examples does not require an exception
[17:13:54] <+jaheikki3> That's true and I agree
[17:14:11]  no other exception requests that I am aware of so far
[17:14:30] <+jaheikki3> In addition to that there might be the webengine one we 
shortly discussed last week, carewolf:?
[17:14:56] <+jaheikki3> (at least alblasch chatted me about that yesterday)
[17:16:41] <+jaheikki3> It seems carewolf isn't here now so I think we need to 
handle that later if needed
[17:17:01] <+jaheikki3> Then we could check Qt 6.7.2 plans
[17:17:25] <+jaheikki3> Original plan was to release Qt 6.7.2 after summer 
holidays, ~ mid August
[17:18:29]  I am here now
[17:18:45]  we have integrated all features we need in webengine now.
[17:19:05] <+jaheikki3> Ok, so no need for exception, great
[17:19:35]  I found three bugs reported as regressions 6.7.0 -> 6.7.1 
(https://bugreports.qt.io/browse/QTBUG-125858, 
https://bugreports.qt.io/browse/QTBUG-125497, and 
https://bugreports.qt.io/browse/QTBUG-125481) in addition to the Qt Designer 
bug; unclear how realistic it is to fix all of them so quickly that a 6.7.2 
before summer break is realistic though
[17:20:43] <+jaheikki3> Yeah, it will be really h

[Development] HEADS-UP: Qt 6.8 API change review

[Jani Heikkinen via Development]

Hi!



Qt 6.8 API Change Review is started, see 
https://bugreports.qt.io/browse/QTBUG-125859

generated diffs are here:

  *   https://codereview.qt-project.org/q/topic:api-change-review-6.8
  *   https://codereview.qt-project.org/q/topic:qml_api_review_6.8



Please review the diffs as soon as possible.



br,

Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from 'dev' to '6.8' done & Qt 6.8 Feature Freeze in effect

[Jani Heikkinen via Development]

Hi!

Branching from 'dev' to '6.8' is now done and the Qt 6.8 Feature Freeze is in 
effect! So from now on all changes targeted to the Qt 6.8 must have 'Pick-to: 
6.8' and 'dev' is for Qt 6.9.



Staging qt5.git#6.8 will be restricted until Qt 6.8 beta1 is out but 
restrictions in 'dev' are removed & you can start staging changes in qt5.git#dev



br,

Jani Heikkinen

Release Manager


From: Jani Heikkinen
Sent: perjantai 31. toukokuuta 2024 14.39
To: development@qt-project.org
Subject: HEADS-UP: Qt 6.8 Feature Freeze today


Hi!



Qt 6.8 Feature Freeze will be in effect today. If your changes are ready and 
approved by the end of today, you can still continue staging those in 'dev' 
over the weekend. The plan is to branch from "6.8" to "dev" on Monday morning 
(3rd of June).



If your feature isn't ready by the end of today, you'll either need to postpone 
it to Qt 6.9 or request an exception.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.8 Feature Freeze today

[Jani Heikkinen via Development]

Hi!



Qt 6.8 Feature Freeze will be in effect today. If your changes are ready and 
approved by the end of today, you can still continue staging those in 'dev' 
over the weekend. The plan is to branch from "6.8" to "dev" on Monday morning 
(3rd of June).



If your feature isn't ready by the end of today, you'll either need to postpone 
it to Qt 6.9 or request an exception.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 28.05.2024

[Jani Heikkinen via Development]

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]  jaheikki3: pong
[17:00:33]  jaheikki3: pong
[17:01:16]  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]  jaheikki3: pong
[17:02:40]  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]  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]  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]  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]  I don't think SBOM is a feature per se
[17:14:20]  but fair, it's excepted
[17:15:15]  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]  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]  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]  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 l

[Development] Heads-up: what's new in '6.8' -documentation needs updates

[Jani Heikkinen via Development]

Hi all,
Qt 6.8 Feature Freeze will be in effect this Friday and 
https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew68.qdoc seem 
to be still quite unfinished ☹ It would be good to get some more content there 
for Qt 6.8 Beta1 so please do at least most important updates now; finalizing 
and polishing can then happen later in beta phase.

br,
Jani


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Feature and provisioning freeze exception for SBOM (Software Bill of Materials) generation

[Jani Heikkinen via Development]

Hi!

I don't have any opinion about FF exception for this but what comes to 
https://codereview.qt-project.org/c/qt/qt5/+/561694  I think we can wait 
branching & integrate this in 'dev' after it; In big picture it is more 
important to keep CI & provisioning as stable as possible this close to feature 
freeze to make sure we can keep FF schedule (and so on Qt 6.8.0 final schedule 
as well) and get Beta1 out before summer vacations starts... And if FF 
exception is granted you can pick provisioning change in '6.8' after beta1.

br,
Jani

> -Original Message-
> From: Development  On Behalf Of
> Alexandru Croitor via Development
> Sent: tiistai 21. toukokuuta 2024 12.28
> To: Qt development mailing list 
> Subject: [Development] Feature and provisioning freeze exception for SBOM
> (Software Bill of Materials) generation
>
> Hi,
>
> I would like to request a feature freeze and provisioning freeze exception for
> SBOM (Software Bill of Materials) generation.
>
> https://codereview.qt-project.org/c/qt/qtbase/+/546923
> https://codereview.qt-project.org/c/qt/qt5/+/561694
>
> SBOM generation is about shipping some text files alongside the built Qt
> libraries, that describe things like 3rd party dependencies used, checksums of
> built files, copyright info, license info, etc.
> Some details at
> https://www.n/
> tia.gov%2Fpage%2Fsoftware-bill-
> materials&data=05%7C02%7Cjani.heikkinen%40qt.io%7C76efd9f976324c74a
> d5408dc7978b429%7C20d0b167794d448a9d01aaeccc1124ac%7C0%7C0%7C6
> 38518806536519047%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM
> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&s
> data=EO%2BPZlyYYYsbiZjAr70Ak5wjWL9hF2mkxs%2FGgVHt7YM%3D&reserve
> d=0
>
> SBOM generation for Qt was planned for 6.8, but it is likely won't be finished
> in time for FF.
>
> The generation itself only requires build system changes, no C++ API changes
> required.
>
> The only user-facing changes would be a new opt-in configure flag (.e.g -
> sbom) and additional files being installed as part of Qt (one spdx.json file 
> for
> each repository built).
>
> Verification and auditing of the generated files needs some additional python
> packages to be available during the CI build, hence the request for
> provisioning exception.
>
> The impact for those who don't opt-in should be zero, and for the CI,
> installing some additional python packages is nothing new, and hopefully
> shouldn't cause any breakage.
>
> We'd like to have this in for 6.8 because it's an LTS release, and because of 
> the
> new EU CRA law (Cyber Resilience Act) pending.
>
> It would also be good to receive feedback during 6.8 release whether we lack
> any info in the generated SBOM, so we can fix it for the LTS.
>
> Regards,
> Alexandru.
> --
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Provisioning freeze exception for building FFmpeg as shared libraries

[Jani Heikkinen via Development]

Hi!

In my opinion we can wait branching & integrate this in 'dev' after it. And 
pick changes in '6.8' after beta1; it is more important to keep CI & 
provisioning as stable as possible this close to feature freeze to make sure we 
can keep FF schedule (and so on Qt 6.8.0 final schedule as well) and get Beta1 
out before summer vacations starts...

br,
Jani

> -Original Message-
> From: Development  On Behalf Of
> Jøger Hansegård via Development
> Sent: tiistai 21. toukokuuta 2024 18.53
> To: development@qt-project.org
> Subject: [Development] Provisioning freeze exception for building FFmpeg as
> shared libraries
> 
> Hi,
> 
> I would like to request a provisioning freeze exception for building FFmpeg as
> shared libraries.
> 
> The goal of this change is to make it easier to transition Qt Multimedia
> applications from legacy native media backends to the default FFmpeg media
> backend.
> 
> Although the FFmpeg media backend can still be built with static linking to
> FFmpeg, we will switch to dynamic linking against FFmpeg for binaries
> deployed by the Qt Online Installer. This is already released for Windows in 
> Qt
> 6.7 and will be implemented for all platforms in Qt 6.8.
> 
> FFmpeg is built as part of provisioning, and the corresponding scripts must
> therefore be updated to build FFmpeg as shared libraries on the remaining
> platforms, iOS, Linux, and Android.
> 
> * https://bugreports.qt.io/browse/QTBUG-120990
> * https://bugreports.qt.io/browse/QTBUG-120991
> * https://bugreports.qt.io/browse/QTBUG-122010
> 
> Since the change has implications for application deployment, we depend on
> getting early feedback on the change, and if possible, as part of beta 1.
> 
> Best regards,
> Jøger Hansegård
> --
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.8 platform and module freeze

[Jani Heikkinen via Development]

Hi!

Qt 6.8 platform and module freeze is in effect now, so no new modules or 
provisioning related changes in 'dev' until '6.8' is branched. Staging in 
qt5#dev is restricted to release team only until branching is done.

br,
Jani



From: Jani Heikkinen
Sent: tiistai 23. huhtikuuta 2024 9.37
To: development@qt-project.org
Subject: HEADS-UP: Qt 6.8 Feature Freeze is getting closer


Hi all,



Just a kindly reminder: Qt 6.8 Feature freeze will be in effect 31st of May 
2024 and Qt 6.8 platform and module freeze already 17th of May 2024, see 
https://wiki.qt.io/Qt_6.8_Release.



Please inform me about all new modules planned to be released in Qt 6.8; we 
should start adding those in CI & packages now. Also please inform me if 
existing technology preview module will be officially supported etc.



br,

Jani Heikkinen
Release Manager
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 14.05.2024

[Jani Heikkinen via Development]

Qt 6.7 status

  *   Qt 6.7.1 preparations are still ongoing
 *   Unfortunately couple of new p0 issues reported. Fixes are in & 
dependency update round is ongoing
 *   The target is to get new packages for testing as soon as possible and 
release Qt 6.7.1 Mon 20th of May
Qt 6.8 status

  *   Platform and Module Freeze will be in effect Fri 17th of May


Next meeting Tue 28th of May 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:08] <+jaheikki3> ablasche: akseli: carewolf: frkleint: lars__: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:27]  jaheikki3: pong
[17:02:39] <+jaheikki3> Time to start qt release team meeting
[17:02:44] <+jaheikki3> on agenda today:
[17:02:47] <+jaheikki3> Qt 6.7 status
[17:02:52] <+jaheikki3> Qt 6.8 statuss
[17:03:05] <+jaheikki3> any other issue to the agenda?
[17:03:08]  pogn
[17:03:13]  jaheikki3: pong
[17:04:12] <+jaheikki3> ok, let's start from Qt 6.7 status:
[17:04:25] <+jaheikki3> Qt 6.7.1 preparations are still ongoing
[17:04:54] <+jaheikki3> Unfortunately couple of new p0 issues reported. Fixes 
are in & dependency update round ongoing
[17:05:17] <+jaheikki3> The target is to get new packages for testing tomorrow 
and release Qt 6.7.1 Mon 20th of May
[17:05:42] <+jaheikki3> that's all about Qt 6.7 status at this time. Any 
comments or questions?
[17:07:21] <+jaheikki3> ok, then quick Qt 6.8 status update
[17:07:48] <+jaheikki3> Platform and Module Freeze will be in effect this 
friday.
[17:08:14] <+jaheikki3> So no provisioning related changes after that in 'dev' 
before '6.8' is branched
[17:09:07]  any news on vs2022 builds?
[17:09:12]  I haven't seen anything
[17:09:36] <+jaheikki3> thiago: builds are up and running in CI
[17:10:34] <+jaheikki3> and packaging related changes are ongoing. The target 
is to publish a snapshot with msvc2022 packages before FF
[17:11:09] <+jaheikki3> that's all about 6.8 status at this time. Any comments 
or questions?
[17:13:11] <+jaheikki3> It was all at this time so let's end this meeting now & 
have new one tue 28th May at this same time; I can't join next week...
[17:13:24] <+jaheikki3> thanks for your participation, bye!
[17:13:42]  bye
[17:14:10]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 07.05.2024

[Jani Heikkinen via Development]

Qt 6.7 status

  *   Qt 6.7.1 preparations are ongoing
 *   Release content is frozen & RTA testing ongoing
 *   The target is to release Qt 6.7.1 Tue 14th of May
*   Unfortunately new p0 already found so let’s see if that will happen 
or will there be more delay…
Qt 6.8 status

  *   Snapshot updated to the production. Target is to update it regularly 
after successful dependency update round in ‘dev’
  *   Reminder: Qt 6.8 platform and module freeze will be in effect 17th of May 
and Qt 6.8 Feature Freeze will be in effect Fri 31st of May
Next meeting Tue 14th  May 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:32] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:02:59] <+jaheikki3> time to start qt release team meeting
[17:03:14]  jaheikki3: pong
[17:03:25] <+jaheikki3> on agenda today
[17:03:29] <+jaheikki3> Qt 6.7 status
[17:03:33] <+jaheikki3> Qt 6.8 status
[17:03:43] <+jaheikki3> Any additional item to the agenda?
[17:05:01] <+jaheikki3> Ok, let's start from Qt 6.7 status
[17:05:11] <+jaheikki3> Qt 6.7.1 preparations ongoing
[17:05:28] <+jaheikki3> Release content is frozen, packages created & testing 
started
[17:06:07] <+jaheikki3> unfortunately new, critical regression found: 
QTBUG-125142
[17:07:30] <+jaheikki3> The target is to release Qt 6.7.1 as soon as possible, 
current estimation is tue 14th May but let's see if that's possible because of 
this new regression & public holiday this thu
[17:08:17] <+jaheikki3> that's actually all about 6.7 status at this time. Any 
comments or questions?
[17:10:03] <+jaheikki3> Ok, then quick Qt 6.8 status update
[17:10:24] <+jaheikki3> snapshot from the dev updated to the production
[17:10:58] <+jaheikki3> It doesn't contain new msvc2022 binaries yet. But the 
target is to add those in the snapshot soon
[17:11:45] <+jaheikki3> Target is also update the snapshot reqularly, after 
successful dependency update rounds
[17:12:30]  any trouble getting it running?
[17:12:33] <+jaheikki3> And please remember:  Qt 6.8 platform and module freeze 
will be in effect 17th of May and  Qt 6.8 Feature Freeze will be in effect Fri 
31st of May
[17:12:33]  I haven't seen anything
[17:13:03] <+jaheikki3> thiago: recently there were some issues with BIC tests 
but those were false alarms & test set should be fixed now
[17:13:36] <+jaheikki3> so dependency updates has been OK but qt5.git update 
has failed twice
[17:14:15] <+jaheikki3> that's all about 6.8 status at this time. Any more 
comments or questions?
[17:17:23] <+jaheikki3> It was all at this time so let's end this meeting now & 
have new one Tue 14th May at this same time
[17:17:32] <+jaheikki3> Thanks for your participation, bye!
[17:18:07]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.7' to '6.7.1' done

[Jani Heikkinen via Development]

Hi!



We have branched '6.7.1' from '6.7' now. So from now on all changes targeted to 
Qt 6.7.1 release must have 'Pick-to: 6.7.1' and '6.7' is for Qt 6.7.2. But 
remember, please do not try to add anything nice-to-haves in '6.7.1' anymore; 
we will take in only fixes for release blockers (+ of course documentation and 
example improvements). As usual, staging will be restricted for release team 
only in '6.7.1'. We will monitor changes and stage clear ones in automatically.



The target is to release Qt 6.7.1 at the beginning of May





br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 23.04.2024

[Jani Heikkinen via Development]

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]  jaheikki3: pong
[17:01:31]  jaheikki3: pong
[17:01:40]  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]  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]  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]  bye
[17:14:19]  sounds good
[17:14:22]  bye
[17:14:29]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.8 Feature Freeze is getting closer

[Jani Heikkinen via Development]

Hi all,



Just a kindly reminder: Qt 6.8 Feature freeze will be in effect 31st of May 
2024 and Qt 6.8 platform and module freeze already 17th of May 2024, see 
https://wiki.qt.io/Qt_6.8_Release.



Please inform me about all new modules planned to be released in Qt 6.8; we 
should start adding those in CI & packages now. Also please inform me if 
existing technology preview module will be officially supported etc.



br,

Jani Heikkinen
Release Manager
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 09.04.2024

[Jani Heikkinen via Development]

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]  ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:25]  jaheikki3: pong
[17:00:35]  jaheikki3: pong
[17:01:01]  jaheikki3: pong
[17:01:25]  time to start qt release team meeting
[17:01:34]  on agenda today:
[17:01:39]  Qt 6.7 status
[17:01:42]  QT 6.8 status
[17:01:52]  Any additional item to the agenda?
[17:03:30]  let's start from Qt 6.7 status
[17:03:46]  Qt 6.7.0 was released Tue 2nd of April
[17:04:33]  at least one severe regression already reported: 
https://bugreports.qt.io/browse/QTBUG-123997 (binary break in qtmultimedia)
[17:05:00]  so let's do the Qt 6.7.1 release a bit earlier than 
originally planned
[17:05:17]  agree :)
[17:05:21]  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]  that's actually all about Qt 6.7 status at this time. 
Any comments or questions?
[17:06:30]  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]  wouldn't we usually branch on a Friday and release on a 
Monday?
[17:06:50]  pyqt build failure with 6.7 likely due to 
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7a3fed3f
[17:08:36]  vohi: true. But I am on vacation 17.4 - 21.4 and CI 
maintenance break is 6th May
[17:09:31]  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]  krop: thanks, I'll check this with Ivan
[17:09:58]  ack
[17:10:42]  Then Qt 6.8 status
[17:11:19]  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]  ok
[17:12:16]  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]  a snapshot is already available in the online installer 
but it hasn't been updated lately
[17:12:59]  we will update the snapshot after next successful 
dependency update round in 'dev'
[17:13:39]  that's all about 6.8 status at this time. Any comments 
or questions?
[17:13:43]  how about the change to build with VS2022?
[17:14:42]  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]  I'll discuss with them soon & let's agree that in ML as 
soon as possible
[17:15:40]  I think we need to, because 6.9 is LTS and you'll be 
reticent to change then
[17:15:49]  and if you don't, then you're stuck with 2019
[17:16:00]  true
[17:18:01]  ok, let's end this meeting now and have new one tue 23rd 
of April at this same time.
[17:18:14]  thanks for your participation, bye!
[17:26:44]  thanks, bye!
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Removing Qt 3D from release configuration in dev branch

[Jani Heikkinen via Development]

Some comments  below

> -Original Message-
> From: Development  On Behalf Of Mike
> Krus via Development
> Sent: torstai 4. huhtikuuta 2024 17.14
> To: Tuukka Turunen 
> Cc: Qt Project Development 
> Subject: Re: [Development] Removing Qt 3D from release configuration in dev
> branch
> 
> Hi everyone
> 
> Disclaimer: I'm one of the contributors to Qt3D, and a KDAB employee.
> 
> As mentioned, early discussions have taken place between KDAB and tQtC
> around this issue, although much needs to be clarified as to why, how and when
> this happens.
> 
> As mentioned by Tuukka, Qt3D was introduced in Qt4 timeline, but didn't make 
> it
> into Qt5.
> KDAB invested a lot of time in a complete rewrite of the module (don't think 
> it
> shares anything with the original) and it was made available sometime in the 
> Qt 5
> timeline.  Many contributions have been made since then, including in Qt6 with
> the introduction of an RHI based backend (although to this day this doesn't 
> have
> feature parity with the GL backend due to limitations of RHI).
> 
> But since then things have settled down in the Qt6 branch, no major features 
> have
> been added. KDAB has continued to contribute bug fixes, and small features in
> support of our clients. So development has indeed been very slow.
> 
> So hence came the discussions on retiring Qt3D. KDAB is ok on the principle 
> and
> committed to keep maintaining Qt3D in the same manor.
> 
> But there's a lot of implications.
> 
> So what does "removing qt3d from release configuration" mean for contributors?
> - if CI remains, gerrit continue to check commits right? If so, the version 
> of qt this
> is built against
>   remains controlled by the dependencies.yaml file?
Yes, that's possible and I think that's the idea behind Tuukka's proposal.

> - but I also presume qt5.dev integration will no longer affect qt3d? ie there 
> will no
> automated checked that
>   qt3d continues to build against the rest qt when that changes and the
> dependencies.yaml won't  be
>   updated automatically?
Not necessarily, we can add qt3d in the dependency update round as extra module 
if we want to do so. That way qtd3 would be checked pretty much like it is done 
today. The difference is that it won't block the dependency update round, 
release etc and won't be part of qt release (binary packages, src packages, git 
tags etc)

> - no more automatic branching?
If we want to keep automatic branching we can still enable it.

> - so how does versioning work? Would it be up to maintainer to decide when to
> do branches, tags, releases?
If we remove qt3d from release configuration we don't add tags or include it in 
the release packages. If maintainer wants to "release" new version from qt3d I 
think it is possible but it shouldn't follow qt releasing schema etc. But what 
release means in this context? Git tag? src packages somewhere? From the 
releasing point of view I would not like to see that we remove qt3d from the 
official release configurations but then start releasing qt3d as its own 
release; it would just increase our workload...


>   And what would be a good strategy for that?
> - module life cycle in general needs to be defined.
> 
> And what does "removing qt3d from release configuration" mean for
> users/developers?
> - no longer in the installer, or tarballs?
True

> - probably no longer in linux distributions?
> - do ABI/API compatibility rules still apply?
> - for new projects, no more C++ 3D scene graph API, and no more LGPL licensed
> module to do 3d.
>   At least not bundled with Qt?
> - only way to get the code would be to check it out and build it?
I think this is the way to go.

br,
Jani


> - given qt3d is a proper qt module (as opposed to a simple library), 
> including qml
> (and it's own) plugins, and
>   that it was up to now installed along the rest of Qt, how much work will it 
> be for
> existing users to change
>   their build to continue getting new versions of Qt3D?
> - and finally, how do we warn users of the upcoming change?
> 
> 
> While I have no problems with the aim of this, we need to figure out the
> important details first before
> pulling the trigger.
> 
> 
> 
> Mike
> 
> 
> > On 27 Mar 2024, at 08:39, Tuukka Turunen  wrote:
> >
> > Hi,
> >  We have been discussing with KDAB about the future maintenance of Qt 3D
> module. It is a quite large and complex module, which has for most use cases 
> by
> now been superseded by Qt Quick 3D. Since Qt 3D has been available for a long
> time, it should continue to be available for those who still need it. It is 
> also part of
> all currently supported releases, which would continue to have it in upcoming
> patch level releases.
> >  After discussing with KDAB (maintainer of Qt 3D) on how to proceed, we came
> up with the following and also agreed that I'll summarize it for the Qt 
> project
> development list:
> > * Qt 3D module is removed from official release configuration in the dev
> branch, i.e. no lo

Re: [Development] Qt 6.7.0 RC2

[Jani Heikkinen via Development]

> -Original Message-
> From: Ilya Fedin 
> Sent: lauantai 23. maaliskuuta 2024 1.16
> To: development@qt-project.org
> Cc: Jani Heikkinen 
> Subject: Re: [Development] Qt 6.7.0 RC2
> 
> I'm unable to find the tag for RC2...
> 

Tag should be now in place, please try again

br,
Jani
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Qt 6.7.0 RC2

[Jani Heikkinen via Development]

Hi all!

Qt 6.7.0 RC2 is available via online installer. Src packages are also available 
in the Qt Account and download.qt.io. Delta to the first rc attached.

The target is to release Qt 6.7.0 final release immediately after the Easter, 
Tue 2nd of April 2024.

br,
Jani Heikkinen
Release Manager

qt5.git
qt3d:
qt5compat:
qtactiveqt:
qtbase:
63d6012b03e5c85000d52ce735c848dd814cf1de Condition inline fromString() 
definitions on datestring feature
dbda7d2f8b68b32ff580fc386ad32d0cad459dbd wasm: Dont access QNetworkReply header 
data through dangling pointer
9888d8ee2272139c2d7d3088c7ada148661bc338 SQLite: Update SQLite to v3.45.2
d86a93ba21342997f54f8ff2d7b14e5e42ac3ce3 Schannel: fix handling of empty 
ciphers list
b45d7cc24cf85bcb4225db57a5282e1b9427cc35 Revert "QTextEngine: Protect against 
integer overflow with huge texts"
cfcfe7d07b03c0154c01c0c172d8fcc120080edc Revert "Windeployqt: remove unused 
library list"
9d791aabad5c7885aec9ec31779c37be14572aa6 Update bundled libpng to version 1.6.43
0df3ff3d7067c5a57e51a49303f5558b48d348de QProcess/Unix: fix close() on invalid 
file descriptor
9057431efb886990cf633bbb304d18a1d624fe0e Android: don't add lib prefix to 
loaded libs unconditionally
c7cddc92ffc57b509c03bf4fbbf3cd08ab01eb54 QTest::qWaitFor(., int): restore lost 
Qt::PreciseTimer'ness
494aa933342ec894dc4d1fd533945c6ff41df919 Android: Do Thread.sleep before 
loading Qt libraries in Debug Mode
e12a87c2334862ed881d7b7d725f318428051f24 Correct license for tools files
1fd0dcfd8efc1421eb6bb9b83958da475383ff28 Change license for .in files
d87d4eb6b12eb9b1e7cc42874849da1e41eaf042 Bump Android platform version in 
documentation to 34
f32abfdc78ca0be1374d3e301afba5d98956a487 Android: Add Thread.sleep before 
loading main in Debug mode
b444ae399684f7f6b1be5b772c73bfe0c8479efc QProcess/Unix: fix improper 
restoration of signal mask and cancel state
026aecf47c9aa5605054857ab3882ed0020c4ac6 QCborStreamReader: rename 
toStringish() -> readAllStringish()
c9556213ac5c7f108c8838e9b12337d67db3437d QCborStreamReader: rename 
appendToType() -> readAndAppendToType()
qtcharts:
qtcoap:
qtconnectivity:
qtdatavis3d:
qtdeclarative:
81dfaa0fcb06b2667b248d5f9137b9e636a3576a Update Controls Text Editor example 
and docs
2d69be1b1234abddafce77cc5698a4a7e8751134 Handle more potential underlying types
eb0a3811f34e20eb53c3c13c34d1245b0f6c858c Android: Fix missing qqmlengine.h 
include
54abc984dcc9fb8243a04a6e0b9697ad568ffbe9 Fix enum class lookup on Singletons
3e45909f00d4982aa9acfdca52ecd7fff079fa76 fix crash in qquickspinbox.cpp
6b1f8d471664ea20d6be0b0ac66de17acd996a05 Android: Add documentation for 
QtQuickView class
6b8bf79a5ef70d72ffa349fae1dafb5149f7f1f4 Keep markup when toggling 
TextEdit.format: AutoText / PlainText
d5faecd1d85325366bb4a54c5f4fd3dd2d4e5857 Android: Add docs to QtQuickView class
qtdoc:
3cf2598574f015b8c4412bf4ab3112705d302138 Fix broken links in WebEngine what's 
new 6.7
44995d84bd56309b08c7749b94e2ed0cdca934c9 Document third-Party code changes in 
Qt 6.7.0 (and 6.6.3)
4af9387fae67317348d716d4e8a1e09702eb3e04 Update supported Qt versions 
documentation
e215c0c64a90f559c05024eb7465d9973ac029a9 OSM buildings: correctly download and 
add OpenSSL libraries
255725ebbbe1508839b256f7c4f7891f7222f99f Docs: Update Qt Dice example 
documentation
qtgraphs:
qtgrpc:
344f7fe150b0904b122c59b8d3a430b364b82b0f QtProtobuf: add escaping for Qt C++ 
keywords
446cde4b1244661a9cbbafd901f3cf9fc23a132c Add the missing END_STREAM flag to the 
single-request operations
qthttpserver:
qtimageformats:
qtlanguageserver:
qtlocation:
3c3f2e3f1bc969f1d2882807f67f08dffe4e292b Fix GeoJson Viewer example Android 
deployment
qtlottie:
qtmqtt:
qtmultimedia:
daa0ab209afbc7c444b954d86b2567b56dc73c0c Update 
src/3rdparty/ffmpeg/qt_attribution.json
6a1cf1d5718835a71ace23ca1b50a93f882375b0 GStreamer: output - only use 
`videoconvertscale` when available
qtnetworkauth:
qtopcua:
qtpositioning:
qtquick3d:
593f742be96b694085f39cd921570b89bf857f1f Doc: Move examples to '3D' category
qtquick3dphysics:
qtquickeffectmaker:
qtquicktimeline:
qtremoteobjects:
qtscxml:
qtsensors:
qtserialbus:
qtserialport:
qtshadertools:
qtsvg:
88435cab65bc0db797678fe19d04dcb6a2efc8aa Propagate states correctly in 
 element
45c72ec0639ee7a706d72c95bf3c90c6ce16a5d2 Enable  elements in  and 
propagate state to mask children
qtspeech:
qttools:
655223f8dbfcd16fb04fa9c7a1d9ba8fb3d0 CMake: Fix 'file to open is a 
directory' on update_translations
0b6536bcb56f4092a20422cee24859b6513788fe QDoc: Adapt clang/AST/QualTypeNames.h 
to upstream change
qttranslations:
qtvirtualkeyboard:
qtwayland:
qtwebchannel:
qtwebengine:
64fda53830f47f0deb01f890c83ccb3488bcfac7 Fix flaky horizontalScrollbarTest
1345e33eb56a92f81b218f3db275d0565125f3b9 Update Chromium
23a26550cf044929f24a512427a0aee462ec0a1a Clean up GLX code
941ac35c0b35760bd6793f74285f2776f765b252 Update Chromium
qtwebsockets:
qtwebview:
-- 
Development mailing list
Dev

[Development] Meeting minutes from Qt Release Team meeting 12.03.2024

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.3 preparations started
 *   Branching from '6.6' to '6.6.3' done
 *   The target is to release Qt 6.6.3 Fri 22rd March 2024
Qt 6.7 status:

  *   Qt 6.7.0 RC content frozen and packages available in the production
 *   Release announcements will be sent later today, after production tests 
are finalized.
  *   The target is to release Qt 6.7.0 Tue 26th March 2024
 *   Release blocker list here: 
https://bugreports.qt.io/issues/?filter=25675
Next meeting Tue 19th March 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:01:06] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:01:29]  jaheikki3: pong
[17:01:31]  jaheikki3: pong
[17:02:02]  jaheikki3: pong
[17:02:40] <+jaheikki3> Time to start qt release team meeting
[17:02:48] <+jaheikki3> On agenda today:
[17:02:51] <+jaheikki3> Qt 6.6 status
[17:03:00] <+jaheikki3> Qt 6.7 status
[17:03:12] <+jaheikki3> Any additional item to the agenda?
[17:04:19] <+jaheikki3> Let's start from Qt 6.6 status
[17:04:42] <+jaheikki3> Qt 6.6.3 preparations started
[17:05:10] <+jaheikki3> Branching from '6.6' to '6.6.3' is done and first 
dependency update round in '6.6.3' succeed
[17:05:36] <+jaheikki3> Plan is to create first snapshot for RTA later this week
[17:05:46] <+jaheikki3> And the target is to release Qt 6.6.3 Fri 22rd March 
2024
[17:06:11] <+jaheikki3> And like said earlier it will be the last release from 
the Qt 6.6 series
[17:06:33] <+jaheikki3> That's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:08:07] <+jaheikki3> Ok, then Qt 6.7 status:
[17:08:40] <+jaheikki3> Qt 6.7.0 RC content frozen, packages created and 
release available in the production
[17:09:12] <+jaheikki3> Release announcements will be sent later today (or 
tomorrow morning), after production tests are fully done
[17:09:41] <+jaheikki3> The target is to release Qt 6.7.0 Tue 26th March 2024, 
2 weeks after the RC (as planned)
[17:10:41] <+jaheikki3> Blocker list for final release here: 
https://bugreports.qt.io/issues/?filter=25675
[17:11:00] <+jaheikki3> That's all about 6.7 status at this time. Any comments 
or questions?
[17:11:14]  rc1 is definitely not acceptable
[17:11:24]  the fix for QProcess has gone in the last 12 hours
[17:11:46]  it's still going through 6.7 right now
[17:11:52]  cp to 6.7.0 still pending
[17:13:02] <+jaheikki3> thiago: that's true. We had a discussion about that 
with vohi & tuukka and we agreed that we won't block rc anymore because of that
[17:13:55]  the other fix for QProcess (staged for dev now) fixes 
QProcess::startDetached
[17:14:04]  it's a silent corruption otherwise
[17:14:08]  P1 level at least
[17:14:15] <+jaheikki3> We can publish RC2 between RC and final if needed but 
we really needed to proceed with the RC to be able to get it out for testing & 
be able to get final out before Easter
[17:15:56] <+jaheikki3> thiago: what are the changes you are referring? I might 
mix those to those API review related ones...
[17:16:21]  https://codereview.qt-project.org/c/qt/qtbase/+/546770 and 
https://codereview.qt-project.org/c/qt/qtbase/+/546895
[17:18:04] <+jaheikki3> Ok, we can take those in between RC and final release. 
I'll make sure those will be staged in 6.7.0 immediately when landed there
[17:19:04] <+jaheikki3> Is there some other comments or questions related to Qt 
6.7.0 still?
[17:21:27] <+jaheikki3> Ok, then it was all at this time so let's end this 
meeting now & have new one Tue 19th March at this same time
[17:21:41] <+jaheikki3> Thanks for your participation, bye!
[17:24:42]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.6' to '6.6.3' done

[Jani Heikkinen via Development]

Hi!

We have branched '6.6.3' from '6.6'. So from now on all changes targeted to Qt 
6.6.3 release must have 'Pick-to: 6.6.3'

Staging in '6.6.3' is restricted to release team only and we will monitor 
incoming changes and stage the clear ones automatically. And as usual, please 
do not add any nice-to-haves in '6.6.3' anymore.

The target is to release Qt 6.6.3 Fri 22nd March 2024 and it will be the last 
release from Qt 6.6 series.

br,
Jani Heikkinen
Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.7' to '6.7.0' done

[Jani Heikkinen via Development]

Hi!



We have branched '6.7.0' from '6.7' now. So from now on all changes targeted to 
Qt 6.7.0 release must have 'Pick-to: 6.7.0' and '6.7' is for Qt 6.7.1. But 
remember, please do not try to add anything nice-to-haves in '6.7.0' anymore; 
we will take in only fixes for release blockers (+ of course documentation and 
example improvements). As usual, staging will be restricted for release team 
only in '6.7.0'. We will monitor changes and stage clear ones in automatically.



Target is to release Qt 6.7.0 RC at the beginning of next week and Qt 6.7.0 
final release at the end of March. Qt 6.7.0 release blocker list here: 
https://bugreports.qt.io/issues/?filter=25675. Please make sure all release 
blockers are visible in the blocker list and are fixed immediately. We're 
already late, so let's make sure we're not late any more...



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 27.02.2024

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.3 preparations started
 *   The target is to branch from ‘6.6’ to ‘6.6.3’ Mon 11th March
 *   The target is to release Qt 6.6.3 Fri 22rd March 2024
*   Qt 6.6.3 will be the last release from Qt 6.6 series


Qt 6.7 status:

  *   Qt 6.7 API review still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
à Most probably branching from ‘6.7’ to ‘6.7.0’ will be delayed; we need to 
complete the review before branching

  *   Initial plan was to release Qt 6.7.0 RC Tue 5th March 2024
 *   Hoping we can freeze the RC content asap so that we could get RC out 
during next week
 *   Release blocker list here: 
https://bugreports.qt.io/issues/?filter=25675
*   We will improve the documentation about how to create a ticket that 
ends up on the blocker list.
Next meeting Tue 12th March 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:35] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:48]  jaheikki3: pong
[17:01:11]  pong
[17:01:56]  jaheikki3: pong
[17:02:30] <+jaheikki3> Time to start qt release team meeting. On agenda today:
[17:02:38] <+jaheikki3> Qt 6.6 status
[17:02:43] <+jaheikki3> Qt 6.7 status
[17:02:52] <+jaheikki3> Any additional item to the agenda?
[17:04:01]  Can we check if the definition of the list of blockers (as 
per JIRA query) makes sense?
[17:04:34] <+jaheikki3> vohi: sure, let's take that as a part of 6.7 status
[17:04:43]  👍
[17:04:48] <+jaheikki3> But let's start from 6.6
[17:05:08] <+jaheikki3> Qt 6.6.3 preparations started.
[17:05:31] <+jaheikki3> Target is to branch from ‘6.6’ to ‘6.6.3’ at the 
beginning of next week
[17:05:45] <+jaheikki3> And the target is to release Qt 6.6.3 Fri 15th March 
2024
[17:06:13] <+jaheikki3> And 6.6.3 will be the last release from Qt 6.6.3 series
[17:06:37] <+jaheikki3> That's actually all about 6.6 status at this time. Any 
comments or questions?
[17:07:02]  last week the target was to release 6.6.3 by end of March; 
what has changed that we need to speed that up by two weeks?
[17:07:50]  6.6.2 is only two weeks old at this point
[17:08:35] <+jaheikki3> vohi: actually nothing has changed. Usually we have 
done the last release before the first new one and QT 6.7.0 is planned to 
happen 19th March
[17:09:53] <+jaheikki3> But we can also do the last Qt 6.6 release after Qt 
6.7.0, I don't think it isn't a problem at all
[17:10:21] <+jaheikki3> And actually that would fit to my schedule a bit better 
as well :D
[17:12:13]  a later 6.6.3, together with (or right after) 6.7.0 makes 
sense tome
[17:12:15]  a later 6.6.3, together with (or right after) 6.7.0 makes 
sense to me
[17:13:59] <+jaheikki3> Agree. So let's do the branching from '6.6' to '6.6.3' 
Mon 11th March. That way we should be able to get Qt 6.6.3 out right after Qt 
6.7.0
[17:14:57] <+jaheikki3> And then Qt 6.7 status
[17:15:15] <+jaheikki3> Qt 6.7 API review still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:16:16] <+jaheikki3> Unfortunately it most probably means that branching 
from ‘6.7’ to ‘6.7.0’ will be delayed a bit; we need to complete the review (or 
at least have all fixes in) before branching
[17:16:55] <+jaheikki3> Initial plan was to release Qt 6.7.0 RC Tue 5th March 
2024 but it might be too tight, let's see
[17:17:11] <+jaheikki3> Hoping we can freeze the RC content asap so that we 
could get RC out during next week
[17:17:26] <+jaheikki3> Release blocker list here: 
https://bugreports.qt.io/issues/?filter=25675
[17:17:50] <+jaheikki3> vohi: what was in your mind related to blocker list?
[17:18:43]  two things: a) other than the actual filter I'm not aware of 
any documentation that describes what it takes to make an issue a release 
blocker
[17:18:56]  and b) the filter itself, e.g. for 6.7 that would be 
https://bugreports.qt.io/issues/?filter=25675
[17:20:03]  the filter right now captures all P1 issues with "fixVersion" 
set to a 6.7.0* version, and all P0 issues that affect a 6.7* version. I wonder 
about the inconsistency.
[17:20:32]  I.e. why would a P0 issue that has fixVersion set to 6.7.0* 
not be a release blocker?
[17:21:18] <+jaheikki3> vohi: It is true that it's not documented so well
[17:21:22]  or why would a P1 that affects "6.7.0 RC" not be a blocker?
[17:21:52]  so I think we can perhaps make it a bit more intuitive and 
less likely for something that should be a blocker to fall through the cracks 
just because someone doesn't pick the exact right combination of field values
[17:23:34] <+jaheikki3> But not sure what you mean, P0 issue (affecting to some 
6.7 release) will be in 6.7.0 blocker list, all P0 issues affecting to that 
release are in the list
[17:25:05] &

Re: [Development] HEADS-UP: Qt 6.7 API change review

[Jani Heikkinen via Development]

Hi all,

API review for Qt 6.7 is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952

Especially qtbase has many documents open, but there are also open ones in 
qtdeclarative, qtquick3d, qtsensors and qtwebengine.

Please help us to complete the review; we need to do it immediately to be able 
to keep the Qt 6.7.0 release schedule

br,
Jani

From: Development  On Behalf Of Jani 
Heikkinen via Development
Sent: perjantai 5. tammikuuta 2024 7.50
To: development@qt-project.org
Subject: [Development] HEADS-UP: Qt 6.7 API change review


Hi!



Qt 6.7 API Change Review is finally started, see 
https://bugreports.qt.io/browse/QTBUG-119952

generated diffs are here:

  *   https://codereview.qt-project.org/q/topic:api-change-review-6.7
  *   https://codereview.qt-project.org/q/topic:qml_api_review_6.7



Please review the diffs as soon as possible.



br,

Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Decrease amount of qt releases in online installer

[Jani Heikkinen via Development]

> -Original Message-
> From: Ville Voutilainen 
> Sent: torstai 22. helmikuuta 2024 17.53
> To: Jani Heikkinen 
> Cc: Giuseppe D'Angelo ; development@qt-
> project.org
> Subject: Re: [Development] Decrease amount of qt releases in online installer
> 
> So yeah, overall, I'd like us to investigate the possibilities of providing 
> filtered
> views that can be multi-step-expanded to show more of the available options,
> rather than just outright removing the older releases as a choice.

yeah, this installation problem can be worked around (as I wrote, it's much 
better today than before), but the mirroring problem is bigger and much harder 
to solve...
- Jani
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Decrease amount of qt releases in online installer

[Jani Heikkinen via Development]

> -Original Message-
> From: Development  On Behalf Of
> Giuseppe D'Angelo via Development
> Sent: keskiviikko 21. helmikuuta 2024 13.21
> To: development@qt-project.org
> Subject: Re: [Development] Decrease amount of qt releases in online installer
> 
> Hello,
> 
> On 21/02/2024 11:42, Jani Heikkinen via Development wrote:
> > Currently, more than 60 Qt releases can be installed from the Qt open
> > source online installer (if all installation categories are selected).
> > This requires a huge amount of disk space on the mirrors and also
> > causes some performance issues with the online installer.
> 
> What kind of performance issues are we talking about?

It takes quite a time to show all releases when you select  'archive'  
category. With latest online installer this is already much better than earlier 
but it still takes some time and it's a bit annoying... 

> 
> > That's why I suggest
> > removing the older ones from the online installer; these releases can
> > still be found in the archive as source packages and offline installers.
> >
> > But what are the ones that can be removed? I suggest removing all Qt 5
> > except Qt 5.15.x. And maybe we could also remove the oldest Qt6s, e.g.
> > all Qt 6.0.x, 6.1.x?
> >
> > Any objections or other opinions?
> >
> 
> Do you have data on how what's the share of downloads per Qt version / OS?
> Maybe those can be mirrored less aggressively?

I don't have that kind of data in my hands now but it isn't that easy to choose 
mirroring strategy based on the release; releases aren't in one folder in 
online installer and so on it would be quite hard for mirrors to define which 
repos (==folders) should not be mirrored.

- Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Decrease amount of qt releases in online installer

[Jani Heikkinen via Development]

Hi,

Currently, more than 60 Qt releases can be installed from the Qt open source 
online installer (if all installation categories are selected). This requires a 
huge amount of disk space on the mirrors and also causes some performance 
issues with the online installer. That's why I suggest removing the older ones 
from the online installer; these releases can still be found in the archive as 
source packages and offline installers.

But what are the ones that can be removed? I suggest removing all Qt 5 except 
Qt 5.15.x. And maybe we could also remove the oldest Qt6s, e.g. all Qt 6.0.x, 
6.1.x?

Any objections or other opinions?

br,
Jani
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 20.02.2024

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.2 is released
  *   The target is to release Qt 6.6.3 by the end of March.
 *   Qt 6.6.3 will be the last release from Qt 6.6 series

Qt 6.7 status:

  *   Qt 6.7.0 Beta3 is released.
  *   Updating 3rd party modules for Qt 6.7.0 done
  *   API review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
 *   We should complete the review by the end of this week
  *   Branching from '6.7' to '6.7.0' will happen sometime next week
 *   API review related changes needs to be in before branching( to make 
sure all will be in Qt 6.7.0).
  *   The target is to release Qt 6.7.0 RC Tue 5th March & Qt 6.7.0 final Tue 
19th March
 *   Release blocker list here: 
https://bugreports.qt.io/issues/?filter=25675

Qt 6.8 initial schedule:

  *   Proposal sent to ML 
(https://lists.qt-project.org/pipermail/development/2024-February/044983.html), 
no objections
  *   Initial schedule for Qt 6.8.0 is:
 *   Platform and Module freeze: 17.5.2024
 *   Qt 6.8 Feature freeze: 31.5.2024
 *   Qt 6.8.0 Beta1: 13.6.2024
 *   Qt 6.8.0 RC: 11.9.2024
 *   Qt 6.8.0 Final release: 25.9.2024
Next meeting Tue 27th February 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:11] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:02:15] <+jaheikki3> Time to start qt release team meeting
[17:02:21]  jaheikki3: pong
[17:02:24] <+jaheikki3> On agenda today:
[17:02:36]  jaheikki3: pong
[17:02:39] <+jaheikki3> - Qt 6.6 status
[17:02:45] <+jaheikki3> -Qt 6.7 status
[17:02:56] <+jaheikki3> - Qt 6.8 initial schedule
[17:03:09] <+jaheikki3> - Dropping old Qt releases from online installer
[17:03:19] <+jaheikki3> Any additional item to the agenda?
[17:05:05] <+jaheikki3> Let's start from Qt 6.6 status:
[17:05:23] <+jaheikki3> Qt 6.6.2 is released
[17:05:37] <+jaheikki3> Target is to release Qt 6.6.3 by the end of March
[17:05:53] <+jaheikki3> And Qt 6.6.3 will be the last release from Qt 6.6 series
[17:06:12] <+jaheikki3> That's all about Qt 6.6 status. Any comments or 
questions?
[17:07:43] <+jaheikki3> Ok, then Qt 6.7 status
[17:08:17] <+jaheikki3> Qt 6.7.0 Beta3 released last friday
[17:08:38] <+jaheikki3> Updating 3rd party modules for Qt 6.7.0 done
[17:08:54] <+jaheikki3> API review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:09:20] <+jaheikki3> We should complete the review by the end of this week
[17:10:02] <+jaheikki3> Branching from '6.7' to '6.7.0' will happen during next 
week & API review related changes needs to be in before branching to be sure 
all will be in Qt 6.7.0
[17:10:16]  yay
[17:10:31] <+jaheikki3> The target is to release Qt 6.7.0 RC tue 5th March
[17:10:55] <+jaheikki3> And the target for Qt 6.7.0 final is Tue 19th March
[17:11:07] <+jaheikki3> Release blocker list here: 
https://bugreports.qt.io/issues/?filter=25675
[17:11:33] <+jaheikki3> That's all about Qt 6.7 status at this time. Any 
comments or questions?
[17:13:18] <+jaheikki3> ok, then Qt 6.8 initial schedule:
[17:13:41] <+jaheikki3> Proposal sent to ML 
(https://lists.qt-project.org/pipermail/development/2024-February/044983.html), 
no objections
[17:14:11] <+jaheikki3> So the initial schedule for Qt 6.8 is:
[17:14:19] <+jaheikki3> Platform and Module freeze: 17.5.2024
[17:14:28] <+jaheikki3> Qt 6.8 Feature freeze: 31.5.2024
[17:14:36] <+jaheikki3> Qt 6.8.0 Beta1: 13.6.2024
[17:14:44] <+jaheikki3> Qt 6.8.0 RC: 11.9.2024
[17:14:56] <+jaheikki3> and Qt 6.8.0 Final release: 25.9.2024
[17:15:09] <+jaheikki3> Any comments or questions?
[17:15:37]  the usual that it's a long time but we've had this 
discussion before
[17:15:50] <+jaheikki3> Yeah...
[17:16:20] <+jaheikki3> Ok, then Dropping old Qt releases from online installer:
[17:16:40] <+jaheikki3> At the moment all releases since Qt 5.9.0 are available 
in the online installer so more than 60 releases!
[17:17:10] <+jaheikki3> This is causing issues with mirrors (huge amount of 
data needs to be mirrored) & online installer (huge amount of install scripts 
needs to be evaluated) as well
[17:17:30] <+jaheikki3> So I am proposing to drop some releases from online 
installer
[17:18:07] <+jaheikki3> And I propose we will drop releases at least older than 
Qt 5.15.0 from the online installer; older releases are available in archive as 
src packages and offline installers
[17:18:31]  we probably need to discuss on the ML, but I'd suggestion 
5.15 and the last 3 stables
[17:19:35] <+jaheikki3> thiago: Yeah, sounds good. I'll initiate discussion and 
propose that. Let's see what others thinks
[17:21:00] <+jaheikki3> It was all at this time so let's end this meeting now & 
have new one Tue 27th February at this same time
[17:21:08] <+jaheikki3> Thanks for participation, bye!
[17:21:27]  bye
[17:22:03]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Qt 6.8.0 initial schedule

[Jani Heikkinen via Development]

Hi!

It is time to agree initial schedule for Qt 6.8.0.

This is my proposal:


  *   Platform and Module freeze: 17.5.2024
  *   Feature freeze: 31.5.2024
  *   Beta1: 13.6.2024
  *   RC: 11.9.2024
  *   Final release: 25.9.2024

Any comments? As usual it follows Qt 6.5.0 initial schedule...

br,
Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS UP : Qt 6.7 string freeze

[Jani Heikkinen via Development]

Hi all,



String freeze for Qt 6.7 is in effect now.



br,

Jani


From: Jani Heikkinen
Sent: tiistai 6. helmikuuta 2024 14.51
To: localizat...@qt-project.org; development@qt-project.org; 
releas...@qt-project.org
Subject: HEADS UP : Qt 6.7 soft string freeze


Hi all,

First beta releases from Qt 6.7 are out and it is time to start keeping 
translatable strings as it is. The official string freeze for Qt 6.7 will be in 
effect Tue 13th of February 2024.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Let's drop MSVC 2019 for dev (6.8)

[Jani Heikkinen via Development]

Hi!

I wouldn't once again duplicate these msvc binary packages if that isn't really 
mandatory; we already have so many packages and more is coming all the time so 
something has to be dropped as well. msvc2022 is quite old already so I would 
just replace msvc2019 with msvc2022 from Qt 6.8 ->

br,
Jani

From: Development  On Behalf Of Vladimir 
Minenko via Development
Sent: perjantai 9. helmikuuta 2024 11.59
To: development@qt-project.org
Subject: Re: [Development] Let's drop MSVC 2019 for dev (6.8)

Hi,

I also think we should first get the 2022 compiler packages available for 
installation in parallel to the 2019 ones. This should be available for users 
for a while so that they have a transition period. Along with this, we should 
announce that the 2019 compiler will be dismissed by a specific date.

As we introduce Linux on ARM desktops and later Windows on ARM desktops, this 
can only be done IMHO after work on the release of 6.7 is finished, meaning in 
some of the 6.7.x slots.

Considering removal of MSVC 2019 in "Supported Configurations" in 
https://doc.qt.io/qt-6/windows.html should come after we provide a transition 
solution, IMHO

I fully appreciate the enthusiasm for using new capabilities in the newer 
compiler, but we should not forget the fact there are more users preferring the 
predictability of changes, and none like surprises with these topics.

--
Vladimir



On 6. Feb 2024, at 08:28, Allan Sandfeld Jensen 
mailto:k...@carewolf.com>> wrote:

On Tuesday, 6 February 2024 06:57:34 CET Jani Heikkinen via Development wrote:

How about instead we drop at an LTS+2 release? The next one is actually
6.7.
We can't switch this in 6.7 at this point anymore; we don't have packages
for MSVC2022 at the moment and doing this (adding new packages + removing
ones) change this late of process is too risky
Could you please switch packaging to msvc2022 in dev then, so we don\t have
this discussion and excuse yet again in 6 months?

Br
Allan



--
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
https://lists.qt-project.org/listinfo/development

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 06.02.2024

[Jani Heikkinen via Development]

Qt 6.6 status

  *   Qt 6.6.2 release content was frozen but new blocker was found
 *   Fixing ongoing, the target is to re-freeze the release content later 
this week.
  *   The target is to release Qt 6.6.2 as soon as possible. Most probably this 
will happen at the beginning of next week.

Qt 6.7 status:

  *   Qt 6.7.0 Beta2 released and Qt 6.7.0 Beta3 preparations started. The 
target is to release Qt 6.7.0 Beta3 by the end of next week
  *   API review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
  *   Updating 3rd party components for Qt 6.7.0 mostly done, see 
https://bugreports.qt.io/browse/QTBUG-121323
  *   Qt 6.7.0 Soft string freeze announced. Official String Freeze for Qt 
6.7.0 will be in effect Tue 13th February 2024
Next meeting Tue 13th February 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:03] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:02:11]  pong
[17:02:26]  jaheikki3: pong
[17:02:28] <+jaheikki3> Let's start from Qt 6.6 status
[17:02:47] <+jaheikki3> t 6.6.2 release content was frozen but new blocker was 
found
[17:03:13] <+jaheikki3> Fixing ongoing, the target is to re-freeze the release 
content later this week
[17:03:22]  jaheikki3: pong
[17:03:50] <+jaheikki3> And the target is to release Qt 6.6.2 as soon as 
possible
[17:04:13] <+jaheikki3> But because packages aren't in place the release won't 
happen during this week
[17:04:31] <+jaheikki3> Hoping the release can happen at the beginning of next 
week
[17:04:50] <+jaheikki3> That's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:06:08] <+jaheikki3> Ok, next Qt 6.7 status
[17:06:20] <+jaheikki3> Qt 6.7.0 Beta2 released last week
[17:06:42] <+jaheikki3> And Qt 6.7.0 Beta3 preparations started. The target is 
to release Qt 6.7.0 Beta3 by the end of next week
[17:06:59] <+jaheikki3> API review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:07:40] <+jaheikki3> Some reviews still open but it seems reviews are 
progressing
[17:07:59] <+jaheikki3> Updating 3rd party components for Qt 6.7.0 mostly done, 
see https://bugreports.qt.io/browse/QTBUG-121323
[17:08:34] <+jaheikki3> Qt 6.7.0 Soft string freeze announced, official String 
Freeze will be in effect Tue 13th February 2024
[17:09:04] <+jaheikki3> That's actually all about Qt 6.7 status at this time. 
Any comments or questions?
[17:09:32]  we had a question whether the qHash(quint128) code could be 
added to it
[17:09:44]  it was found byy API review in 6.6 but the implementation 
wasn't done until a few days ago
[17:10:02]  hmm... volker isn't here to opine
[17:11:04] <+jaheikki3> Yeah, vohi is in workshop so let's discuss about that 
in ml
[17:11:56]  ok
[17:12:48] <+jaheikki3> ok, it was all at this time so let's end this meeting 
now & have new one tue 13th February at this same time
[17:12:57] <+jaheikki3> thanks for your participation, bye!
[17:13:11]  bye
[17:13:46]  bye
[17:14:46]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS UP : Qt 6.7 soft string freeze

[Jani Heikkinen via Development]

Hi all,

First beta releases from Qt 6.7 are out and it is time to start keeping 
translatable strings as it is. The official string freeze for Qt 6.7 will be in 
effect Tue 13th of February 2024.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Let's drop MSVC 2019 for dev (6.8)

[Jani Heikkinen via Development]

> 
> How about instead we drop at an LTS+2 release? The next one is actually 6.7.
> 

We can't switch this in 6.7 at this point anymore; we don't have packages for 
MSVC2022 at the moment and doing this (adding new packages + removing ones) 
change this late of process is too risky

br,
Jani


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 30.01.2024

[Jani Heikkinen via Development]

Qt 6.6 status

  *   Qt 6.6.2 release content isn't frozen yet but the target is to freeze the 
release content later this week
  *   New target for Qt 6.6.2 release is Wed 7th February 2024
  *   Current plan is to have Qt 6.6.3 ~mid march

Qt 6.7 status:

  *   Dependency round in '6.7' finally succeed & beta2 packages are under 
testing
  *   Qt 6.7.0 Beta2 will be released Wed 31st of January 2024
  *   New target for Qt 6.7.0 Beta3 is Tue 13th of February
  *   API review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
Next meeting Tue 6th February 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[16:59:45] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:09]  jaheikki3: pong
[17:00:32]  jaheikki3: pong
[17:00:58]  pong
[17:01:15] <+jaheikki3> time to start qt release team meeting
[17:01:21] <+jaheikki3> on agenda today:
[17:01:28] <+jaheikki3> qt 6.6 status
[17:01:34] <+jaheikki3> qt 6.7 status
[17:01:42] <+jaheikki3> Any additional item to the agenda?
[17:03:31] <+jaheikki3> Let's start from Qt 6.6 status
[17:03:57] <+jaheikki3> Qt 6.6.2 release content isn't frozen yet
[17:04:19] <+jaheikki3> There is still couple of regression fixes missing
[17:04:31] <+jaheikki3> the target is to freeze the release content later this 
week
[17:04:49] <+jaheikki3> And new target for Qt 6.6.2 release is Wed 7th February 
2024
[17:05:22] <+jaheikki3> That's all about qt 6.6 status at this time. Any 
comments or quesations?
[17:06:41]  current plan is to have a 6.6.3 at around the same time as 
6.7, right?
[17:07:04] <+jaheikki3> Yes, that's the plan
[17:08:28] <+jaheikki3> Ok, then Qt 6.7 status
[17:08:46] <+jaheikki3> Dependency round in '6.7' finally succeed & beta2 
packages are under testing
[17:09:33] <+jaheikki3> Qt 6.7.0 Beta2 will be officially released tomorrow, 
after testing is completed
[17:09:50] <+jaheikki3> New target for Qt 6.7.0 Beta3 is Tue 13th of February
[17:10:08] <+jaheikki3> And API review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:10:25] <+jaheikki3> Please help to complete the reviews as soon as possible
[17:10:40] <+jaheikki3> that's all about 6.7 status. Any comments or questions?
[17:12:52] <+jaheikki3> ok, it was all at this time so let's end meeting now & 
have new one Tue 6th of February at this same time
[17:13:05] <+jaheikki3> thanks for your participation, bye!
[17:13:08]  thanks, bye!
[17:13:21]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 23.01.2024

[Jani Heikkinen via Development]

Qt 6.6 status

  *   Branching from '6.6' to '6.6.2' done
  *   The target is to freeze the Qt 6.6.2 release content latest by the end of 
this week
  *   The target is to release Qt 6.6.2 by the end of January


Qt 6.7 status:

  *   All known issues from '6.7' dependency update round fixed and new 
dependency update round ongoing
  *   The target is still to release Qt 6.7.0 Beta2 soon after next successful 
dependency update round in '6.7'
  *   API review is ongoing &  proceeding, see 
https://bugreports.qt.io/browse/QTBUG-119952
  *   Updating 3rd party components for Qt 6.7 started, see 
https://bugreports.qt.io/browse/QTBUG-121323
Next meeting Tue 30th January 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:19] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:29]  pong
[17:00:39]  jaheikki3: pong
[17:01:47] <+jaheikki3> time to start qt release team meeting
[17:01:54]  jaheikki3: pong
[17:01:55] <+jaheikki3> on agenda today:
[17:01:59]  jaheikki3: pong
[17:02:01] <+jaheikki3> Qt 6.6 status
[17:02:07] <+jaheikki3> Qt 6.7 status
[17:02:17] <+jaheikki3> Any additional item to the agenda?
[17:03:40] <+jaheikki3> Ok, let's start from Qt 6.6 status
[17:04:14] <+jaheikki3> Dependency update issues in '6.6' finally fixed and 
branching from '6.6' to '6.6.2' finally done
[17:04:40] <+jaheikki3> The target is to freeze the Qt 6.6.2 release content 
latest by the end of this week
[17:04:59] <+jaheikki3> And the target is still to release Qt 6.6.2 by the end 
of January
[17:05:32] <+jaheikki3> that's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:05:55]  sounds good
[17:06:10] <+jaheikki3> great
[17:06:22] <+jaheikki3> then Qt 6.7 status:
[17:07:20] <+jaheikki3> All known issues from '6.7' dependency update fixed and 
new dependency update round in it's final steps
[17:07:52] <+jaheikki3> Hoping there isn't anymore nothing new and we could get 
update round finally done in '6.7'
[17:08:33] <+jaheikki3> if that succeed it will be then Qt 6.7 beta2content
[17:09:32]  jaheikki3: https://wiki.qt.io/Main doesn't have any Qt 6.7 
timeline, and still talks about 6.6 being in Beta Release status
[17:10:02] <+jaheikki3> And if RTA doesn't find anything alarming we will 
release that as Qt 6.7 beta2. Hoping that can happen either this friday or then 
at the beginning of next week
[17:10:27] <+jaheikki3> vohi: thanks, I'll update the page asap
[17:10:48] <+jaheikki3> Qt 6.7 API review is ongoing &  proceeding, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:11:16] <+jaheikki3> let's try to complete the reviews as soon as possible
[17:11:29] <+jaheikki3> Updating 3rd party components for Qt 6.7 also started, 
see https://bugreports.qt.io/browse/QTBUG-121323
[17:11:51] <+jaheikki3> I think it is all about 6.7 status. Any comments or 
questions?
[17:14:32]  not from me
[17:14:51] <+jaheikki3> Ok, it was all at this time so let's end this meeting 
now & have new one Tue 30th January at this same time
[17:15:01] <+jaheikki3> Thanks for your participation, bye!
[17:15:14]  by
[17:16:50]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.6' to '6.6.2' done

[Jani Heikkinen via Development]

Hi!

We have branched '6.6.2' from '6.6'. So from now on all changes targeted to Qt 
6.6.2 release must have 'Pick-to: 6.6.2' and '6.6' is for Qt 6.6.3 release. As 
usual staging in '6.6.2' is restricted to release team only and we will monitor 
incoming changes and stage the clear ones in automatically. Please do not add 
any nice-to-haves in '6.6.2' anymore; those can wait Qt 6.6.3. The target is to 
release Qt 6.6.2 by the end of January 2024.

There were few changes integrating in '6.6' when branching was done so please 
check if those needs to be manually cherry-picked in '6.6.2' or not.

br,
Jani Heikkinen
Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 16.01.2026

[Jani Heikkinen via Development]

Qt 6.6 status

  *   Branching from '6.6' to '6.6.2' has been delayed. The target is to do the 
branching during this week
  *   The target is still to release Qt 6.6.2 during January

Qt 6.7 status

  *   Beta2 has been delayed. The target is to release Qt 6.7.0 Beta2 soon 
after next successful dependency update round in '6.7'
 *   Hoping it will happen at the beginning of next week
  *   API review is proceeding, see https://bugreports.qt.io/browse/QTBUG-119952
  *   Plan is to create tasks for 3rd party component updated by the end of 
this week
Next meeting Tue 23rd January 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:24]  jaheikki3: pong
[17:00:33]  jaheikki3: pong
[17:01:34]  jaheikki3: pong
[17:02:11] <+jaheikki3> time to start qt release team meeting.
[17:02:17] <+jaheikki3> On agenda today:
[17:02:25] <+jaheikki3> Qt 6.6 status
[17:02:26]  jaheikki3: pong
[17:02:29] <+jaheikki3> QT 6.7 status
[17:02:43] <+jaheikki3> Any additional item to the agenda?
[17:04:33] <+jaheikki3> Let's browse through the statuses & start from Qt 6.6 
one (which is actually pretty much same as it was last time)
[17:05:11] <+jaheikki3> Branching from '6.6' to '6.6.2' delayed because of 
issues with dependency updates in '6.6'
[17:05:40] <+jaheikki3> We should have fixes finally in place & already 
integrated in 'dev'
[17:05:53] <+jaheikki3> So those should be in '6.6' quite soon as well
[17:06:19] <+jaheikki3> And branching from '6.6' to '6.6.2' will happen after 
fixes are in '6.6'
[17:06:34] <+jaheikki3> Hoping that can happen still during this week
[17:06:58] <+jaheikki3> The target is still to release Qt 6.6.2 during January
[17:07:27] <+jaheikki3> I think this is all about Qt 6.6 status at this time. 
Any comments or questions?
[17:07:28]  we have a page of open cherry-picks for 6.6 branches: 
https://codereview.qt-project.org/q/status:open+branch:6.6; presumably many 
failed for the same reason as the dependency updates.
[17:07:54]  but also a bunch of unresolved conflicts, so good to get this 
cleaned up swiftly
[17:08:00] -*- vohi goes and mashes the stage button
[17:08:53] <+jaheikki3> Yeah, thanks vohi!
[17:09:11] <+jaheikki3> Then Qt 6.7 status:
[17:09:47] <+jaheikki3> Beta2 delayed because of those dependency update issues
[17:10:13] <+jaheikki3> The target is to release Qt 6.7.0 Beta2 as soon as 
possible after next successful dependency update round in '6.7'
[17:10:33] -*- thiago thinks the "Fix coffee machine" commit is the most 
important in cold weather
[17:10:47] <+jaheikki3> :D
[17:11:38] <+jaheikki3> Dependency update fixes are integrating in '6.7' so 
hoping we can get full update round done soon, latest by the end of this week
[17:12:23] <+jaheikki3> And so on beta2 could be released at the beginning of 
next week if packages will be good enough for the beta2
[17:12:40] <+jaheikki3> Qt 6.7 API review proceeding, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:13:00] <+jaheikki3> But there is still reviews etc to be done so all help 
there is welcome
[17:13:50] <+jaheikki3> Official update round for Qt 6.7 3rd party modules not 
started yet but plan is to create tasks for updates by the end of this week
[17:14:30] <+jaheikki3> And it was all about Qt 6.7 status at this time. Any 
comments or questions?
[17:16:43] <+jaheikki3> Ok so it was all at this time. Let's end this meeting 
now & have new one Tue 23rd January at this same time
[17:16:52] <+jaheikki3> Thanks for your participation, bye!
[17:17:11]  thanks, bye!
[17:17:22]  bye
[17:17:31]  bye
[17:17:50]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 09.01.2026

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.2 preparations to be started
 *   Target is to start branching from '6.6' to '6.6.2' at the beginning of 
next week
 *   Target is to release Qt 6.6.2 by the end of January 2024
Qt 6.7 status:

  *   Qt 6.7 Beta1 released
  *   Target is to release Qt 6.7 Beta2 by mid January 2024
  *   Qt 6.7 API change review is ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
  *   Updating 3rd party components to be started soon as well
Next meeting Tue 16th January 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:14] <+jaheikki3> ablasche: Akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:20]  jaheikki3: pong
[17:00:44]  jaheikki3: pong
[17:01:25] <+jaheikki3> Time to start qt release team meeting
[17:01:29] <+jaheikki3> on agenda today:
[17:01:32]  pong
[17:01:33] <+jaheikki3> Qt 6.6 status
[17:01:37] <+jaheikki3> Qt 6.7 status
[17:01:47] <+jaheikki3> Any additional item to the agenda?
[17:02:45] <+jaheikki3> Let's start from Qt 6.6 status:
[17:03:07] <+jaheikki3> Qt 6.6.2 preparations to be started
[17:03:20] <+jaheikki3> Target is to start branching from '6.6' to '6.6.2' at 
the beginning of next week
[17:03:37] <+jaheikki3> and target is to release Qt 6.6.2 by the end of January 
2024
[17:03:53] <+jaheikki3> that's all about 6.6 status at this time. Any comments 
or questions?
[17:05:23]  sounds good
[17:05:26] <+jaheikki3> Ok, then Qt 6.7 status
[17:05:55] <+jaheikki3> Qt 6.7 Beta1 released just before Christmas
[17:06:15] <+jaheikki3> The target is to release Qt 6.7 Beta2 by mid January 
2024
[17:06:43] <+jaheikki3> Hoping beta2 can be done from next successful 
dependency update round
[17:06:57] <+jaheikki3> Qt 6.7 API change review is ongoing, see 
https://bugreports.qt.io/browse/QTBUG-119952
[17:07:10] <+jaheikki3> Please try to review open ones as soon as possible
[17:07:34] <+jaheikki3> 3rd party component update will be started soon as well
[17:08:11] <+jaheikki3> I think it is all about Qt 6.7 status at this time. Any 
comments or questions?
[17:10:26] <+jaheikki3> ok, it was all at this time so let's end this meeting 
now & have new one Tue 16th January at this same time.
[17:10:37] <+jaheikki3> thanks for your participation, bye!
[17:10:38]  okidoke, thanks jaheikki3
[17:10:53]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.7 API change review

[Jani Heikkinen via Development]

Hi!



Qt 6.7 API Change Review is finally started, see 
https://bugreports.qt.io/browse/QTBUG-119952

generated diffs are here:

  *   https://codereview.qt-project.org/q/topic:api-change-review-6.7
  *   https://codereview.qt-project.org/q/topic:qml_api_review_6.7



Please review the diffs as soon as possible.



br,

Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 19.12.2023

[Jani Heikkinen via Development]

Qt 6.7 status:

  *   Qt 6.7 Beta1 content is frozen and testing ongoing. Beta1 will be 
released later this week
  *   Target is to start Qt 6.7 header review still during this week
  *   Qt 6.7 FF exceptions
 *   Android NDK update to r26b
*   No objections, exception granted
 *   Support for size policy (QTBUG-117597)
*   No objections, exception granted
 *   finishing C++ 20 comparisons
*   Discussion still ongoing in ML; to be agreed there if exception 
will be granted or not

Next meeting Tue 2nd January 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:01:01]  jaheikki3: pong
[17:02:01] <+jaheikki3> time to start qt release team meeting
[17:02:08] <+jaheikki3> on agenda today:
[17:02:39] <+jaheikki3> Qt 6.7 status (& ff exceptions)
[17:02:48] <+jaheikki3> ANy additional item to the agenda?
[17:04:16] <+jaheikki3> Ok, Qt 6.7 status and FF exceptions
[17:04:38] <+jaheikki3> Qt 6.7 Beta1 content is frozen and testing is ongoing
[17:04:48] <+jaheikki3> Beta1 will be released later this week
[17:05:09] <+jaheikki3> The target is to start Qt 6.7 header review still 
during this week
[17:05:48] <+jaheikki3> There is few FF exceptions requests in dev ml
[17:06:46] <+jaheikki3> - Android NDK update to r26b
[17:06:57] <+jaheikki3> - Support for size policy (QTBUG-117597)
[17:07:10] <+jaheikki3> - finishing C++ 20 comparisons
[17:08:30] <+jaheikki3> Any comments to these?
[17:09:07] <+jaheikki3> I got comments from vohi beforehand and based on his 
opinion we could give exceptions for all these
[17:10:06] <+jaheikki3> I don't have so strong opinions but Ville was against 
of the last one inb dev ML
[17:15:46] <+jaheikki3> It seems there isn't correct persons in the meeting to 
make the decision for the 'finishing C++ 20 comparisons' so let's agree that 
later in ML and give the exceptions for 2 other ones
[17:16:10]  sounds good for me
[17:17:16] <+jaheikki3> Ok, great! So let's end this meeting now & have new one 
Tue 2nd January 2024 at this same time
[17:17:49] <+jaheikki3> Have a nice Christmas & Happy New Year 2024!
[17:17:56] <+jaheikki3> Bye...
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 12.12.2023

[Jani Heikkinen via Development]

Qt 6.7 status:

  *   Qt 6.7 Feature Freeze is in effect
 *   Feature Freeze exceptions will be reviewed in the next meeting
  *   Branching from 'dev' to '6.7' done
  *   Target is to release Qt 6.7 Beta1 immediately after dependency update 
succeed in '6.7'
  *   Target is to start Qt 6.7 Header Review immediately after dependency 
update succeed in '6.7'

Next meeting Tue 19th of December 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:36] <+jaheikki3> ablasche: : akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:42]  jaheikki3: pong
[17:01:49] <+jaheikki3> Time to start qt release team meeting
[17:01:55] <+jaheikki3> on agenda today:
[17:02:00] <+jaheikki3> Qt 6.7 status
[17:02:08] <+jaheikki3> Any additional item to the agenda?
[17:03:33]  jaheikki3: pong
[17:03:52] <+jaheikki3> Ok, let's browse through the Qt 6.7 status
[17:04:14] <+jaheikki3> Qt 6.7 Feature Freeze is in effect
[17:04:29] <+jaheikki3> And branching from 'dev' to '6.7' ongoing
[17:05:06] <+jaheikki3> Target is to release Qt 6.7 Beta1 immediately after 
dependency update succeed in '6.7', hoping that can happen before Christmas
[17:05:18] <+jaheikki3> Dependency update round is already ongoin
[17:05:40] <+jaheikki3> Target is also to start Qt 6.7 Header Review round 
immediately after dependency update succeed in '6.7'
[17:06:10] <+jaheikki3> That actually all about 6.7 status at this time. Any 
comments or questions?
[17:07:49]  Let's review exception requests here next week, so far we 
know of a few, but none of them require an urgent decision as work can/has to 
continue in dev anyway for now
[17:08:12] <+jaheikki3> Yeah, agree
[17:08:56] <+jaheikki3> it was all at this time so let's end the meeting now & 
have new one tue 19th December at this same time
[17:09:10] <+jaheikki3> Thanks for your participation, bye!
[17:09:26]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from 'dev' to '6.7' done

[Jani Heikkinen via Development]

Hi!

Branching from 'dev' to '6.7' is now done and the Qt 6.7 Feature Freeze is in 
effect! So from now on all changes targeted to the Qt 6.7 must have 'Pick-to: 
6.7' and 'dev' is for Qt 6.8.



Unfortunately there were (and still are) issues with CI's INTEGRITY builds, so 
if something urgent was left out because of this, please request an exception 
to be able to integrate them into the 6.7 branch as well.



br,

Jani Heikkinen

Release Manager


From: Development  On Behalf Of Jani 
Heikkinen via Development
Sent: perjantai 8. joulukuuta 2023 16.06
To: development@qt-project.org
Subject: [Development] HEADS-UP: Qt 6.7 Feature Freeze


Hi!



Qt 6.7 Feature Freeze will be in effect today. If your changes are ready and 
approved by the end of today, you can still continue staging those in 'dev' 
over the weekend. The plan is to branch from "6.7" to "dev" on Monday morning 
next week.



If your feature isn't ready by the end of today, you'll either need to postpone 
it to Qt 6.8 or request an exception.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.7 Feature Freeze

[Jani Heikkinen via Development]

Hi!



Qt 6.7 Feature Freeze will be in effect today. If your changes are ready and 
approved by the end of today, you can still continue staging those in 'dev' 
over the weekend. The plan is to branch from "6.7" to "dev" on Monday morning 
next week.



If your feature isn't ready by the end of today, you'll either need to postpone 
it to Qt 6.8 or request an exception.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 05.12.2023

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.1 released
  *   Target is to release Qt 6.6.2 by the end of January 2024

Qt 6.7 status:

  *   Platform and module freeze -milestone in effect
  *   Qt 6.7 Feature Freeze will be in effect Fri 8th of December
  *   Branching from 'dev' to '6.7' will happen Monday 11th of December
  *   Target is to release Qt 6.7 Beta1 immediately after dependency update 
succeed in '6.7'

Next meeting Tue 12th of December 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:28] <+jaheikki3> ablasche: : akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:40]  jaheikki3: pong
[17:01:13]  jaheikki3: pong
[17:01:45]  pong
[17:02:22] <+jaheikki3> Time to start qt release team meeting
[17:02:26] <+jaheikki3> on agenda today:
[17:02:29] <+jaheikki3> Qt 6.6 status
[17:02:32] <+jaheikki3> Qt 6.7 status
[17:02:42] <+jaheikki3> Any additional item to the agenda?
[17:04:29] <+jaheikki3> Let's start from Qt 6.6 status
[17:05:10] <+jaheikki3> Qt 6.6.1 was released 27th November
[17:05:25] <+jaheikki3> So far it seems to be quite good release
[17:05:45] <+jaheikki3> The target is to release Qt 6.6.2 by the end of January 
2024
[17:06:14] <+jaheikki3> That's actually all about Qt 6.6 status at this time. 
Any comments or questions?
[17:07:50] <+jaheikki3> Ok, then Qt 6.7 status
[17:08:10] <+jaheikki3> Platform and module freeze -milestone is in effect
[17:08:29]  jaheikki3: pong
[17:08:57] <+jaheikki3> Adding new prebuild binaries (llvm mingw & Linuc on 
arm) in the repositories ongoing
[17:09:15] <+jaheikki3> Qt 6.7 Feature Freeze will be in effect Fri 8th of 
December
[17:09:29] <+jaheikki3> Branching from 'dev' to '6.7' will happen Monday 11th 
of December
[17:09:49] <+jaheikki3> And the target is to release Qt 6.7 Beta1 immediately 
after dependency update succeed in 'dev'
[17:09:57] <+jaheikki3> Sorry, in '6.7'
[17:10:27] <+jaheikki3> That's all about 6.7 status. Any comments or questions?
[17:10:31] -*- thiago has two unifnished features
[17:10:39]  one was the int128 suppotr that I had promised marc but 
forgot to work on
[17:10:50] <+jaheikki3> thiago: Hoping you can get those ready early enough
[17:10:52]  the other was the QMetaMethod::listInvoke I promised Thomas 
Zander and also didn't work on
[17:11:26]  listInvoke is finishable, only unit tests are missing
[17:12:56] <+jaheikki3> what about the int128 support? thiago: vohi: if those 
won't be ready by the FF are those critical enough to get an exception
[17:12:59]  some of int128 support (as per 
https://bugreports.qt.io/browse/QTBUG-116924) seems to be done and/or in 
progress
[17:13:33]  if all that's not done yet is missing qHash support, then 
that's ok to make an exception for IMHO
[17:13:37]  no work has been done since 6.6 release when I argued we 
shouldn't jump the FF
[17:13:41]  but we didn't develop the feature
[17:13:59]  we're missing proper printing of them (QDebug, QTextStream)
[17:14:03]  QLocale
[17:15:51]  we will either way not be worse off with 6.7 than we are with 
6.6; we can decide for individual items and patches if we want them to be in 
6.7, if they are not merged by time of branching
[17:17:48] <+jaheikki3> yeah, let's check those later if needed. But hoping 
most of important items will be in at FF; the time from FF to final release is 
a bit shorter than earlier...
[17:18:22] <+jaheikki3> This was all about 6.7 status at this time. Is there 
more comments or questions?
[17:20:18] <+jaheikki3> It seems it was all at this time so let's end this 
meeting now & have next one Tue 12th December as planned
[17:20:30] <+jaheikki3> Thanks for your participation, bye!
[17:20:46]  thanks!
[17:20:55]  bye
[17:22:24]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS-UP: Qt 6.7 platform and module freeze

[Jani Heikkinen via Development]

Hi!

Qt 6.7 platform and module freeze is in effect now so no new modules or 
provisioning related changes in 'dev' until '6.7' is branched. Staging in 
qt5#dev is restricted to release team only until branching is done.

br,
Jani

From: Jani Heikkinen
Sent: tiistai 31. lokakuuta 2023 10.39
To: development@qt-project.org
Subject: HEADS-UP: Qt 6.7 Feature Freeze is getting closer
Importance: High


Hi all,



Just a kindly reminder: Qt 6.7 Feature freeze will be in effect 8th of December 
2023 and Qt 6.7 platform and module freeze already 24th of November 2023, see 
https://wiki.qt.io/Qt_6.7_Release.



Please inform me about all new modules planned to be released in Qt 6.7; we 
should start adding those in CI & packages now. Also please inform me if 
existing technology preview module will be officially supported etc.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 21.11.2023

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.1 release content is frozen and package creation is ongoing
  *   Qt 6.6.1 will be released when package testing is done
 *   Most probably this will happen at the beginning of next week

Qt 6.7 status:

  *   Platform and module freeze -milestone will be in effect Friday 24th of 
November
  *   The target is to update Qt 6.7.0 snapshot to the production later this 
week


Next meeting Tue 5th of December 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:12] <+jaheikki3> ablasche: akseli: carewolf: lars_: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:53]  jaheikki3: pong
[17:01:11] <+jaheikki3> time to start qt release team meeting
[17:01:17] <+jaheikki3> On agenda today:
[17:01:20] <+jaheikki3> Qt 6.6 status
[17:01:26] <+jaheikki3> Qt 6.7 status
[17:01:33]  jaheikki3: pong
[17:01:35] <+jaheikki3> Any additional item to the agenda?
[17:02:40] <+jaheikki3> Let's start from Qt 6.6 status
[17:03:03] <+jaheikki3> Branching from '6.6' to '6.6.1' done
[17:03:23]  pong
[17:03:32] <+jaheikki3> All Qt 6.6.1 release blockers are fixed and Qt 6.6.1 
release content is frozen
[17:03:44] <+jaheikki3> Package creation is ongoing
[17:03:46]  there's the discussion on IPC
[17:04:01] <+jaheikki3> thiago: where?
[17:04:29]  https://codereview.qt-project.org/c/qt/qtbase/+/518039
[17:05:20]  thiago: is 6.6 worse than any release before it was? My 
interpretation of your email is that things are as bad as before right now.
[17:05:30]  yes
[17:05:36]  it was bad, I made worse
[17:06:57]  ok, so the unavoidable memory leak in 6.6, also after the 
recent fixes following the refactoring, are new in 6.6
[17:07:01] <+jaheikki3> But is this really critical enough to delay Qt 6.6.1 
release? Qt 6.6.2 will be released at the beginning of next year
[17:07:06]  and not fixable for 6.6.1
[17:08:09]  6.6.0 switched the POSIX backend, which leaks memory 100% 
of the tmie
[17:08:16]  the SysV one at least tried to delete
[17:08:19]  it would be status quo
[17:08:29]  the switch only happens for the new API
[17:08:42]  so 6.6.0 is telling people to switch from the old (status 
quo) to the new, worse one
[17:08:50]  I want people *not* to port
[17:10:25] <+jaheikki3> vohi: ?
[17:10:45]  thiago: ok; we could make the change that deprecates those 
APIs for 6.7, and we can publish the online documentation with patches on top 
of 6.6.1 without having to reopen the package. Local documentation would not 
include those changes of course. But maybe a blog post or otherwise head-up 
about the situation would anyway be a good idea; people won't see the doc 
changes unless they are actively looking
[17:11:25]  I think 6.6.1 needs a change that un-deprecates the old API
[17:11:31]  that's the bare minimum
[17:13:08] <+jaheikki3> thiago: do we have that change in place already?
[17:13:09]  those deprecations are from 6.10 on for most people, pointing 
at "Native IPC Key" documentation; can we update that documentation, and remove 
the deprecations for 6.6.2?
[17:13:12]  no
[17:13:27]  the change I have undeprecates the old API but deprecates 
the entire class
[17:13:42]  we could split it in two
[17:14:06]  youŕ e misunderstanding
[17:14:12]  ah, wait, no, I am
[17:14:18]  those are 6.10 deprecations
[17:15:00]  but people who enable deprecated_since=6.0 will get it and 
will begin porting to worse code
[17:15:07]  I still suggest we remove the deprecations, completely
[17:16:25]  I agree that we should remove the deprecations in 6.6.2 at 
the latest. If we have that patch in 6.6, then we can generate the online 
documentation with that change. The question is then if we need to stop the 
6.6.1 show for that patch. deprecated_since=6.0 is an opt-in, right?
[17:17:12]  it is
[17:18:01]  Ok; I think with updated online documentation and a blog 
and/or mail to interest@ telling people to ignore the deprecation warning and 
not port to the new API will be acceptable then
[17:18:11]  ok
[17:18:21]  we can discuss further next week too
[17:18:43]  but 6.6.1 doesn't need to wait for that
[17:18:59]  👍
[17:19:01] <+jaheikki3> Great!
[17:19:50] <+jaheikki3> Who does the online documentation change in 6.6? I'll 
make then sure that it will be taken in the documentation update for Qt 6.6.1
[17:20:35] <+jaheikki3> and what about that blog/interest ml?
[17:20:53]  I can do the interest ML
[17:21:12] <+jaheikki3> thanks
[17:21:15]  but both I'd like to suggest we discuss what the long-term 
will be, frst
[17:21:23]  so, next Friday at the earliest
[17:22:48] <+jaheikki3> That's OK. It just means we don't have those ready with 
Qt 6.6.1 release but I think that's OK; we can update the online documentation 
whenever we have consensus & needed changes in place
[17:23:02]  I'll ping Topi about including the patch w

[Development] HEADS-UP: Branching from '6.6' to '6.6.1' done

[Jani Heikkinen via Development]

Hi!

We have branched '6.6.1' from '6.6'. So from now on all changes targeted to Qt 
6.6.1 release must have 'Pick-to: 6.6.1' and '6.6' is for Qt 6.6.2 release. As 
usual staging in '6.6.1' is restricted to release team only and we will monitor 
incoming changes and stage the clear ones in automatically. Please do not add 
any nice-to-haves in '6.6.1' anymore; those can wait Qt 6.6.2. The target is to 
release Qt 6.6.1 23rd of November 2023.

br,
Jani Heikkinen
Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 07.11.2023

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.1 release preparations are ongoing
 *   Branching from '6.6' to '6.6.1' will happen Tue 14th of November
 *   Target is to release Qt 6.6.1 Thu 23rd of November


Qt 6.7 status:

  *   Platform and module freeze -milestone will be in effect 24th of November
 *   No new modules known for Qt 6.7. If there will be any please inform 
Jani immediately.
 *   Possible exceptions can be taken in after FF & Beta1; It is really 
important to stop provisioning changes at platform and module freeze.
  *   Qt 6.7 Feature Freeze will be in effect 8th of December so only a month 
time to implement new features for Qt 6.7.

Next meeting Tue 21st of November 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[16:59:35] <+jaheikki3> ablasche: akseli: carewolf: lars_: mapaaso: 
The-Compiler: thiago. vohi: ping
[16:59:44]  jaheikki3: pong
[17:00:10]  jaheikki3: pong
[17:00:52] <+jaheikki3> Time to start qt release team meeting
[17:00:58] <+jaheikki3> on agenda today:
[17:01:03] <+jaheikki3> Qt 6.6 status
[17:01:10] <+jaheikki3> Qt 6.7 status
[17:01:18] <+jaheikki3> Any additional item to the agenda?
[17:02:40] <+jaheikki3> Let's start from Qt 6.6 status
[17:02:58] <+jaheikki3> Which is actually pretty much the same as last time:
[17:03:15] <+jaheikki3> Qt 6.6.1 release preparations are ongoing
[17:03:34] <+jaheikki3> Branching from '6.6' to '6.6.1' will happen Fri 10th of 
November
[17:04:03] <+jaheikki3> And the target is to release Qt 6.6.1 23rd of November
[17:05:10] <+jaheikki3> That's actually all about qt 6.6 status at this time. 
Any comments or questions?
[17:06:01]  given that it's bug fixing sprint in the company, maybe 
branching after that is over makes more sense?
[17:06:26]  ie. wait for Tuesday 14th
[17:06:46] <+jaheikki3> That's actually true, I'll postpone the branching then 
a bit
[17:06:59]  +1
[17:07:14] <+jaheikki3> So branching will happen Tue 14th
[17:07:25] <+jaheikki3> Thanks for noticing this!
[17:07:53] <+jaheikki3> Ok, then Qt 6.7 status
[17:08:34] <+jaheikki3> Some challenges to get dependency update done in 'dev'; 
last successful round 20th October
[17:09:10] <+jaheikki3> But known issues should be fixed and new round will be 
started when latest fix integrates in qtbase
[17:09:26] <+jaheikki3> Platform and module freeze -milestone will be in effect 
24th of November
[17:09:38] <+jaheikki3> No new modules informed so far
[17:10:05] <+jaheikki3> So if there will be any please inform me immediately
[17:10:44] <+jaheikki3> Qt 6.7 Feature Freeze will be in effect 8th of December 
so only a month left to implement new features for Qt 6.7
[17:10:56]  ok
[17:11:12] <+jaheikki3> That's all about Qt 6.7 status at this time. Any 
comments or questions?
[17:11:16] -*- thiago needs to finish one feature for QMetaObject::listInvoke
[17:11:20]  thanks for reminding
[17:11:22]  we might have some provisioning changes coming in as a 
consequence of trying to link dynamically against FFmpeg; are those subject to 
the platform/modules deadline?
[17:11:52]  (in which case I might just as well ask for exception right 
away ;))
[17:12:08] <+jaheikki3> vohi: yes, those are. It is really important to stop 
provisioning changes at platform/module freeze
[17:13:11]  agree, those take along time and often have a lot of fallout; 
but also important that we stop linking statically against FFmpeg, that library 
has a huge attack surface
[17:13:17] <+jaheikki3> vohi: if we need an exception for those that's OK for 
me but as usual those exceptions should be taken in only after the FF; after 
beta1 is out
[17:14:20] <+jaheikki3> (those platform etc provisioning changes has been 
biggest reason for FF/beta1 delays in previous releases and it has been much 
easier after we took that milestone in the use)
[17:16:45] <+jaheikki3> It was all at this time so let's end this meeting now. 
I can't participate Tue 14th so let's have new meeting Tue 21st at this same 
time
[17:17:01] <+jaheikki3> Thanks for your participation, bye!
[17:17:04]  bye
[17:19:30]  thanks!

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.7 Feature Freeze is getting closer

[Jani Heikkinen via Development]

Hi all,



Just a kindly reminder: Qt 6.7 Feature freeze will be in effect 8th of December 
2023 and Qt 6.7 platform and module freeze already 24th of November 2023, see 
https://wiki.qt.io/Qt_6.7_Release.



Please inform me about all new modules planned to be released in Qt 6.7; we 
should start adding those in CI & packages now. Also please inform me if 
existing technology preview module will be officially supported etc.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 24.10.2023

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.0 released 2 weeks ago
  *   Qt 6.6.1 release preparations started
 *   First snapshot created
 *   Target is to release Qt 6.6.1 23rd of November
 *   ? branching from '6.6' to '6.6.1' will happen ~mid November

Qt 6.7 status:

  *   Snapshot from 'dev' publicly available & updated regularly
  *   Platform and module freeze -milestone will be in effect 24th of November
 *   Please inform possible new modules for Qt 6.7 to Jani immediately

Next meeting Tue 7th of November 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:58] <+jaheikki3> ablasche: akseli: carewolf: lars_:mapaaso: mibrunin: 
The-Compiler: thiago: vohi: ping
[17:01:05]  jaheikki3: pong
[17:01:10]  pong
[17:01:12]  jaheikki3: pong
[17:01:25]  jaheikki3: pong
[17:01:56]  jaheikki3: pong
[17:02:02] <+jaheikki3> Time to start qt release team meeting
[17:02:09] <+jaheikki3> on agenda today:
[17:02:13] <+jaheikki3> Qt 6.6 status
[17:02:19] <+jaheikki3> Qt 6.7 status
[17:02:25] <+jaheikki3> Any additional item to the agenda?
[17:04:01] <+jaheikki3> Ok, let's start from Qt 6.6 status
[17:04:55] <+jaheikki3> Qt 6.6.0 released 2 weeks ago. It seems to be quite ok 
release; there is bug reports but at least I haven't seen anything alarming
[17:05:35] <+jaheikki3> Qt 6.6.1 preparations started & first snapshot created
[17:05:57] <+jaheikki3> Target is to release Qt 6.6.1 23rd of November
[17:06:26] <+jaheikki3> So branching from 6.6 -> 6.6.1 will happen ~ mid 
November
[17:06:59] <+jaheikki3> That's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:08:45] <+jaheikki3> Ok, then Qt 6.7 status
[17:09:16] <+jaheikki3> Snapshot from 'dev' publicly available & updated 
regularly
[17:10:03] <+jaheikki3> Platform and module freeze -milestone will be in effect 
24th of November so a month time to add new modules & do platform updates
[17:10:27] <+jaheikki3> So please inform possible new modules to me as soon as 
possible
[17:10:40] <+jaheikki3> At the moment I don't know any new modules for Qt 6.7
[17:11:06] <+jaheikki3> Actually this was all about Qt 6.7 status at this time. 
Any comments or questions?
[17:12:09]  none from me
[17:12:57] <+jaheikki3> Ok, let's then end this meeting now. I think we can 
skip next week's meeting & have new one Tue 7th of November at this same time
[17:13:15] <+jaheikki3> thanks for your participation, bye!
[17:13:30]  thanks, bye!
[17:15:04]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 03.10.2023

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   All issues from Qt 6.6.0 release blocker list are fixed -> Qt 6.6.0 
release content is now frozen
  *   We will release Qt 6.6.0 Tue 10th of October (if no new severe regression 
found when testing final packages)
  *   Qt 6.6.1 release target at the end of November
Qt 6.7 status:

  *   Snapshot from 'dev' publicly available
 *   Target is to update the snapshot later this week
  *   It is time to start adding new modules for Qt 6.7 in dev
 *   Qt 6.7.0 platform and module freeze will be in effect 24.11

Next meeting Tue 17th October 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:52]  jaheikki3: pong
[17:01:17]  jaheikki3: pong
[17:01:34]  time to start qt release team meeting
[17:01:38]  on agenda today:
[17:01:41]  Qt 6.6 status
[17:01:44]  Qt 6.7 status
[17:01:53]  Any additional item to the agenda?
[17:03:31]  Let's start from Qt 6.6 status
[17:03:46]  All issues from Qt 6.6.0 release blocker list are fixed
[17:04:11]  And last fix is integrating in '6.6.0'
[17:04:28]  All documentation related updates are also in
[17:04:47]  So we will freeze Qt 6.6.0 after last fix is merged
[17:05:22]  And  we will release Qt 6.6.0 Tue 10th of October if no 
new regression found when testing final packages
[17:06:18]  Qt 6.6.1 will be released ~1,5 months after 6.6.0 so 
release target for it is at the end of November
[17:06:38]  that's all about 6.6 status at this time. Any comments 
or questions?
[17:06:54]  if the last fix is integrating now, the release is in one 
week?
[17:07:35]  thiago: We need enough time for dependency update round, 
packaging & testing
[17:08:02]  ah, ok
[17:08:08]  got it
[17:08:50]  ok, then Qt 6.7 status:
[17:09:04]  snapshot from 'dev' publicly available
[17:09:21]  The target is to update the snapshot later this week
[17:09:59]  And it is time to start adding new modules etc in the 
'dev'; platform and module freeze will be in effect 24.11
[17:10:34]  that's actually all about 6.7 status at this time. Any 
comments or questions?
[17:12:15]  not from me
[17:12:37]  Great, it was all at this time so let's end this meeting 
now & have new one Tue 17th October at this same time. Tue 10th is the release 
day so no need to have a meeting then
[17:12:51]  thanks for your participation, bye!
[17:13:16]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 26.09.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

- Qt 6.5.3 release content is frozen, packages are created & testing is ongoing

- These packages will be released as Qt 6.5.3 if no new surprises found



Qt 6.6 status:

- Qt 6.6.0 rc is released and testing is started

- Target is to release Qt 6.6.0 Tue 10th of October

   * blocker list here: https://bugreports.qt.io/issues/?filter=25215



Next meeting Tue 3rd of October 2023 16:00 CET



br,

Jani Heikkinen

Release Manager

irc log below:
[17:00:25]  ablasche: akseli: carewolf: frkleint: lars_: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:02:00]  time to start qt release team meeting
[17:02:05]  on agenda today:
[17:02:09]  jaheikki3: pong
[17:02:10]  Qt 6.5 status
[17:02:15]  Qt 6.6 status
[17:02:27]  Any additional item to the agenda?
[17:04:00]  Let's start from Qt 6.5 status
[17:04:14]  Qt 6.5.3 release content frozen
[17:04:27]  Packages are created and testing started
[17:04:59]  We will release these packages as Qt 6.5.3 if no new 
surprises found
[17:05:40]  That's actually all about Qt 6.5 status at this time. 
Any comments or questions?
[17:07:19]  Then Qt 6.6 status:
[17:07:32]  Qt 6.6.0 rc released today
[17:07:44]  Testing RC ongoing
[17:08:07]  Target is to release Qt 6.6.0 Final Tue 10th October
[17:08:18]  blocker list here: 
https://bugreports.qt.io/issues/?filter=25215
[17:08:51]  Looking good so far but I bet there will be some new 
findings
[17:09:18]  that's all about Qt 6.6 status. Any comments or 
questions?
[17:10:27]  not from me
[17:10:58]  ok, it was all at this time so let's end this meeting 
now & have new one tue 3rd of October at this same time
[17:11:08]  Thanks for your participation, bye!
[17:11:39]  thanks! and apologies for being late
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Staging in qt5#dev is restricted to release team only

[Jani Heikkinen via Development]

Hi!

Staging in qt5#dev is finally enabled for everyone again. Sorry that this took 
so long.

br,
Jani

From: Development  On Behalf Of Jani 
Heikkinen via Development
Sent: torstai 31. elokuuta 2023 10.08
To: development@qt-project.org
Subject: [Development] Staging in qt5#dev is restricted to release team only

Hi!
There seems to be so many qt5 level changes going in so we decided to 
coordinate the staging to save resources. So Jukka and me will handle the 
staging in qt5#dev a while.

br,
Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 19.09.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

- Branching from '6.5' to '6.5.3' is done

- Target is to release Qt 6.5.3 Wed 27th of September

   * Release content will be frozen latest Friday 22nd of September



Qt 6.6 status:

- Qt 6.6.0 Beta4 is released

- Branching from '6.6' to '6.6.0' is done & RC preparations are ongoing

   * RC blocker list here: https://bugreports.qt.io/issues/?filter=25215

-  RC content needs to be frozen latest Thu 21st September to be able to keep 
the updated schedule

   * Qt 6.6.0 RC target Tue 26th September

   * Qt 6.6.0 Final release Tue 10th October

Next meeting Tue 26th September 2023 16:00 CET



br,

Jani Heikkinen

Release Manager

irc log below:
[17:01:17]  ablasche: akseli: carewolf: frkleint: lars_: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:01:42]  jaheikki3: pong
[17:02:12]  Time to start qt release team meeting
[17:02:18]  on agenda today:
[17:02:24]  Qt 6.5 status
[17:02:28]  qt 6.6 status
[17:02:37]  Any additional item to the agenda?
[17:04:13]  ok, lets start from Qt 6.5 status
[17:04:20]  pong
[17:04:33]  Branching from '6.5' to '6.5.3' is done and release 
preparations are ongoing
[17:04:46]  Target is to release Qt 6.5.3 Wed 27th of September
[17:05:16]  so we need to freeze the release content latest this 
friday
[17:05:39]  Few changes are still missing but that should be doable
[17:06:04]  that's all about Qt 6.5 status at this time. Any 
comments or questions?
[17:07:40]  ok, then Qt 6.6 status
[17:07:57]  Qt 6.6.0 Beta4 released yesterday
[17:08:10]  Branching from '6.6' to '6.6.0' is done
[17:08:19]  and RC preparations are ongoing
[17:08:38]  RC blocker list almost empty, see 
https://bugreports.qt.io/issues/?filter=25215
[17:09:00]  RC content needs to be frozen latest Thu 21st of 
September to be able to keep the updated schedule
[17:09:07]  Qt 6.6.0 RC target Tue 26th September
[17:09:13]  and Qt 6.6.0 Final release Tue 10th October
[17:09:43]  That's all about Qt 6.6 status. Any comments or 
questions?
[17:11:35]  It was all at this time. Let's end this meeting now & 
have new one Tue 26th September as planned
[17:11:50]  thanks for your participation, bye!
[17:17:01]  kbye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.5' to '6.5.3' done

[Jani Heikkinen via Development]

Hi!

We have branched '6.5.3' from '6.5' now. So from now on all changes targeted to 
Qt 6.5.3 release must have 'Pick-to: 6.5.3'. As usual staging in '6.5.3' is 
restricted to release team only and we will monitor incoming changes 
automatically. The target is to release Qt 6.5.3 during September.



br,

Jani Heikkinen

Release Manager


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.6' to '6.6.0' done

[Jani Heikkinen via Development]

Hi!



We have branched '6.6.0' from '6.6' now. So from now on all changes targeted to 
Qt 6.6.0 release must have 'Pick-to: 6.6.0' and '6.6' is for Qt 6.6.1. But 
remember, please do not try to add anything nice-to-haves in '6.6.0' anymore; 
we will take in only fixes for release blockers (+ of course documentation and 
example improvements).



Qt 6.6.0 release blocker list here: 
https://bugreports.qt.io/issues/?filter=25215. Please make sure all release 
blockers are visible in the blocker list and are fixed immediately.



As usual staging will be restricted for release team only in '6.6.0'. We will 
monitor changes and stage clear ones in automatically.



br,

Jani Heikkinen

Release Manager



-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 12.09.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

- Branching from '6.5' to '6.5.3' isn't done yet but the target is to do the 
branching later this week

- The target is still to release Qt 6.5.3 during September.

Qt 6.6 status:

- Qt 6.6.0 Beta4 content is frozen. The target is to release the beta4 later 
this week

- Branching from '6.6' to '6.6.0' will be done Wed 13th September

- Qt 6.6 RC blocker list here: https://bugreports.qt.io/issues/?filter=25215



Next meeting Tue 19th September 2023 16:00 CET

br,

Jani Heikkinen

Release Manager

irc log below:
[17:00:28]  ablasche: akseli: carewolf_home: frkleint: 
lars_:mapaaso:The-Compiler:thiago: vohi: ping
[17:00:39]  jaheikki3: pong
[17:00:59]  jaheikki3: pong
[17:01:58]  time to start qt release team meeting
[17:02:05]  on agenda today:
[17:02:10]  Qt 6.5 status
[17:02:14]  Qt 6.6 status
[17:02:24]  Any additional item to the agenda?
[17:02:40]  pong
[17:03:37]  Let's start from Qt 6.5 status
[17:04:13]  Actually the status is exactly the same as last week: 
Branching from '6.5' to '6.5.3' isn't done yet but the target is to do the 
branching later this week
[17:05:23]  there is still couple of failed cherry picks in '6.5' 
and waiting for those to go in before branching
[17:05:40]  And the target is still to release Qt 6.5.3 during 
September
[17:06:05]  that's all about 6.5 status at this time. Any comments 
or questions?
[17:07:26]  ok, then Qt 6.6 status:
[17:07:36]  I guess once 6.5 cherry-picks are merged, we also need to 
wait for the submodule update round
[17:08:38]  vohi: Yeah, I think it would be good to wait that as 
well to make sure everything is OK
[17:09:29]  Qt 6.6 beta4 content should be frozen finally
[17:10:21]  Package creation will start immediately after exporting 
the qt5.git integration is ready
[17:10:35]  Target is to release beta4 later this week
[17:11:02]  And branching from '6.6' to '6.6.0' will start tomorrow 
morning
[17:11:31]  Qt 6.6 RC blocker list here: 
https://bugreports.qt.io/issues/?filter=25215
[17:11:54]  Hoping we can close open ones so that we could get the 
RC out during next week
[17:12:23]  that's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:13:11]  my changes usually take 3-4 weeks to go from "I'm done" to 
"reviewed and merged"
[17:13:40]  may I take this as a permission to send "ping" after 2 days 
instead of 7?
[17:13:56]  thiago: let's hope a bit quicker progress at this time
[17:14:16]  past performance isn't a good indicator here
[17:14:39]  And I think that's ok at least at this time when we are 
handling a blocker for the release
[17:14:41]  for stuff that is release-blocking, nag as quickly as you
[17:14:45]  want
[17:15:13]  thiago: given your timezone, a mail to the list after you 
pushed something that needs an urgent review will not be too early
[17:17:13]  thiago: and it seems review is already started but some 
clarification is needed
[17:18:53]  Ok, I think it was all at this time so let's end this 
meeting now & have new one Tue 19th September at this same time
[17:19:07]  thanks!
[17:19:08]  Thanks for your participation, bye!

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 05.09.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

  *   Branching from '6.5' to '6.5.3' isn't done yet but the target is to do 
the branching later this week
  *   Target is to release Qt 6.5.3 during September.

Qt 6.6 status:

  *   Qt 6.6.0 Beta4 content isn't frozen yet, target is to freeze it during 
this week
 *   still waiting remaining API change review related fixes to land in 
'6.6' as well as some 3rd party component updates
  *   Branching from '6.6' to '6.6.0' not done yet, will happen after beta4 
content is frozen.
  *   Target is to release Qt 6.6.0 RC ~mid September
 *   Qt 6.6 RC blocker list here: 
https://bugreports.qt.io/issues/?filter=25215



Qt 6.7 initial schedule:

  *   Qt 6.7 Platform and Module freeze 24.11.2023
  *   Qt 6.7 Feature Freeze 8.12.2023
  *   Qt 6.7 Beta1 19.12.2023
  *   Qt 6.7 RC 5.3.2024
  *   Qt 6.7 Final release 19.3.2024



Next meeting Tue 12th September 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:

[17:00:55]  ablasche: akseli: carewolf_work: frkleint: 
lars_:mapaaso:The-Compiler:thiago: vohi: ping

[17:01:29]  jaheikki3: pong

[17:01:42]  jaheikki3: pong

[17:01:47]  time to start qt release team meeting

[17:01:52]  on agenda today:

[17:01:59]  Qt 6.5 status

[17:02:03]  Qt 6.6 status

[17:02:08]  Qt 6.7 initial schedule

[17:02:18]  Any additional items to the agenda?

[17:03:10]  Let's start from Qt 6.5 status

[17:03:28]  Branching from '6.5' to '6.5.3' not done yet but the 
target is to do the branching later this week

[17:03:55]  Release plan is still the same: Target is to release Qt 
6.5.3 during September. Current target is 19th of September

[17:04:20]  That's all about Qt 6.5 status at this time. Any 
comments or questions?

[17:04:25]  the recent CI instability has caused a lot of cherry-picks 
into 6.5 (and 6.6 for that matter) to fail and pile up, e.g. 
https://codereview.qt-project.org/q/status:open+branch:6.5+repo:qt/qtbase

[17:05:03]  since 6.5.3 is expected to be the last release immediately 
available to Open Source users we should make sure that most things are in 
before we branch

[17:05:41]  Yeah, agree. And we aren't that hurry with Qt 6.5.3 so 
we can wait thse

[17:06:32]  Then Qt 6.6 status

[17:06:54]  Qt 6.6.0 Beta4 content isn't frozen yet

[17:07:30]  We are still waiting remaining API change review related 
fixes to land in '6.6' as well as some 3rd party component updates

[17:07:56]  target is to freeze the beta4 content during this week

[17:08:34]  Branching from '6.6' to '6.6.0' isn't done yet. Target 
is to do it  after beta4 content is frozen.

[17:09:11]  Target is to release Qt 6.6.0 RC ~mid September, blocker 
list here: https://bugreports.qt.io/issues/?filter=25215

[17:09:30]  That's all about QT 6.6 status at this time. Any 
comments or questions?

[17:10:48]  checking

[17:11:12]  no

[17:11:29]  And then Qt 6.7 initial schedule:

[17:11:58]  Proposal sent to dev ml last week 
(https://lists.qt-project.org/pipermail/development/2023-August/044417.html), 
no objections

[17:12:12]  So initial schedule for Qt 6.7 is:

[17:12:23]  Qt 6.7 Platform and Module freeze 24.11.2023

[17:12:33]  Qt 6.7 Feature Freeze 8.12.2023

[17:12:39]  Qt 6.7 Beta1 19.12.2023

[17:12:45]  Qt 6.7 RC 5.3.2024

[17:12:51]  and Qt 6.7 Final release 19.3.2024

[17:13:09]  Any comments or questions?

[17:13:48]  freeze shortly before WS and CS, probably a good idea

[17:14:08]  oh, feature freeze is after

[17:14:36]  ok, no problem. So long as it's not that exact week.

[17:14:47]  Great!

[17:15:26]  It was all at this time. Let's end this meeting now & 
have new one Tue 12th September at this same time

[17:15:34]  Thanks for your participation, bye!

[17:16:06]  thanks, bye




-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Qt 6.7.0 initial schedule

[Jani Heikkinen via Development]

Hi all!



My proposal for Qt 6.7 schedule is:



* Qt 6.7 Platform and Module freeze 24.11.2023

* Qt 6.7 Feature Freeze 8.12.2023

* Qt 6.7 Beta1 19.12.2023

* Qt 6.7 RC 5.3.2024

* Qt 6.7 Final release 19.3.2024



This is pretty much similar schedule we had with Qt 6.5.0, only beta phase is a 
bit shorter because of Easter at the end of March. But I think this should be 
doable; we just need to respect the milestones to make it happen!



Any objections?



br,

Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Staging in qt5#dev is restricted to release team only

[Jani Heikkinen via Development]

Hi!
There seems to be so many qt5 level changes going in so we decided to 
coordinate the staging to save resources. So Jukka and me will handle the 
staging in qt5#dev a while.

br,
Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 29.08.2023

[Jani Heikkinen via Development]

Qt 6.6 status:

  *   Qt 6.6.0 beta3 released
  *   Qt 6.6.0 Beta4 preparations started. Target is to release Qt 6.6.0 beta4 
at week 36.
  *   API Change review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214
  *   Updating 3rd party components is also ongoing, see 
https://bugreports.qt.io/browse/QTBUG-116234
  *   Branching from '6.6' to '6.6.0' will happen after beta4 content is frozen.
  *   Target is to release Qt 6.6.0 RC ~mid September
 *   Qt 6.6 RC blocker list here: 
https://bugreports.qt.io/issues/?filter=25215
Qt 6.5 status:

  *   Qt 6.5.3 release preparations started
 *   Target is to release Qt 6.5.3 during September. Current target is 19th 
September.
 *   Target is to start branching from '6.5' to '6.5.3' 5th September
 *   Qt 6.5.3 will be the last public release from Qt 6.5 series
 *   Qt 6.5.3 blocker list here: 
https://bugreports.qt.io/issues/?filter=25223

Next meeting Tue 5th September 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:18]  alblasch: akseli: carewolf_work: frkleint: 
lars__:mapaaso_:The-Compiler: thiago: vohi: ping
[17:01:08]  jaheikki3_: pong
[17:01:19]  jaheikki3_: pong
[17:01:39]  jaheikki3_: pong
[17:02:00]  time to start qt release team meeting
[17:02:05]  On agenda today:
[17:02:10]  Qt 6.6 status
[17:02:13]  Qt 6.5 status
[17:02:27]  Any additional item to the agenda?
[17:03:36]  Let's start from Qt 6.6 status:
[17:03:57]  beta3 released and beta4 preparations started
[17:04:09]  Target is to release Qt 6.6.0 beta4 at week 36
[17:04:26]  API Change review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214
[17:04:43]  Updating 3rd party components is also ongoing, see 
https://bugreports.qt.io/browse/QTBUG-116234
[17:05:38]  Please help finalize those; it would be good to get all 
related fixes in before Beta4
[17:06:04]  For the API change review, most comments outside of Qt Core 
seem to be addressed with changes integrating; Qt Core has a few open comment 
threads
[17:06:47]  Branching from '6.6' to '6.6.0' will happen after beta4 
content is frozen
[17:07:21]  Target is to release Qt 6.6.0 RC ~ mid September, Qt 
6.6 RC blocker list here: https://bugreports.qt.io/issues/?filter=25215
[17:07:43]  That's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:09:08]  Ok, then quick Qt 6.5 status update
[17:09:26]  I think the core ones are waiting for Marc to come back 
from vacation
[17:10:39]  Qt 6.5.3 release preparations started
[17:10:56]  Target is to release Qt 6.5.3 during September. Current 
target 19th September
[17:11:05]  thiago: some yes; but you could probably reply to his 
qprocess.h comments (the pass-by-value comment makes sense if the others can be 
closed without action)
[17:12:01]  Target is to start branching from '6.5' to '6.5.3' 5th 
September
[17:12:12]  Qt 6.5.3 blocker list here: 
https://bugreports.qt.io/issues/?filter=25223
[17:12:42]  And plan is that Qt 6.5.3 is the last public release 
from Qt 6.5 series
[17:13:03]  That's all about QT 6.5 status. Any comments or 
questions?
[17:15:16]  Ok, it was all at this time. Let's end this meeting now 
& have new one Tue 5th September at this same time
[17:15:26]  Thanks for your participation, bye!
[17:15:32]  thanks!
[17:17:11]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS UP : Qt 6.6 string freeze

[Jani Heikkinen via Development]

Hi all,

String freeze for Qt 6.6 is in effect now.

br,
Jani

> -Original Message-
> From: Jani Heikkinen
> Sent: tiistai 15. elokuuta 2023 14.55
> To: localizat...@qt-project.org; development@qt-project.org; releasing@qt-
> project.org
> Subject: HEADS UP : Qt 6.6 soft string freeze
> 
> Hi all,
> First beta releases from Qt 6.6 are out and it is time to start keeping 
> translatable
> strings as it is. The official string freeze for Qt 6.6 will be in effect Tue 
> 22nd of
> August 2023.
> 
> br,
> Jani Heikkinen
> Release Manager
> 
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Failed to run configure.bat in qt/qt5 repository on Windows?

[Jani Heikkinen via Development]

Hi!

The documentation is a bit misleading; you can't install those packages from Qt 
Online Installer. You can download those packages from 
http://download.qt.io/development_releases/prebuilt/libclang/qt and those are 
the same which are used for building the Qt binaries in the online installer.

br,
Jani

> -Original Message-
> From: Development  On Behalf Of
> Haowei Hsu
> Sent: perjantai 18. elokuuta 2023 5.36
> To: Cristian Adam 
> Cc: Qt development mailing list 
> Subject: Re: [Development] Failed to run configure.bat in qt/qt5 repository on
> Windows?
> 
> Hello, Cristian.
> 
> According to Installing Clang for QDoc  clang.html> , it seems that we can install thoes pre-built libclang packages 
> from
> Qt Online Installer, right?
> 
> 
> 
> 
> However, I didn't find any of them in Qt Online Installer. Why?
> 
> 
> 
> ---
> Haowei Hsu
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 15.08.2023

[Jani Heikkinen via Development]

Qt 6.6 status

  *   Qt 6.6 Beta3 preparations are ongoing
 *   Content is not frozen yet but target is to freeze the content later 
this week
 *   The latest estimate for beta3 release is Tue 22nd August
  *   API Change review is still ongoing, see 
https://lists.qt-project.org/pipermail/development/2023-August/044267.html
  *   Soft string freeze in effect now: 
https://lists.qt-project.org/pipermail/localization/2023-August/000578.html

Next meeting Tue 29th August 2023 16:00 CET


br,

Jani Heikkinen

Release Manager



irc log below:

[17:00:21] <+jaheikki3> ablasche: akseli: carewolf_home:frkleint: 
lars_:mapaaso: The-Compiler:thiago:vohi: ping

[17:00:33]  jaheikki3: pong

[17:00:37]  jaheikki3: pong

[17:01:03] <+jaheikki3> time to start qt release team meeting

[17:01:09] <+jaheikki3> on agenda today:

[17:01:11]  pong

[17:01:15] <+jaheikki3> Qt 6.6 status

[17:01:25] <+jaheikki3> Any additional item to the agenda?

[17:02:43] <+jaheikki3> Ok, Qt 6.6 status update:

[17:03:06] <+jaheikki3> Qt 6.6 Beta3 preparations are still ongoing

[17:03:19]  not beta4?

[17:03:35] <+jaheikki3> carewolf_home: beta3 isn't released yet

[17:03:38]  ah, no okay

[17:04:07] <+jaheikki3> Content is not frozen yet but the target is to freeze 
the content later this week when dependency update round succeed with the 
needed fixes

[17:04:35] <+jaheikki3> The previous one had bugs preventing us to produce all 
packages

[17:04:51] <+jaheikki3> Current estimation for beta3 release is Tue 22nd August

[17:05:30] <+jaheikki3> API Change review is still ongoing, see 
https://lists.qt-project.org/pipermail/development/2023-August/044267.html

[17:06:04] <+jaheikki3> open reviews updated recently

[17:06:24] <+jaheikki3> Soft string freeze in effect now, see 
https://lists.qt-project.org/pipermail/localization/2023-August/000578.html

[17:06:46] <+jaheikki3> that's all at this time. Any comments or questions?

[17:07:04]  sorry, I was late

[17:07:37] <+jaheikki3> thiago: no problem. We are already pretty much done :D

[17:08:23]  yep

[17:08:35] -*- thiago is looking after a bug in QSharedMemory but not much 
progress yet

[17:08:43]  probably my fault

[17:10:39] <+jaheikki3> Ok, it was all at this time. I can't join next week so 
let's have next meeting Tue 29th August at this same time

[17:10:48] <+jaheikki3> thanks for your participation, bye!

[17:10:54]  thanks

[17:11:52]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS-UP: Qt 6.6 API change review

[Jani Heikkinen via Development]

Hi all! 

There are still many reviews open; please help to review and fix findings to 
complete the review

Open ones
qtbase
* https://codereview.qt-project.org/c/qt/qtbase/+/481745 Widgets: API 
comparison from v6.5.0 to 6.6 in qtbase
* https://codereview.qt-project.org/c/qt/qtbase/+/481746 
https://codereview.qt-project.org/c/qt/qtbase/+/481746Core: API comparison from 
v6.5.0 to 6.6 in qtbase
* https://codereview.qt-project.org/c/qt/qtbase/+/481747 Sql: API comparison 
from v6.5.0 to 6.6 in qtbase
* https://codereview.qt-project.org/c/qt/qtbase/+/481748 Gui: API comparison 
from v6.5.0 to 6.6 in qtbase

qtconnectivity
* https://codereview.qt-project.org/c/qt/qtconnectivity/+/481758 Bluetooth: API 
comparison from v6.5.0 to 6.6 in qtconnectivity

qtdeclarative
* https://codereview.qt-project.org/c/qt/qtdeclarative/+/481751 Quick: API 
comparison from v6.5.0 to 6.6 in qtdeclarative
* https://codereview.qt-project.org/c/qt/qtdeclarative/+/495734 qtdeclarative 
6.6 QML API Review

qtopcua
* https://codereview.qt-project.org/c/qt/qtopcua/+/481774 OpcUa: API comparison 
from v6.5.0 to 6.6 in qtopcua

qt3d
* https://codereview.qt-project.org/c/qt/qt3d/+/495763 qt3d 6.6 QML API Review

qtquick3d
* https://codereview.qt-project.org/c/qt/qtquick3d/+/482617 qtquick3d 6.6 QML 
API Review

qtwayland
* https://codereview.qt-project.org/c/qt/qtwayland/+/495768 qtwayland 6.6 QML 
API Review

qtwebengine
* https://codereview.qt-project.org/c/qt/qtwebengine/+/481763 PdfWidgets: API 
comparison from v6.5.0 to 6.6 in qtwebengine
* https://codereview.qt-project.org/c/qt/qtwebengine/+/481764 WebEngineCore: 
API comparison from v6.5.0 to 6.6 in qtwebengine
* https://codereview.qt-project.org/c/qt/qtwebengine/+/481765 WebEngineQuick: 
API comparison from v6.5.0 to 6.6 in qtwebengine
* https://codereview.qt-project.org/c/qt/qtwebengine/+/481766 Pdf: API 
comparison from v6.5.0 to 6.6 in qtwebengine
* https://codereview.qt-project.org/c/qt/qtwebengine/+/495983 qtwebengine 6.6 
QML API Review

qtwebchannel
* https://codereview.qt-project.org/c/qt/qtwebchannel/+/482624 qtwebchannel 6.6 
QML API Review

br
Jani Heikkinen

> -Original Message-
> From: Jani Heikkinen
> Sent: keskiviikko 7. kesäkuuta 2023 13.46
> To: development@qt-project.org
> Subject: HEADS-UP: Qt 6.6 API change review
> 
> Hi!
> 
> Qt 6.6 API Change Review is started & generated diffs are here:
> https://codereview.qt-project.org/q/topic:%2522api-change-review-
> 6.6%2522+(status:open+OR+status:merged) <https://codereview.qt-
> project.org/q/topic:%2522api-change-review-
> 6.6%2522+(status:open+OR+status:merged)>
> There is also a task in Jira: https://bugreports.qt.io/browse/QTBUG-114214
> Please review diffs as soon as possible.
> 
> br,
> Jani
> 
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS UP : Qt 6.6 soft string freeze

[Jani Heikkinen via Development]

Hi all,

First beta releases from Qt 6.6 are out and it is time to start keeping 
translatable strings as it is. The official string freeze for Qt 6.6 will be in 
effect Tue 22nd of August 2023.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 08.08.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

  *   Qt 6.5.2 was released 19th of July
  *   Qt 6.5.3 release preparations are started. The target is to release Qt 
6.5.3 ~mid September 2023

Qt 6.6 status:

  *   Qt 6.6 Beta2 was released mid July
  *   Qt 6.6 Beta3 preparations are ongoing
 *   Target is to release beta3 ~mid August 2023
  *   Qt 6.6 API change review still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214
 *   C++ API changes are already updated & updating QML ones is ongoing
 *   Hoping we can close remaining reviews soon
  *   Qt 6.6 String freeze will be in effect 22nd August
 *   soft string freeze will be announced Tue 15th of August

Next meeting Tue 15th August 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:31]  akseli: carewolf: frkleint: lars_:mapaaso: The-Compiler: 
thiago: vohi: ping
[17:00:46]  jaheikki3: pong
[17:01:45]  Time to start qt release team meeting
[17:01:52]  on agenda today:
[17:01:55]  Qt 6.5 status
[17:01:59]  Qt 6.6 status
[17:02:07]  Any additional item to the agenda?
[17:02:33]  pong
[17:03:23]  Let's start from Qt 6.5 status:
[17:03:50]  Qt 6.5.2 was released 19th of July
[17:04:21]  Qt 6.5.3 release preparations are started
[17:04:39]  Target is to release Qt 6.5.3 ~mid September 2023
[17:04:46]  That'
[17:05:03]  s actually all about Qt 6.5.3 status at this time. Any 
comments or questions?
[17:05:42]  sounds good
[17:06:39]  Then Qt 6.6 status:
[17:07:04]  Qt 6.6 Beta2 was released mid July
[17:07:18]  Qt 6.6 Beta3 preparations are ongoing
[17:07:33]  The target is to release beta3 ~mid August 2023
[17:07:50]  Qt 6.6 API change review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214
[17:08:19]  C++ API changes already updated & updating QML ones 
ongoing
[17:08:46]  I am hoping we can close remaining reviews really soon
[17:09:02]  Qt 6.6 String freeze will be in effect 22nd of August
[17:09:15]  so soft string freeze will be announced Tue 15th of 
August
[17:09:41]  That's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:10:15]  sounds good
[17:10:53]  Great! It was all at this time so let's end this meeting 
now & have next one Tue 15th August at this same time.
[17:11:05]  Thanks for your participation, bye!
[17:11:13]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 20.06.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

-  Branching from '6.5' to '6.5.2' done

- Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt 6.5.2 
content later this week

- The target is to release Qt 6.5.2 Wed 28th June

Qt 6.6 status:

- Qt 6.6.0 Beta1 released

- Target is to release Qt 6.6.0 Beta2 ~Mid July

- Qt 6.6 API change review ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214

Next meeting Tue 1st of August 16:00 CET

br,

Jani Heikkinen

Release Manager

irc log below:
[17:00:10]  akseli: carewolf: frkleint: lars_:mapaaso: The-Compiler: 
thiago: vohi: ping
[17:00:18]  pong
[17:00:20]  jaheikki3: pong
[17:00:57]  Time to start qt release team meeting
[17:01:03]  on agenda today:
[17:01:06]  Qt 6.5 status
[17:01:09]  Qt 6.6 status
[17:01:30]  Any additional item to the agenda?
[17:02:44]  Let's start from Qt 6.5 status
[17:02:58]  Branching from '6.5' to '6.5.2' done
[17:03:13]  Qt 6.5.2 content is not frozen yet but the target is to 
freeze the Qt 6.5.2 content later this week
[17:03:35]  The target is to release Qt 6.5.2 Wed 28th June
[17:04:15]  That might be a bit tight schedule because of midsummer 
fest and holiday season but let's try
[17:04:46]  That's all about Qt 6.5 status at this time. Any 
comments or questions?
[17:06:20]  Then Qt 6.6 status:
[17:06:30]  Qt 6.6.0 Beta1 released
[17:06:42]  the target is to release Qt 6.6.0 Beta2 ~Mid July
[17:07:01]  Qt 6.6 API change review is still ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214
[17:07:27]  I pushed updates just before this meeting
[17:07:52]  That's actually all about 6.6 status at this time. Any 
comments or questions?
[17:10:10]  Let's then end this meeting now. I will start my summer 
vacation this Thu so let's have next meeting after it, 1st of August, at this 
same time
[17:10:21]  Thanks for your participation, bye!
[17:10:23]  enjoy your holidays!
[17:10:39]  Thanks, will do :D
[17:10:42]  bye, have a nice holiday
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Heads-up: what's new in '6.6' doc needs your updates

[Jani Heikkinen via Development]

Hi all,
https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc 
seems to be quite unfinished ☹ It would be good to get some more content there 
for Qt 6.6 Beta1 (which is planned to happen during this week). So please do at 
least most important updates now; finalizing and polishing can then happen 
later in beta phase.

br,
Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.5' to '6.5.2' done

[Jani Heikkinen via Development]

Hi!

We have branched '6.5.2' from '6.5' now. So from now on all changes targeted to 
Qt 6.5.2 release must have 'Pick-to: 6.5.2' and '6.5' is for Qt 6.5.3 release. 
As usual staging in '6.5.2' is restricted to release team only and we will 
monitor incoming changes automatically.

Target is to release Qt 6.5.2 Wed 28th June so the content for Qt 6.5.2 release 
will be frozen latest Thu 22nd June (but preferably already earlier)

br,
Jani Heikkinen
Release Manager
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 13.06.2023

[Jani Heikkinen via Development]

Qt 6.5 status:

- Qt 6.5.2 preparations are ongoing

   * Branching from '6.5' to '6.5.2' will happen Wed 14th June

   * The plan is to release Qt 6.5.2 Wed 28th June -> Qt 6.5.2 content will be 
frozen Thu 22nd June



Qt 6.6 status:
- Qt 6.6.0 Beta1 preparations are ongoing
   * Beta1 content is frozen
   * Target is to release Qt 6.6.0 Beta1 later this week
- Qt 6.6 API change review ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214

Next meeting Tue 20th June 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:13] <+jaheikki3> ablasche: akseli: carewolf: frkleint: lars_:mapaaso: 
The-Compiler: thiago: vohi: ping
[17:01:35]  jaheikki3: pong
[17:02:03] <+jaheikki3> time to start qt release team meeting
[17:02:09] <+jaheikki3> On agenda today:
[17:02:12] <+jaheikki3> Qt 6.5 status
[17:02:15] <+jaheikki3> Qt 6.6 status
[17:02:21] <+jaheikki3> Any additional item to the agenda?
[17:04:06] <+jaheikki3> Ok, lets start from Qt 6.5 status
[17:04:51] <+jaheikki3> Qt 6.5.2 preparations ongoing
[17:05:11] <+jaheikki3> Branching from '6.5' to '6.5.2' will happen wed 14th 
June
[17:06:12] <+jaheikki3> the plan is to release Qt 6.5.2 Wed 28th June so 
release content will be frozen thu 22nd June
[17:06:32] <+jaheikki3> That's pretty much all about Qt 6.5 status at this 
time. Any comments or questions?
[17:06:57]  I'm a bit worried about 
https://bugreports.qt.io/browse/QTBUG-114334 - it seems like a rather bad 
regression in Qt 6.5.1 to me (any Qt application crashes when 
connecting/disconnecting an input device and then using the touchscreen or a 
touchpad). I was able to exactly pinpoint the bug (see my latest comment 
there), but I'm unable to fix it myself (maybe with some help), but haven't 
heard back
[17:07:00]  so far.
[17:07:22]  (Linux/X11 only, but still meh)
[17:08:24] <+jaheikki3> The-Compiler: Ok, thanks for pointing this one. I'll 
check if Shawn could fix the issue
[17:09:48] <+jaheikki3> Ok, then Qt 6.6 status
[17:11:24] <+jaheikki3> Qt 6.6.0 Beta1 preparations ongoing
[17:11:41] <+jaheikki3> Beta1 content is frozen and package creation ongoing
[17:12:03] <+jaheikki3> Target is to release beta1 later this week
[17:12:34] <+jaheikki3> Qt 6.6 API change review ongoing, see 
https://bugreports.qt.io/browse/QTBUG-114214
[17:13:10] <+jaheikki3> That's actually all about Qt 6.6 status at this time. 
Any comments or questions?
[17:14:38] <+jaheikki3> It was all at this time so let's end this meeting now & 
have new one tue 20th June at this same time
[17:14:47] <+jaheikki3> Thanks for your participation, bye!
[17:14:49]  thanks
[17:15:14]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.6 API change review

[Jani Heikkinen via Development]

Hi!



Qt 6.6 API Change Review is started & generated diffs are here: 
https://codereview.qt-project.org/q/topic:%2522api-change-review-6.6%2522+(status:open+OR+status:merged)

There is also a task in Jira: https://bugreports.qt.io/browse/QTBUG-114214

Please review diffs as soon as possible.



br,

Jani

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Meeting minutes from Qt Release Team meeting 06.06.2023

[Jani Heikkinen via Development]

Hi!

Yes, that's true. Sorry for confusion!

So once again:
3 Qt 6.6 FF exception requests so far:
* container-assign epic: exception request accepted
* C++20 comparison: exception request rejected
* QMultiMap/Hash support in Qvariant: exception request rejected

br,
Jani Heikkinen
Release manager

> -Original Message-
> From: Ivan Solovev 
> Sent: keskiviikko 7. kesäkuuta 2023 9.13
> To: releas...@qt-project.org; development@qt-project.org; Jani Heikkinen
> 
> Subject: Re: Meeting minutes from Qt Release Team meeting 06.06.2023
> 
> Hi Jani,
> 
> > 3 exception requests so far:
> >  - C++20 comparison: exception request accepted
> >  - container-assign epic: exception request rejected
> 
> 
> I think it's the other way around - the container-assign epic is accepted, and
> the C++20 comparison is rejected.
> 
> 
> Best regards,
> Ivan
> 
> 
> 
> 
> Ivan Solovev
> 
> Senior Software Engineer
> 
> 
> 
> 
> The Qt Company GmbH
> Erich-Thilo-Str. 10
> 12489 Berlin, Germany
> 
> ivan.solo...@qt.io <mailto:ivan.solo...@qt.io>
> 
> www.qt.io <https://www.qt.io>
> 
> 
> 
> 
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Jouni Lintunen
> Sitz der Gesellschaft: Berlin,
> Registergericht: Amtsgericht
> Charlottenburg, HRB 144331 B
> 
> 
> 
> 
> 
> From: Development  on behalf of
> Jani Heikkinen via Development 
> Sent: Wednesday, June 7, 2023 7:20 AM
> To: releas...@qt-project.org ; development@qt-
> project.org 
> Subject: [Development] Meeting minutes from Qt Release Team meeting
> 06.06.2023
> 
> 
> Qt 6.5 status
> 
> * Qt 6.5.2 preparations started
> 
>   *   First internal snapshot created and tested
>   *   Target is to branch from '6.5' to '6.5.2' Wed 14th
> June
>   *   Target is to release Qt 6.5.2 Wed 28th June
> 
> Qt 6.6 status
> 
> * Qt 6.6 Feature Freeze in effect now & branching from 'dev' to
> '6.6' done
> 
>   *   3 exception requests so far:
> 
>   *   C++20 comparison: exception
> request accepted
>   *   container-assign epic: exception
> request rejected
>   *   QMultiMap/Hash support in
> Qvariant: exception request rejected
> 
> * API change review started
> 
>   *   Most of diffs already available, see
> https://bugreports.qt.io/browse/QTBUG-114214
>   *   Official review call will be sent to dev ML later
> this week
> 
> * Target is to release Qt 6.6 Beta1 immediately after dependency
> update round succeed in '6.6'
> 
> 
> 
> Next meeting Tue 13th June 16:00 CET
> 
> 
> 
> br,
> 
> Jani Heikkinen
> 
> Release Manager
> 
> 
> 
> 
> 
> irc log below
> 
> [17:00:13] <+jaheikki3> ablasche: akseli: carewolf_home: lars_:mapaaso:
> The-Compiler:thiago:vohi: ping
> 
> [17:00:23]  jaheikki3: pong
> 
> [17:00:24]  pong
> 
> [17:00:26]  pong
> 
> [17:00:35]  pong
> 
> [17:00:37]  jaheikki3: pong
> 
> [17:01:17] <+jaheikki3> time to start qt release team meeting
> 
> [17:01:23] <+jaheikki3> on agenda today:
> 
> [17:01:29] <+jaheikki3> Qt 6.5 status
> 
> [17:01:33] <+jaheikki3> Qt 6.6 status
> 
> [17:01:42] <+jaheikki3> Any additional item to the agenda?
> 
> [17:01:57]  Lets discuss the requested exceptions from Qt 6.6 feature
> freeze
> 
> [17:02:54]  (as part of the Qt 6.6 status)
> 
> [17:03:06] <+jaheikki3> vohi: Yes, agree
> 
> [17:03:19] <+jaheikki3> But let's start from Qt 6.5 status
> 
> [17:03:36] <+jaheikki3> Qt 6.5.2 preparations started
> 
> [17:03:54] <+jaheikki3> First snapshot created and tested
> 
> [17:04:13] <+jaheikki3> Target is to release Qt 6.5.2 Wed 28th June
> 
> [17:04:36] <+jaheikki3> So branching from '6.5' to '6.5.2' will happen Wed
> 14th June
> 
> [17:05:00] <+jaheikki3> that's all about Qt 6.5 status. Any comments or
> questions?
> 
> [17:06:27]  none
> 
> [17:06:48] <+jaheikki3> Ok, then Qt 6.6 status
> 
> [17:07:02] <+jaheikki3> Qt 6.6 Feature Freeze is in effect now
> 
> [17:07:13] <+jaheikki3> 3 Exception requests so far:
> 
> [17:07:33] <+jaheikki3> C++20 comparison, container-assign epic &
> QMultiMap/Hash support in Qvariant
> 
> [17:07:42] <+jaheikki3> vohi:
> 
> [17:08:01]  container-assign seems pretty clear cut.
> 
> [17:08:07]  greed
&

[Development] Meeting minutes from Qt Release Team meeting 06.06.2023

[Jani Heikkinen via Development]

Qt 6.5 status

  *   Qt 6.5.2 preparations started
 *   First internal snapshot created and tested
 *   Target is to branch from '6.5' to '6.5.2' Wed 14th June
 *   Target is to release Qt 6.5.2 Wed 28th June
Qt 6.6 status

  *   Qt 6.6 Feature Freeze in effect now & branching from 'dev' to '6.6' done
 *   3 exception requests so far:
*   C++20 comparison: exception request accepted
*   container-assign epic: exception request rejected
*   QMultiMap/Hash support in Qvariant: exception request rejected
  *   API change review started
 *   Most of diffs already available, see 
https://bugreports.qt.io/browse/QTBUG-114214
 *   Official review call will be sent to dev ML later this week
  *   Target is to release Qt 6.6 Beta1 immediately after dependency update 
round succeed in '6.6'

Next meeting Tue 13th June 16:00 CET

br,
Jani Heikkinen
Release Manager


irc log below
[17:00:13] <+jaheikki3> ablasche: akseli: carewolf_home: lars_:mapaaso: 
The-Compiler:thiago:vohi: ping
[17:00:23]  jaheikki3: pong
[17:00:24]  pong
[17:00:26]  pong
[17:00:35]  pong
[17:00:37]  jaheikki3: pong
[17:01:17] <+jaheikki3> time to start qt release team meeting
[17:01:23] <+jaheikki3> on agenda today:
[17:01:29] <+jaheikki3> Qt 6.5 status
[17:01:33] <+jaheikki3> Qt 6.6 status
[17:01:42] <+jaheikki3> Any additional item to the agenda?
[17:01:57]  Lets discuss the requested exceptions from Qt 6.6 feature 
freeze
[17:02:54]  (as part of the Qt 6.6 status)
[17:03:06] <+jaheikki3> vohi: Yes, agree
[17:03:19] <+jaheikki3> But let's start from Qt 6.5 status
[17:03:36] <+jaheikki3> Qt 6.5.2 preparations started
[17:03:54] <+jaheikki3> First snapshot created and tested
[17:04:13] <+jaheikki3> Target is to release Qt 6.5.2 Wed 28th June
[17:04:36] <+jaheikki3> So branching from '6.5' to '6.5.2' will happen Wed 14th 
June
[17:05:00] <+jaheikki3> that's all about Qt 6.5 status. Any comments or 
questions?
[17:06:27]  none
[17:06:48] <+jaheikki3> Ok, then Qt 6.6 status
[17:07:02] <+jaheikki3> Qt 6.6 Feature Freeze is in effect now
[17:07:13] <+jaheikki3> 3 Exception requests so far:
[17:07:33] <+jaheikki3> C++20 comparison, container-assign epic & 
QMultiMap/Hash support in Qvariant
[17:07:42] <+jaheikki3> vohi:
[17:08:01]  container-assign seems pretty clear cut.
[17:08:07]  greed
[17:08:09]  agreed
[17:09:28]  THe C++20 comparison less so, obviously. The discussion with 
Ivan has confirmed that this isn't needed for Qt 6.6, and given that the header 
review process has started, I don't quite see why we need to make an exception 
here. I respect that a lot of thought and work has gone into the implementation 
of course.
[17:11:21]  Since we won't make C++20 a requirement for Qt 6.6, and 
generally don't plan to make C++20 support on any level a part of the launch 
communication, I'm not quite seeing why we need to make an exception. The scope 
of what has been done is small, and I somewhat share Thiago's concern that 
maybe it's too small for us to see all the corner cases.
[17:13:14] <+jaheikki3> I understand and agree; we shouldn't make an exception 
for this because it isn't needed nesessarily for Qt 6.6
[17:14:03] <+jaheikki3> Any objections?
[17:14:27]  no
[17:14:32]  Alex is right in saying that we don't need to roll this out 
across all relevant types in all submodules, but a bit more than the two or 
three cases in Qt Core alone wouldn't hurt.
[17:15:36]  I think we need as a validation that it works
[17:15:53]  he has 5 types currently (the 4 date/time types and 
qfloat16)
[17:17:26] <+jaheikki3> It seems we agree no exception for the C++20 comparison
[17:17:44] <+jaheikki3> vohi: what about the last one (QMultiMap/Hash support 
in Qvariant)?
[17:18:17]  is there a timeframe mentioned?
[17:19:20]  no; Peppe doesn't know how to continue based on Thiago's 
input, so it's a bit open
[17:20:11]  We changed behavior, unintentionally perhaps, from Qt 5 to Qt 
6 by making QMultiMap no longer a QMap subclass (ditto QHash)
[17:20:56]  but since no API in Qt uses QVariantMap/Hash as a 
multi-map/hash, it's gone unnoticed. At least I assume that Peppe's motivation 
to bring them back is the respective question on 
inter...@qt-project.org<mailto:inter...@qt-project.org>
[17:21:16]  
(https://lists.qt-project.org/pipermail/interest/2023-April/039055.html
[17:21:52]  with out a plan I would lean towards no, it has been 
broken for a long time so 6.6 vs 6.7 doesn't make much difference
[17:22:26]  we should perhaps establish first that we need those types to 
be built-in types in Qt at all; we don't use them in Qt ourselves
[17:23:16]  I don't think it makes a difference if it get

[Development] HEADS-UP: Branching from 'dev' to '6.6' done

[Jani Heikkinen via Development]

Hi!
Qt 6.6 Feature Freeze is in effect now! We have also branched '6.6' from the 
'dev'.  So from now on all changes targeted to Qt 6.6 must have 'Pick-to: 6.6' 
and 'dev' is for Qt 6.7.

br,
Jani Heikkinen
Release Manager

> -Original Message-----
> From: Development  On Behalf Of
> Jani Heikkinen via Development
> Sent: perjantai 2. kesäkuuta 2023 14.40
> To: development@qt-project.org
> Subject: [Development] HEADS-UP: Qt 6.6 Feature Freeze will be in effect
> soon
> 
> Hi all,
> 
> Just a reminder: Qt 6.6 Feature Freeze will be in effect today. As earlier you
> can continue staging ready changes (== ones having +2 today) during the
> weekend as well. But if new feature isn't ready today you need to get the
> exception to get it in Qt 6.6.
> 
> The target is to branch from 'dev' to '6.6' on Monday 5th June.
> 
> br,
> Jani Heikkinen
> Release Manager
> 
> > -Original Message-
> > From: Jani Heikkinen
> > Sent: tiistai 18. huhtikuuta 2023 9.07
> > To: development@qt-project.org
> > Subject: HEADS-UP: Qt 6.6 Feature Freeze is getting closer
> >
> > Hi all,
> >
> >
> >
> > Just a kindly reminder: Qt 6.6 Feature freeze will be in effect 2nd of
> > June
> > 2023 and Qt 6.6 platform and module freeze 19th of May 2023, see
> > https://wiki.qt.io/Qt_6.6_Release
> >
> >
> >
> > Please inform me about all new modules planned to be released in Qt
> > 6.6; we should start adding those in CI & packages asap.
> >
> > Also please inform me if existing technology preview module will be
> > officially supported etc.
> >
> >
> >
> > br,
> >
> > Jani
> >
> >
> 
> --
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Qt 6.6 Feature Freeze will be in effect soon

[Jani Heikkinen via Development]

Hi all,

Just a reminder: Qt 6.6 Feature Freeze will be in effect today. As earlier you 
can continue staging ready changes (== ones having +2 today) during the weekend 
as well. But if new feature isn't ready today you need to get the exception to 
get it in Qt 6.6.

The target is to branch from 'dev' to '6.6' on Monday 5th June.

br,
Jani Heikkinen
Release Manager

> -Original Message-
> From: Jani Heikkinen
> Sent: tiistai 18. huhtikuuta 2023 9.07
> To: development@qt-project.org
> Subject: HEADS-UP: Qt 6.6 Feature Freeze is getting closer
> 
> Hi all,
> 
> 
> 
> Just a kindly reminder: Qt 6.6 Feature freeze will be in effect 2nd of June
> 2023 and Qt 6.6 platform and module freeze 19th of May 2023, see
> https://wiki.qt.io/Qt_6.6_Release
> 
> 
> 
> Please inform me about all new modules planned to be released in Qt 6.6;
> we should start adding those in CI & packages asap.
> 
> Also please inform me if existing technology preview module will be officially
> supported etc.
> 
> 
> 
> br,
> 
> Jani
> 
> 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 23.05.2023

[Jani Heikkinen via Development]

Qt 6.5 status

  *   Qt 6.5.1 packages are ready and we will release Qt 6.5.1 Wed 24th May
  *   Target is to release Qt 6.5.2 at the end of June and Qt 6.5.3 at the 
beginning of September


Qt 6.6 status

  *   Platform and Module freeze is in effect so no provisioning changes to the 
'dev' until '6.6' is branched
  *   Dependency update issues in dev are fixed & dependencies updated 
regularly atm
 *   New snapshot from dev created but not published yet
  *   Qt 6.6 Feature Freeze will be in effect Fri 2nd June
 *   Like earlier you can still stage changes in 'dev' during the weekend 
if changes were ready and approved latest on Friday 2nd June.
 *   Volker is on vacation from Friday 26th May on and back on the 5th of 
June, so great if anyone that knows that they need an exception can raise that 
this week.
  *   Target is to branch '6.6' from 'dev' Monday 5th of June
  *   Target is to publish Qt 6.6.0 Beta1 immediately when dependency update 
round succeed in '6.6'
  *   API change review will start after branching as well

Next meeting Tue 30th May 2023 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:01:29] <+jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso: 
The-Compiler: vohi: thiago ping
[17:01:36]  pong
[17:01:41]  jaheikki3: pong
[17:03:18] <+jaheikki3> time to start qt release team meeting
[17:03:24] <+jaheikki3> On agenda today:
[17:03:27] <+jaheikki3> Qt 6.5 status
[17:03:32] <+jaheikki3> Qt 6.6 status
[17:03:39] <+jaheikki3> Any additional item to the agenda?
[17:04:57] <+jaheikki3> Ok, Qt 6.5 status at first
[17:05:18] <+jaheikki3> Qt 6.5.1 packages are ready and we will release Qt 
6.5.1 tomorrow
[17:05:44] <+jaheikki3> Target is to release Qt 6.5.2 at the end of June and Qt 
6.5.3 beginning of September
[17:05:55]  jaheikki3: pong
[17:06:34] <+jaheikki3> that's actually all about qt 6.5 status at this time. 
Any comments or questions?
[17:08:00] <+jaheikki3> Ok, then Qt 6.6 status
[17:08:25] <+jaheikki3> Qt 6.6.0 Platform and Module freeze is in effect now so 
no provisioning changes to the 'dev' until '6.6' is branched
[17:08:53] <+jaheikki3> Dependency update issues in dev are fixed & 
dependencies updated regularly atm
[17:09:51] <+jaheikki3> New snapshot from dev created but not published yet; 
there seems to be some issue with QtC and we want to fix/flarify it before 
publishing the snapshot
[17:10:11] -*- thiago still has API fixes for 6.6 he hasn't properly finished
[17:10:48] <+jaheikki3> thiago: That's OK; Qt 6.6 Feature Freeze will be in 
effect Fri 2nd June so almost 2 weeks time to finalize those
[17:11:43]  I'm on vacation from Friday on and back on the 5th, so great 
if anyone that knows that they need an exception can raise that this week.
[17:11:44] <+jaheikki3> and like earlier ready changes can be staged in 'dev' 
during the weekend after FF
[17:12:20] <+jaheikki3> But only if changes were ready and approved latest 
during Friday 2nd June
[17:12:35] <+jaheikki3> Otherwise exception needs to be asked
[17:12:38]  we're not freezing API, only features
[17:12:44]  so we can still change API
[17:12:49]  Feature freeze != API freeze anyway, we do assume that we 
will make changes to the API based on header review feedback and API reviews
[17:13:07] <+jaheikki3> thiago: vohi: yeah, true
[17:13:16] <+jaheikki3> my mistake, sorry
[17:14:00] <+jaheikki3> The target is to branch '6.6' from 'dev' Monday 5th June
[17:14:16] <+jaheikki3> API change review will start after branching
[17:14:36] <+jaheikki3> and the target is to publish Qt 6.6.0 Beta1 immediately 
when dependency update round succeed in '6.6'
[17:15:07] <+jaheikki3> That's actially all about qt 6.6 status at this time. 
Any more comments or questions
[17:16:20]  In the week of the 5th, the R&D teams in TQtC will start a 
focused bug fixing week or two or three to catch up with stuff in JIRA
[17:17:26]  If anyone wants to help, or has particular bugs that they are 
keen on getting fixed, then updating JIRA tickets, adding reproducers, trying 
to reproduce etc is a good way to contribute
[17:17:46]  (and of course fixing things and writing tests)
[17:19:12] <+jaheikki3> It seems it was all at this time so let's end this 
meeting now and have new one tue 30th May at this same time.
[17:19:28] <+jaheikki3> Thanks for your participation, bye!
[17:19:38]  bye
[17:19:42]  bye
[17:22:28]  bye

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS-UP: Qt 6.6 Feature Freeze is getting closer

[Jani Heikkinen via Development]

Hi Everyone!

Qt 6.6 Platform and Module Freeze is in effect now! 

br,
Jani

> -Original Message-
> From: Development  On Behalf Of
> Jani Heikkinen via Development
> Sent: tiistai 9. toukokuuta 2023 7.57
> To: development@qt-project.org
> Subject: Re: [Development] HEADS-UP: Qt 6.6 Feature Freeze is getting closer
> 
> Hi,
> 
> Only less than 2 weeks to 'Platform and Module' freeze and  ~ a month to
> official feature freeze. So it is time
> - to inform me about new modules coming in Qt 6.6
>* Qt Graphs is only known one atm
> - to inform me if some 'TP' module will be officially supported in Qt 6.6
> - to start updating new features etc in 'What' new in Qt 6.6' wiki
>*
> https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qd
> oc
> 
> br,
> Jani
> 
> > -Original Message-
> > From: Jani Heikkinen
> > Sent: tiistai 18. huhtikuuta 2023 9.07
> > To: development@qt-project.org
> > Subject: HEADS-UP: Qt 6.6 Feature Freeze is getting closer
> >
> > Hi all,
> >
> >
> >
> > Just a kindly reminder: Qt 6.6 Feature freeze will be in effect 2nd of
> > June
> > 2023 and Qt 6.6 platform and module freeze 19th of May 2023, see
> > https://wiki.qt.io/Qt_6.6_Release
> >
> >
> >
> > Please inform me about all new modules planned to be released in Qt
> > 6.6; we should start adding those in CI & packages asap.
> >
> > Also please inform me if existing technology preview module will be
> > officially supported etc.
> >
> >
> >
> > br,
> >
> > Jani
> >
> >
> 
> --
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 16.05.2023

[Jani Heikkinen via Development]

Qt 6.5 status

  *   Qt 6.5.1 release content is finally frozen and package creation is ongoing
  *   Target is to release Qt 6.5.1 Wed 24th May

Qt 6.6 status

  *   There is still issues with dependency update round -> no new snapshot 
from dev since mid April
 *   Submodule dependencies has been updated lately but qt5.git waits the 
update
  *   Platform and Module freeze will be in effect this Friday
 *   It seems only new module for Qt 6.6 is Qt Graphs



Next meeting Tue 23rd May 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:
[17:00:16] <+jaheikki3> ablasche: akseli: carewolf: frkleint:lars_: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:46]  jaheikki3: pong
[17:00:53]  jaheikki3: pong
[17:01:31] <+jaheikki3> time to start qt release team meeting
[17:01:36] <+jaheikki3> On agenda today:
[17:01:39] <+jaheikki3> Qt 6.5 status
[17:01:42] <+jaheikki3> Qt 6.6 status
[17:01:50] <+jaheikki3> Any additional item to the agenda?
[17:02:12]  jaheikki3: pong
[17:03:11] <+jaheikki3> Let's start from Qt 6.5 status:
[17:03:32] <+jaheikki3> Qt 6.5.1 release content is finally frozen
[17:03:48] <+jaheikki3> Updating dependencies is ongoing
[17:04:20] <+jaheikki3> Package creation will start when dependecy update round 
is done
[17:05:24] <+jaheikki3> Target is to release Qt 6.5.1 Wed 24th May or maybe mon 
or tue next week if we are ready earlier
[17:05:54] <+jaheikki3> That's all about 6.5 status at this time. Any comments 
or questions?
[17:06:45]  we have another open security report
[17:06:53]  are we going to wait for the patch for 6.5.1?
[17:07:41] <+jaheikki3> thiago: It seems it isn't ready yet so I think we 
shouldn't wait it anymore
[17:09:03] <+jaheikki3> The fix for it will be in Qt 6.5.2 and patch will be 
available for Qt 6.5.1 and Qt 6.5.0 users
[17:09:12]  ok
[17:09:52] <+jaheikki3> Ok, then Qt 6.6 status
[17:10:35] <+jaheikki3> Unfortunately no new snapshot yet; still issues with 
dependency update round
[17:11:10] <+jaheikki3> submodule dependencies has been updated lately but 
qt5.git waits the update
[17:11:44]  has the problem with provisioning been resolved?
[17:11:55] <+jaheikki3> Fixes should be in place but with the last try both got 
confuced and didn't use the correct SHA1s
[17:12:27] <+jaheikki3> carewolf: I don't know any open provisioning related 
issues atm
[17:12:39]  ok
[17:13:27] <+jaheikki3> Qt 6.6 platform and module freeze will be effect this 
Friday
[17:13:47] <+jaheikki3> It seems only new module for Qt 6.6 is Qt Graphs
[17:14:18] <+jaheikki3> that's all about Qt 6.6 status at this time. Any 
comments or questions?
[17:16:33] <+jaheikki3> Ok, it was all at this time so let's end the meeting 
now & have new one tue 23rd May at this same time
[17:16:48] <+jaheikki3> Thanks for your participation, bye!
[17:19:57]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 09.05.2023

[Jani Heikkinen via Development]

Qt 6.5 status

  *   Qt 6.5.1 content is not frozen yet
 *   the last changes are integrating.
 *   Target is to freeze the release content later this week
  *   Target is to release Qt 6.5.1 during next week

Qt 6.6 status

  *   Unfortunately no new snapshot available yet.
 *   No successfully submodule update available
 *   Target is to update existing one immediately after successfully 
submodule update
  *   NOTE: Please review new API as soon as you think you are done; do not 
wait for header review
 *   Focus on header review should be checking things for technical errors 
(like bc breakage),
discussion about API design and naming and such should be done much earlier.



Next meeting Tue 16th May 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:
[17:00:00] <+jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:09]  poing
[17:01:13] <+jaheikki3> time to start qt release team meeting
[17:01:21] <+jaheikki3> on agenda today:
[17:01:25] <+jaheikki3> Qt 6.5 status
[17:01:31] <+jaheikki3> Qt 6.6 status
[17:01:43] <+jaheikki3> Any additional item to the agenda?
[17:03:03] <+jaheikki3> Let's start from Qt 6.5 status:
[17:03:23] <+jaheikki3> Qt 6.5.1 content not frozen yet
[17:03:54] <+jaheikki3> But the last changes are integrating
[17:04:15] <+jaheikki3> target is to freeze the release content later this week
[17:04:35] <+jaheikki3> and the target is to release Qt 6.5.1 during next week
[17:05:03] <+jaheikki3> That's all about Qt 6.5 status at this time. Any 
comments or questions?
[17:05:26]  sounds good
[17:06:18] <+jaheikki3> great, then Qt 6.6 status
[17:06:42] <+jaheikki3> Actually the status is pretty much the same as last week
[17:07:05] <+jaheikki3> Unfortunately no new snapshot available yet
[17:07:26] <+jaheikki3> because there isn't successfully submodule update 
available
[17:07:49] <+jaheikki3> All known issues should be fixed & round ongoing
[17:08:05] <+jaheikki3> But it will take a while; CI is under heavy load at the 
moment
[17:08:41] <+jaheikki3> But the target is to update the snapshot immediately 
after successfully dependency update round
[17:09:11] <+jaheikki3> That's actually all about qt 6.6 status at this time. 
Any comments or questions?
[17:09:49]  any update on when we would do start API review for 6.6? 
There was talk about starting it earlier
[17:10:08] <+jaheikki3> vohi: any comments from your side for that?
[17:10:30]  I think we should not abuse the header review process for API 
review. If there's new API, review those as soon as you think you are done.
[17:11:25]  I liked what the build system team did a while ago with a 
public review of cmake APIs, inviting anyone to the meeting. Perhaps that 
doesn't always scale/make sense, but more of that wouldn't hurt
[17:11:38]  that's how it used to be
[17:11:47]  the request was for the header review. Specifically from 
marc, who thought it got a bit stressy with 6.5
[17:11:48]  API review at feature freeze, header review after beta
[17:12:06]  for the past few releases, "header review" has been both
[17:12:44]  right, so that is a problem with some teams not doing api 
review earlier then?
[17:13:16]  Yeah, it's natural that not everyone can be part of every 
code review, even if they would have something to contribute. And with a lot of 
template stuff landing in header files, the header review then also becomes an 
implementation review.
[17:14:08]  so, anyone that has something new where the discussion should 
be about API design and naming and such, please have an API review as soon as 
you can, without waiting for Jani to organize the header review, which then can 
hopefully focus on checking things for technical errors (like bc breakage)
[17:15:12] <+jaheikki3> Should we make that clearer for developers somehow?
[17:17:26] <+jaheikki3> meaning the difference between new API review and 
header review
[17:18:03]  yes, probably. We don't have great tools to let people 
outside the Qt Company invite to reviews, sadly, but as long as MS Teams is an 
acceptable tool to host the discussion, someone inside can just take care of 
the practicalities
[17:18:59]  and yes, we need to make it clearer that the header review is 
not supposed to be the first time an API should get reviewed and discussed by a 
wider audience (everything is obviously reviewed as part of code review)
[17:20:18] <+jaheikki3> vohi: would it be possible for you to send something 
about that to the development ml?
[17:20:53]  yeah, it's perhaps a conclusion to some of the respective 
email threads.
[17:21:07] <+jaheikki3> yeah
[17:21:55] <+jaheikki3> ok, I think it was all at this time. Let's end this 
meeting now and have new one tue 16th may at this same time
[17:22:05] <+jaheikki3> thanks for your participation, bye!
[17:22:44]  thanks!
[17:24:02]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS-UP: Qt 6.6 Feature Freeze is getting closer

[Jani Heikkinen via Development]

Hi,

Only less than 2 weeks to 'Platform and Module' freeze and  ~ a month to 
official feature freeze. So it is time
- to inform me about new modules coming in Qt 6.6 
   * Qt Graphs is only known one atm
- to inform me if some 'TP' module will be officially supported in Qt 6.6
- to start updating new features etc in 'What' new in Qt 6.6' wiki
   *  https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc

br,
Jani

> -----Original Message-
> From: Jani Heikkinen
> Sent: tiistai 18. huhtikuuta 2023 9.07
> To: development@qt-project.org
> Subject: HEADS-UP: Qt 6.6 Feature Freeze is getting closer
> 
> Hi all,
> 
> 
> 
> Just a kindly reminder: Qt 6.6 Feature freeze will be in effect 2nd of June
> 2023 and Qt 6.6 platform and module freeze 19th of May 2023, see
> https://wiki.qt.io/Qt_6.6_Release
> 
> 
> 
> Please inform me about all new modules planned to be released in Qt 6.6;
> we should start adding those in CI & packages asap.
> 
> Also please inform me if existing technology preview module will be officially
> supported etc.
> 
> 
> 
> br,
> 
> Jani
> 
> 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 02.05.2023

[Jani Heikkinen via Development]

Qt 6.5 status

  *   Branching from '6.5' to '6.5.1' done
  *   Qt 6.5.1 release preparations ongoing
  *   Target is to release Qt 6.5.1 Wed 10th May



Qt 6.6 status

  *   Only a month left to implement new features for Qt 6.6
 *   the whatsnew66.qdoc document here: 
https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc
*   Please add new features etc. here as soon as possible
  *   Some challenges to get dependency update done in 'dev'
 *   latest successfully submodule update was 12th April & existing 
snapshot is based on that
  *   API review process improvement started, see 
https://lists.qt-project.org/pipermail/development/2023-May/043803.html



Next meeting Tue 9th May 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:

[17:01:21] <+jaheikki3> ablasche: akseli: carewolf_home: frkleint: lars_: 
mapaaso: The-Compiler: thiago: vohi: ping

[17:01:32]  pong

[17:01:34]  pong

[17:01:39]  jaheikki3: pong

[17:01:46]  jaheikki3: pong

[17:02:14] <+jaheikki3> Time to start qt release team meeting

[17:02:19] <+jaheikki3> On agenda today:

[17:02:22]  jaheikki: pong

[17:02:24] <+jaheikki3> Qt 6.5 status

[17:02:40] <+jaheikki3> Qt 6.6 status

[17:02:47] <+jaheikki3> Any additional item to the agenda?

[17:04:05] <+jaheikki3> Ok, let's start from Qt 6.5 status

[17:04:24] <+jaheikki3> Branching from '6.5' to '6.5.1' done

[17:04:41] <+jaheikki3> Qt 6.5.1 release preparations are ongoing

[17:05:11] <+jaheikki3> All known release blockers should be already fixed

[17:06:03]  have we re-fixed the moc/qdbusxml2cpp issue?

[17:06:07] <+jaheikki3> Target is to freeze the release content at the end of 
this week &  release Qt 6.5.1 Wed 10th May

[17:06:15]  the original emergency fix was 6.5.0 only

[17:07:20] <+jaheikki3> thiago: Ahh, that one. Chatted about that with Fabina 
this morning and his plan is to cherry-pick the revert in 6.5.1 as well; the 
fix isn't ready yet

[17:07:37] <+jaheikki3> Fabian I meant to write

[17:07:55]  https://bugreports.qt.io/browse/QTBUG-110979

[17:09:16] <+jaheikki3> thiago: And this one: 
https://bugreports.qt.io/browse/QTBUG-111330

[17:10:25] <+jaheikki3> vohi: thiago: What do you think, can we live with the 
revert in Qt 6.5.1 or do we need to get the proper fix in? That will most 
likely delay the release but on the other hand we aren't that hurry with it...

[17:10:37]  the cherry-pick of the revert into 6.5.1 is 
https://codereview.qt-project.org/c/qt/qtbase/+/475342; if we have no better 
fix, then merging that revert is the right course of action

[17:12:42] <+jaheikki3> Yeah, true

[17:14:09]  we can live with the revert because it's been like that for 
a long time

[17:14:15]  it's not a regression

[17:14:57] <+jaheikki3> Ok, so let's take the revert in 6.5.1 & try to get the 
issue fixed properly in 6.5.x/6.6

[17:15:48] <+jaheikki3> It was all about Qt 6.5 at this time. Then Qt 6.6 status

[17:16:38] <+jaheikki3> Qt 6.6 feature freeze preparations ongoing

[17:16:57] <+jaheikki3> Only a month left to implement new features for Qt 6.6

[17:17:33] <+jaheikki3> So far only one new module coming in Qt 6.6

[17:17:43]  which one?

[17:17:51] <+jaheikki3> qtgraphs

[17:18:07]  Oh!!

[17:18:12]  fe

[17:18:27] <+jaheikki3> That's not yet in the snapshot but the target is to add 
it asap

[17:18:43]  aha, ok, needs PySide bindings..

[17:19:23] <+jaheikki3> We have had light challenges (once again) to get 
submodule updates done in 'dev'

[17:19:41] <+jaheikki3> latest successfully submodule update was 12th April & 
existing snapshot is based on that

[17:20:21] <+jaheikki3> But new round is ongoing & all known issues should be 
fixed so let's hope we can get full update by tomorrow morning

[17:20:55] <+jaheikki3> & so on we could get new snapshot in the installer 
tomorrow

[17:21:23] <+jaheikki3> vohi also started the discussion to improve API  review 
process, see 
https://lists.qt-project.org/pipermail/development/2023-May/043803.html

[17:21:53] <+jaheikki3> So please participate the discussion to get the process 
as smooth as possible

[17:22:18] <+jaheikki3> that's all at this time. Any more comments or questions?

[17:22:24]  Also: Seems that we had a hiccup with documentation testing 
being disabled after the last CI/Gerrit maintenance, which might need a bit of 
grinding through race conditions where new warnings block the turning-back-on 
of the documentation testing configuration.

[17:22:31]  And regular reminder to $DEAR_READER that the whatsnew66.qdoc 
document is at 
https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc :)

[17:23:20] <+jaheikki3> Yeah, thanks

[17:23:51] <+jaheikki3> Let's end this meeting now & have new one tue 9th May 
at this same time.

[17:24:02] <+jaheikki3> Thanks for your participation, bye!

[17:24:18]  thanks, bye!

[17:24:52]  bye
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] HEADS-UP: Branching from '6.5' to '6.5.1' done

[Jani Heikkinen via Development]

Hi!

We have branched '6.5.1' from '6.5'. So from now on all changes targeted to Qt 
6.5.1 release must have 'Pick-to: 6.5.1' and '6.5' is for Qt 6.5.2 release. As 
usual staging in '6.5.1' is restricted to release team only and we will monitor 
incoming changes and stage the clear ones in automatically. Please do not add 
any nice-to-haves in '6.5.1' anymore; those can wait Qt 6.5.2. The target is to 
release Qt 6.5.1 10th May 2023

br,
Jani Heikkinen
Release Manager
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Meeting minutes from Qt Release Team meeting 18.04.2023

[Jani Heikkinen via Development]

Qt 6.5 status

  *   Qt 6.5.0 released
  *   Qt 6.5.1 preparations started
 *   First internal snapshot created & testing ongoing
  *   Target is to branch '6.5.1' from '6.5' at the beginning of May
  *   Target is to release Qt 6.5.1 10th of May 2023



Qt 6.6 status

  *   Platform and module freeze will be in effect Fri 19th May
  *   Qt 6.6 feature freeze will be in effect 2nd June
 *   Please add new issues to  
https://codereview.qt-project.org/gitweb?p=qt/qtdoc.git;a=blob;f=doc/src/whatsnew/whatsnew66.qdoc
 when new stuff merges
  *   Qt 6.6 snapshot available in the installer & updated regularly



Next meeting Tue 2nd May 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:

[17:00:25]  ablasche: akseli: carewolf_home: frkleint: lars_: 
mapaaso: The-Compiler: thiago: vohi: ping

[17:00:29]  pong

[17:00:38]  jaheikki3: pong

[17:00:49]  jaheikki3: pong

[17:01:13]  Time to start qt release team meeting

[17:01:17]  pong

[17:01:19]  On agenda today:

[17:01:23]  Qt 6.5 status

[17:01:26]  Qt 6.6 status

[17:01:34]  Any additional item to the agenda?

[17:02:53]  Let's start from Qt 6.5 status

[17:03:24]  Qt 6.5.0 released 3.4.2023

[17:03:54]  jaheikki3: pong

[17:04:08]  Seems to be quite solid release; at least I haven't get 
reports from anything that critical

[17:04:40]  Qt 6.5.1 preparations started and first snapshot created

[17:04:53]  RTA for that ongoing

[17:05:05]  a few regressions in 6.5.0 that we are working on, but 
nothing world-breaking as far as I have seen

[17:05:08]  I haven't seen any major reports on 6.5,9 either

[17:05:11]  6.5.0

[17:05:17]  there were reports, but nothing major

[17:05:50]  sounds good

[17:06:23]  the plan is to start branching from '6.5' to '6.5.1' at 
the beginning of May and release Qt 6.5.1 10th May

[17:07:03]  that's all about Qt 6.5 status at this time. Any 
comments or questions?

[17:08:25]  Ok, then Qt 6.6 status

[17:09:23]  Qt 6.6 platform and module freeze milestone will be 19th 
may so only a month left to get all new modules in

[17:10:22]  And Qt 6.6 feature freeze will be in effect 2nd June

[17:11:13]  Qt 6.6 snapshot available in online installer. It is 
updated pretty reqularly, last time 15th April

[17:11:59]  That's pretty much all at this time. Any comments or 
questions?

[17:12:25]  there's a whatsnew66.qdoc file already in the qtdoc repo, 
good to keep that up-to-date as new stuff merges

[17:12:56]  yep

[17:13:31]  and the 6.5 header review has been an unusually painful 
process. Shout-out to Marc for doing a heroic effort reviewing and fixing 
things and chasing after folks, but perhaps there are things we can improve. 
Will send a mail to the mailing list in a bit to ask for "retrospective" input

[17:13:52]  I need to finish the IPC stuff that was merged

[17:14:55]  vohi: totally agree and it would be good to get that 
improved somehow

[17:16:19]  Ok, it was all at this time so let's end this meeting 
now and have new one Tue 2nd May; I can't join next week

[17:16:34]  Thanks for your participation, bye!

[17:16:46]  ok, thanks!
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development