On 2/3/21 5:36 PM, Volker Hilsheimer wrote:
Milk, Joerg.
Blame my handwriting!
But why not get rid of the gap in the first place, ie instead of having a gap
between
- final dependency update sha1s are fixed, full update round started
- 6.1 branch is created
What stops us from simply cre
> On 3 Feb 2021, at 16:01, Joerg Bornemann wrote:
>
> On 2/3/21 11:42 AM, Edward Welbourne wrote:
>
The change in question cannot have the Pick-to: 6.1 footer, because
the branch does not exist. How can I avoid to forget cherry-picking
that change, once 6.1 is in place?
>
>>> Yes
On 2/3/21 11:42 AM, Edward Welbourne wrote:
The change in question cannot have the Pick-to: 6.1 footer, because
the branch does not exist. How can I avoid to forget cherry-picking
that change, once 6.1 is in place?
Yes, that’s a risk with cherry-pick mode.
That's the confirmation I was look
Hi all,
We have released Qt 6.0.1 today, see https://www.qt.io/blog/qt-6.0.1-released
Big thanks to everyone involved!
Br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/deve
Hi,
Branching from 'dev' to '6.1' is now done. So all changes targeted to Qt 6.1
release must be done in '6.1' and 'dev' is for Qt 6.2
br,
Jani Heikkinen
Release Manager
From: Development on behalf of Jani
Heikkinen
Sent: Monday, February 1, 2021 2:34
On 3 Feb 2021, at 09:31, Joerg Bornemann wrote:
>> Let's say I have a change for qtbase's dev branch that is supposed to
>> be cherry-picked to 6.1. What happens if this change hits qtbase
>> between those two points in time:
>>
>> - final dependency update sha1s are fixed, full update round start
> On 3 Feb 2021, at 09:31, Joerg Bornemann wrote:
>
> On 2/1/21 1:34 PM, Jani Heikkinen wrote:
>
>> Qt 6.1 Feature Freeze is in effect now. So please do not add any new
>> features, API changes ect in 'dev' anymore until we have done branching from
>> 'dev' to '6.1'. We are trying to do branch
On 2/1/21 1:34 PM, Jani Heikkinen wrote:
Qt 6.1 Feature Freeze is in effect now. So please do not add any new features,
API changes ect in 'dev' anymore until we have done branching from 'dev' to
'6.1'. We are trying to do branching from 'dev' to '6.1' as soon as possible
but at first we need
