[Development] Changes to Qt offering

[Dmitriy Purgin]

Hi Cristián,

surely, everyone is technically able to cherry-pick and backport bug fixes
into their local Qt versions but not everybody has resources and/or
knowledge to do so.

I personally think this could be an inflection point into forking the Qt 5
"Community Edition", with all binary builds supported and maintained by the
community not affiliated with The Qt Company. There could be a Non-TQC Qt
5.15 Community LTS with backported bug fixes and maybe even new features.
As already mentioned in this thread, the free-to-download binary releases
would be the first thing to appear as soon as the Qt account will be
required.

Of course, there is always Qt Commercial offering but there could be
smaller 3rd party companies offering the same but for less money. It's a
free market but it would a split in the community, and  I personally see
this as a bad thing that can happen to the Qt Framework.

Cheers
Dmitriy

On Mon, Jan 27, 2020 at 11:16 PM Cristián Maureira-Fredes <
Cristian.Maureira-Fredes at qt.io> wrote:

> Hello David,
>
> On 1/27/20 11:00 PM, David Edmundson wrote:
> >> All security fixes are made available to everyone, for all Qt versions
> that
> >> they affect, provided it's still a supported Qt version (or it was easy
> to
> >> make the fix).
> >>
> > If we could have that explicitly in writing from TQC, that would mean a
> lot.
>
> The blog post states:
>
> "We are changing our process in R&D to push all bug fixes to the main
> development branch first, and then backport selected bug fixes back into
> stable release branches. This process ensures that the latest version of
> Qt will always contain all bug fixes. This process change was discussed
> during the last Qt Contributor Summit – we communicate the exact process
> details when Qt 5.15 will be released. Otherwise, development processes
> and the governance model will not change."
>
> This means that you still have access to all the fixes for 5.15
> that happen after 5.15.2-3, since they will be on the dev branch.
>
>
> > I can easily envision a situation that affects only Qt5.15, but not
> > Qt6.0 at which point it's not covered by what has been suggested
> > officially so far as there would be nothing to cherry-pick.
> >
> > David
>
> If there is a bug on 5.15 and not on 6.0,
> a fix will be pushed to the dev branch, then cherry pick to the
> commercial LTS version, but the patch will still be there, so you
> can just added to your local Qt version.
>
> The Qt Contributors Summit discussion can be found here too:
> https://wiki.qt.io/Qt_Contributors_Summit_2019_-_Branch_Policy
>
>
> Cheers
>
> --
> Dr. Cristián Maureira-Fredes
> R&D Manager
>
> The Qt Company GmbH
> Erich-Thilo-Straße 10
> D-12489 Berlin
> https://qt.io
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200127/a70e5ed9/attachment.html>