[Development] Meeting minutes from Qt Release Team meeting 09.04.2024
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] Trouble getting reviews in months and years
On Tuesday 9 April 2024 10:12:48 PDT Ilya Fedin wrote: > Oh, sorry, I was answering in quite a sleepy state but now I checked the > change you quoted and it seems I did almost everything as you said? The > change is supplied at Nov 23, 2022 which is long before Christmas, with > only a rebase and a minor commit message change during Christmas, > then I pinged at Jan 14 which is exactly a day before the second week of > January? The only thing I haven't done is adding Volker as I didn't > know (is this written anywhere?) that's something should be done... I missed that the initial upload was in November.. In any case, that was only one of many changes and the others don't fall on holidays. So that portion of the message wouldn't apply to them. Just take the procedure as I outlined, to send ping and re-pings, then adding maintainers and then asking this list. Don't wait months and years: you're entitled to getting a review within one month. The worst that can happen are that someone decides to make a permanent rejection because they can't justify accepting. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Trouble getting reviews in months and years
On Mon, 08 Apr 2024 22:36:56 -0500 Thiago Macieira wrote: > On Monday 8 April 2024 17:17:04 CDT Ilya Fedin wrote: > > 2. https://codereview.qt-project.org/c/qt/qtbase/+/444859 which is > > 1.5 years old and no review > > Submitted during Christmas break and no changes since New Years. No > wonder it was missed. You should have sent a "ping" during the second > week of January. > > That's the rule of thumb: after a week with no reviews, send "ping> . > One week later, "re-ping". If you reach the third week, explicitly > add the maintainer of the module in question and say, "maintainer, do > your duty and review". And if that maintainer is unavailable for some > reason, add Volker. > > If all else fails, there's this mailing list. You can send an email > with your pending reviews and request that they be reviewed. But > advice: include the topic of the review, not just the link and how > long it's been. I have absolutely no clue on reviewing XCB stuff, but > I had to click every link to make sure none of them was a QtCore > issue I might have missed. > Oh, sorry, I was answering in quite a sleepy state but now I checked the change you quoted and it seems I did almost everything as you said? The change is supplied at Nov 23, 2022 which is long before Christmas, with only a rebase and a minor commit message change during Christmas, then I pinged at Jan 14 which is exactly a day before the second week of January? The only thing I haven't done is adding Volker as I didn't know (is this written anywhere?) that's something should be done... -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Cherry-pick bot outage 08/09 April
Hi all, Yesterday and today, 08/09 April, there were a few brief cherry-pick bot outages which caused the bot to not receive events about merging changes. Root cause for this issue is was introduction of nonstandard branch naming in a repo, causing a crash in pickbot's pick-order logic. At this time, I believe pickbot's recovery scripts have identified all missed work and regenerated change-merged events for changes which merged during the outage periods. This will have the bot to perform the cherry-picks as usual, but please keep an eye out in your changes to make sure that merged changes over the last day have been cherry-picked as intended. If not, you can either cherry-pick to the target branch manually, or send me an email with the change that needs to be fed through the bot again. Best regards, -Daniel -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
