[Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

Simon Hausmann Simon.Hausmann at qt.io
Tue Apr 11 11:00:22 CEST 2017


When closing a branch we'll always do the merge. So closing 5.8 will be followed by a last 5.8 -> 5.9 merge for sure. For qt5.git Liang has already done that, for


From: Development <development-bounces+simon.hausmann=qt.io at qt-project.org> on behalf of Ville Voutilainen <ville.voutilainen at gmail.com>
Sent: Tuesday, April 11, 2017 10:55:55 AM
To: Tuukka Turunen
Cc: Qt development mailing list
Subject: Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

On 11 April 2017 at 11:47, Tuukka Turunen <tuukka.turunen at qt.io> wrote:
> Hi Marc,
> I can understand your viewpoint, but unfortunately keeping 5.8 open does cause additional load to the systems as well as people. It would be great if you would rather focus into improving Qt 5.9 and making it good for our users than pushing stuff into a branch that has no further releases planned from it.
> Can you explain why you can not push your Qt Base changes to 5.9 like ~everyone else?

I still hear suggestions along the lines of pushing stuff into 5.8,
from which they "eventually get merged into 5.9 and dev". That
merging seems to be an occasional manual process, though, so the
overall situation is confusing indeed.  At any rate, I think
it would be wise to do a 5.8->5.9 merge before even considering
closing 5.8, lest we lose bugfixes.
Development mailing list
Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170411/f5a32ca3/attachment.html>

More information about the Development mailing list