Hi,

I've now run a post-branching script that will have cherry-pick bot warn you if 
you were targeting 6.6 for a Pick-to target from dev, but have not updated it 
to target 6.7 as well.

Similarly, the bot has also removed +2 approvals from any dev change that does 
not already target 6.7. This is a new behavior for this branching event but 
will be the standard moving forward. This is to force re-evaluation if a change 
really must get into the 6.7 FF, or if it can simply merge normally on dev with 
6.8 as the future target. Reviewers which gave a +2 on a given change have been 
added to the attention set, so please take a look at the Your Turn dashboard 
and give a new +2 and edit the commit message to target 6.7 as a pick target if 
necessary.

Best regards,
-Daniel
________________________________
From: Development <development-boun...@qt-project.org> on behalf of Jani 
Heikkinen via Development <development@qt-project.org>
Sent: Monday, December 11, 2023 7:15 AM
To: development@qt-project.org <development@qt-project.org>
Subject: [Development] HEADS-UP: Branching from 'dev' to '6.7' done


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 <development-boun...@qt-project.org> 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

Reply via email to