[Development] Staging in '5.6'

[Tuukka Turunen]

+1

From: Development <development-bounces+tuukka.turunen=qt.io at qt-project.org> on behalf of Jani Heikkinen <jani.heikkinen at qt.io>
Date: Thursday, 12 October 2017 at 11.14
To: "development at qt-project.org" <development at qt-project.org>
Subject: [Development] Staging in '5.6'


Hi all,



After Qt 5.6.3 release, staging has been restricted in ‘5.6’ and I have monitored some of the changes trying to come in. I have noticed people sometimes trying to put some really minor P3 etc fixes in ‘5.6’ even those really shouldn’t be put in there. With ‘5.6’ we are already in ‘strict’ mode so there shouldn’t be that much changes taken in ( see http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.txt )



Ossi opened staging for everyone but I propose we should restrict staging for release team only. That way we could better monitor changes coming into ‘5.6’ and owners must explain really well why every change is really needed in ‘5.6’ series. That will decrease changes in ‘5.6’ and so on decrease the risk of new regression. And this all would be good preparations for moving to very strict mode which should happen March 2018.



br,

Jani
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20171012/fbf0868e/attachment.html>