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

Tuukka Turunen tuukka.turunen at qt.io
Tue Apr 11 10:47:52 CEST 2017

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? 



On 11/04/2017, 11.34, "Development on behalf of Ville Voutilainen" <development-bounces+tuukka.turunen=qt.io at qt-project.org on behalf of ville.voutilainen at gmail.com> wrote:

    On 11 April 2017 at 11:22, Ville Voutilainen
    <ville.voutilainen at gmail.com> wrote:
    > On 11 April 2017 at 10:30, Marc Mutz <marc.mutz at kdab.com> wrote:
    >> On Tuesday 11 April 2017 07:49:28 Tuukka Turunen wrote:
    >>> There has been a lot of discussion about this in the mailing lists, I think
    >>> the two ones below sum it up quite well.
    >> They sum up *your* POV well. But up to a few weeks ago, more fixes went into
    >> 5.8 QtBase than changes into 5.9, even though TQC personell was asked to
    >> ignore 5.8.
    >> You can close 5.8 on all other modules, if you wish, but I'd ask to keep it
    >> open on QtBase, which has a lively development going on in 5.8 to this day.
    > Here's an anecdote: this https://codereview.qt-project.org/#/c/189229/
    > hasn't been merged
    > to 5.9, as far as I can see. I find it curious that bugfixes from two
    > weeks ago haven't trickled
    > into 5.9 from 5.8 yet. Such matters may well raise the bar for users
    > for working with 5.9 rather than
    > with 5.8.
    To elaborate: I run a bleeding-edge compiler. It feels odd to me that
    the best branch to run it on
    is a non-bleeding-edge branch, it's quite the opposite.
    Development mailing list
    Development at qt-project.org

More information about the Development mailing list