[Development] Changes to Qt offering

NIkolai Marchenko enmarantispam at gmail.com
Mon Jan 27 17:44:26 CET 2020

>  A: We have had the Qt Account as an option for over 4 years, and during
that time there has been already nearly a million people who have
registered and verified their Qt Account.
And how many of them use these accounts to download qt, eh? I bet you they
only use the acc to login to bugtracker and develop qt.
No one wants to enter credentials to reinstal qt. Period.

On Mon, Jan 27, 2020 at 7:39 PM NIkolai Marchenko <enmarantispam at gmail.com>

>  > and the offline installer will become available to commercial
> licensees only
> Not to mention "free qt binaries installer" will become a third party
> thing like, immediately.
> On Mon, Jan 27, 2020 at 7:37 PM Benjamin TERRIER <b.terrier at gmail.com>
> wrote:
>> My understanding of the agreement between The Qt Company and the KDE Free
>> Qt Foundation is that if the Qt Company
>> releases a commercial Qt version without releasing the corresponding
>> open-source version within 12 months, the ownership of Qt will be
>> transferred
>> to the KDE Free Qt Foundation under a BSD license. (section 3.(ii)).
>> I am pretty sure a source only release would be enough. So I bet that the
>> LTS branches will be public, but we will not have a binary release through
>> the installer.
>> Le lun. 27 janv. 2020 à 17:17, Bogdan Vatra via Development <
>> development at qt-project.org> a écrit :
>>> Hi Lars,
>>> În ziua de luni, 27 ianuarie 2020, la 16:34:44 EET, Lars Knoll a scris:
>>> > Hi all,
>>> [...]
>>> >
>>> > One is a change in policy regarding the LTS releases, where the LTS
>>> part of
>>> > a release is in the future going to be restricted to commercial
>>> customers.
>>> > All bug fixes will (as agreed on the Qt Contributor Summit) go into dev
>>> > first.
>>>   I was at the Qt Contributor Summit, and I can swear that I not heard
>>> anything about LTS being restricted to commercial customers...
>>> Just to be crystal clear, will you close also the branches?
>>> What will happen if I want to fix something in one of these LTS branches?
>>> > Backporting bug fixes is something that the Qt Company will take
>>> > care of for these LTS branches. We’ve seen over the past that LTS
>>> support
>>> > is something mainly required by large companies, and should hopefully
>>> help
>>> > us get some more commercial support for developing Qt further.
>>> I bet you the following scenario will happen soon:
>>> - someone will fork Qt LTS (most probably immediately after you closed
>>> these
>>> branches, if not even sooner)
>>> - the community will continue to support that fork as it's open, with
>>> improvements, bug fixes, security patches, etc.
>>> - you'll not get these patches as they are not contributed via your
>>> gerrit...
>>> > None of these changes should affect how Qt is being developed. There
>>> won’t
>>> > be any changes to Open Governance or the open development model.
>>>  If the qt5 branches will NOT be closed, then yes, you are right, if
>>> they will
>>> be closed then, I'm afraid, your statement can't stand...
>>> Cheers,
>>> BogDan.
>>> _______________________________________________
>>> Development mailing list
>>> Development at qt-project.org
>>> https://lists.qt-project.org/listinfo/development
>> _______________________________________________
>> 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/a884303c/attachment-0001.html>

More information about the Development mailing list