[Development] HEADS-UP: Branching from 'dev' to '6.10' is done & Qt 6.10 Feature Freeze is in effect
Volker Hilsheimer
volker.hilsheimer at qt.io
Mon Jun 2 09:41:00 CEST 2025
Hi Sami,
Keep staging it so that we know that it works in dev; as mentioned just now in reply to Hamed, we’ll review and decide on exception requests in the release team meeting.
If you get an exception, you’ll have to manually cherry-pick the change:
https://wiki.qt.io/Branch_Guidelines#How_to_cherry-pick
Volker
> On 2 Jun 2025, at 09:32, Sami Shalayel via Development <development at qt-project.org> wrote:
>
> Hi,
> I would like to ask for a FF exception for qmlls. The feature (643577: cmake: map module to import paths in build folder for qmlls | https://codereview.qt-project.org/c/qt/qtdeclarative/+/643577) is already ready but failed to merge into 6.10 due to unrelated test failures.
> Best Regards,
> Sami Shalayel
>
> On 02.06.25 06:52, Jani Heikkinen via Development wrote:
>> Hi!
>> Branching from ‘dev’ to ‘6.10’ is now done and the Qt 6.10 Feature Freeze is in effect! So from now on all changes targeted to the Qt 6.10 must have 'Pick-to: 6.10' and 'dev' is for Qt 6.11. If your new feature skipped the branching, you need either request an exception or wait Qt 6.11.
>> Staging qt5.git#6.10 will be restricted until Qt 6.10 beta1 is out, but restrictions in ‘dev’ are removed & you can start staging changes in qt5.git#dev
>> br,
>> Jani Heikkinen
>> Release Manager
>> From: Development <development-bounces at qt-project.org> On Behalf Of Jani Heikkinen via Development
>> Sent: perjantai 30. toukokuuta 2025 12.59
>> To: Qt development mailing list <development at qt-project.org>
>> Subject: [Development] HEADS-UP: Qt 6.10 Feature Freeze
>> Hi!
>> Qt 6.10 Feature Freeze will be in effect today. As earlier: 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 ‘dev’ to ‘6.10’ 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.11 or request an exception.
>> br,
>> Jani Heikkinen
>> Release Manager
>>
> --
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
More information about the Development
mailing list