‘5.6.0’ branch is now available, please start using it for the changes targeted
to Qt5.6.0 release.
We will merge ‘5.6’ branch to ‘5.6.0’ Monday 1st February so there should be
enough time to finalize ongoing changes in ‘5.6’ and start using '5.6.0'. All
new changes for Qt5.6.0 should be done
Jani:
I see the 5.6.0 RC blocker list.
But what about bugs like?
Using 5.6.0 Beta: https://bugreports.qt.io/browse/QTBUG-50374
What is the criterion for entry into the blocker list?
Only core code, not tools?
Thank you,
md
On Mon, Jan 25, 2016 at 5:39 AM, Heikkinen Jani
wrote:
> ‘5.6.0’ b
Hi,
Final downmerge is now done and branching is complete. From now on '5.6' is for
Qt 5.6.1 and '5.6.0' for Qt 5.6.0. Staging in '5.6.0' is restricted and we in
the release team will stage needed changes in '5.6.0' from now on. We will
check approved changes automatically so no need for any sp
Jani:
I submitted a message a week ago about the blocker list criterion and
could not find a QT FAQ on what are the critierion.
For example: https://bugreports.qt.io/browse/QTBUG-50374 is NOT a
blocker for 5.6.0 RC.
It is P2: Important.
Likely I am missing something about how the blocker list i
m: mark diener [mailto:rpzrpz...@gmail.com]
>>Sent: 2. helmikuuta 2016 16:37
>>To: Heikkinen Jani
>>Cc: development@qt-project.org
>>Subject: Re: [Development] HEADS UP: Qt 5.6.0 branching ongoing
>>
>>Jani:
>>
>>I submitted a message a week ago about the
ruary 2, 2016 3:37 PM
To: Heikkinen Jani
Cc: development@qt-project.org
Subject: Re: [Development] HEADS UP: Qt 5.6.0 branching ongoing
Jani:
I submitted a message a week ago about the blocker list criterion and
could not find a QT FAQ on what are the critierion.
For example: https://bugreport
