Re: Qt goes "commercial only! - what now?
El jue, 7 de ene. de 2021 a la(s) 08:52, Mathias Homann (mathias.hom...@opensuse.org) escribió: > > Am Donnerstag, 7. Januar 2021, 11:01:23 CET schrieb David Edmundson: > > > From a user point of view, there will be no impact. > > are you sure? To me it sounds as if only commercial "licensees" will have > access to the latest sources and/or security fixes, which also won't get > backported anymore... Only commercial licensees will have access to backported fixes for Qt 5.15. There are no changes regarding access to Qt6. Qt 5.12 is LTS and will keep getting public fixes until Dec 2021 too. -- Nicolás
Re: Qt goes "commercial only! - what now?
On Thursday, 7 January 2021 08:52:12 -03 Mathias Homann wrote: > Am Donnerstag, 7. Januar 2021, 11:01:23 CET schrieb David Edmundson: > > From a user point of view, there will be no impact. > > are you sure? To me it sounds as if only commercial "licensees" will have > access to the latest sources and/or security fixes, which also won't get > backported anymore... Let me be very clear so there's no mistake: all security issues will be dealt with in all branches, to the extent that we are able to reproduce them and confirm them. We usually identify down to the point release where security issues apply and will continue to do so. All non-security fixes will be available in later branches, per Qt Project policy. Non-commercial users will simply not see them backported (and thus adjusted, if necessary) to the older versions. That unfortunately also means we won't know which commits will be selected for backporting. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Re: Qt goes "commercial only! - what now?
Am Donnerstag, 7. Januar 2021, 11:01:23 CET schrieb David Edmundson: > From a user point of view, there will be no impact. are you sure? To me it sounds as if only commercial "licensees" will have access to the latest sources and/or security fixes, which also won't get backported anymore... Cheers MH -- Mathias Homann mathias.hom...@opensuse.org OBS: lemmy04 Jabber (XMPP): le...@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 signature.asc Description: This is a digitally signed message part.
Re: Qt goes "commercial only! - what now?
Really this is just eol for qt5. On Thu, Jan 7, 2021, 4:55 AM Mathias Homann wrote: > Hi, > > https://www.theregister.com/2021/01/05/qt_lts_goes_commercial_only/ > https://bugreports.qt.io/browse/QTQAINFRA-4121 > https://lists.qt-project.org/pipermail/development/2021-January/040799.html > > ...what is that going to mean for KDE/Plasma? > > Cheers > MH > -- > Mathias Homann > mathias.hom...@opensuse.org > OBS: lemmy04 > Jabber (XMPP): le...@tuxonline.tech > IRC: [Lemmy] on freenode and ircnet (bouncer active) > telegram: https://telegram.me/lemmy98 > keybase: https://keybase.io/lemmy > gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Re: Qt goes "commercial only! - what now?
That subject title is misleading. >From a user point of view, there will be no impact. David
Qt goes "commercial only! - what now?
Hi, https://www.theregister.com/2021/01/05/qt_lts_goes_commercial_only/ https://bugreports.qt.io/browse/QTQAINFRA-4121 https://lists.qt-project.org/pipermail/development/2021-January/040799.html ...what is that going to mean for KDE/Plasma? Cheers MH -- Mathias Homann mathias.hom...@opensuse.org OBS: lemmy04 Jabber (XMPP): le...@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 signature.asc Description: This is a digitally signed message part.