[Development] HEADS UP: Qt 5.6.0 branching ongoing

Wed Feb 3 10:49:47 CET 2016

Hi,

As Jani explained in another mail, the fact that something does not block a release does not mean it's considered unimportant. We want to be as close as possible to a time-based release schedule, which means that if a new release does not regress and is an improvement to most users, it's better to get it out than to delay for everyone in order to get a bug fix in. 

As for priorities: P0 is for bugs that prevent further development of Qt and that need to be fixed right away. P1 is for crashes, regressions, security issues, memory corruption, bad drawing bugs, some build issues, etc. 

The highest priority we have for issues that do not fall into these categories is P2, so I think that's the appropriate priority for the bug in question since it's an inconvenience that you cannot debug on the simulator using Qt Creator. If you disagree with the priority set, you can discuss it with the assignee in the comment field of the bug report and explain why you believe the bug is more critical. It happens that the bug triaging team or assignee has underestimated a bug, so it's important to get input from the people affected by it. 

It's also possible to vote for bugs. That will usually be taken into account when people prioritize what they work on, since it's an indication of the number of users affected by the bug.

-- Eskil

________________________________________
From: Development <development-bounces at qt-project.org> on behalf of mark diener <rpzrpzrpz at gmail.com>
Sent: Tuesday, February 2, 2016 3:37 PM
To: Heikkinen Jani
Cc: development at 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://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 is
constructed and interpreted.

But should 5.6.0 release with QTBUG-50374 still present, Qt is
effectively saying, we have cut back support for IOS.

And that would be big news.

Please educate me.

md

On Tue, Feb 2, 2016 at 6:51 AM, Heikkinen Jani
<jani.heikkinen at theqtcompany.com> wrote:
> 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 special actions from you; just take care that your changes will be approved.
>
> And please remember: We will take in only really important changes so please don't add any nice-to-haves in '5.6.0' anymore! If we can live with issue in Qt 5.6.0 then please use '5.6' instead.
>
> And as usual please send re-targeting request to Ossi if there is some change open in '5.6' and which must be in Qt 5.6.0
>
> br,
> Jani
>
> ________________________________________
> Lähettäjä: Heikkinen Jani
> Lähetetty: 25. tammikuuta 2016 13:39
> Vastaanottaja: development at qt-project.org
> Kopio: releasing at qt-project.org
> Aihe: HEADS UP: Qt 5.6.0 branching ongoing
>
> ‘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 in ‘5.6.0’ branch from now on.
>
> Target is to release Qt5.6.0 RC quite soon so please make sure all blockers will be fixed as soon as possible. Blocker list here: https://bugreports.qt.io/issues/?filter=17225
> Please make sure all Qt 5.6.0 blockers are found from blocker list (== set 5.6.0 RC as fix version(s)): We should fix all blockers before RC & minimize changes between RC and final.
>
> And please remember: Do not add any 'nice to have' -changes in anymore (P0 & P1 bug fixes mostly, in some special cases p2 fixes might be ok as well).
>
> Best regards,
> Jani Heikkinen
> Release Manager | The Qt Company
>
> The Qt Company / Digia Finland Ltd, Elektroniikkatie 13, 90590 Oulu, Finland
> Email: jani.heikkinen at theqtcompany.com | Mobile: + 358 50 48 73 735
> www.qt.io |Qt Blog: http://blog.qt.digia.com/ | Twitter: @QtbyDigia, @Qtproject Facebook: www.facebook.com/qt
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development