 https://www.qt.io/blog/qt-5.14.1-released
 \o/
 As said earlier, I don't have time to look at it, but that may change in a few days.
 Yeah, just put that there for info. Especially (as pointed out) no release email yet
 As I say that, the email arrived!
 https://www.qt.io/blog/qt-offering-changes-2020
 Oh! But there is one thing I don't understand:
 > This means open-source users will receive patch-level releases of 5.15 until the next minor release will become available. … But there will be no minor release after 5.15. The next series will be 6.0.
 If they drop support for 5.15 immediately after 6.0 is released, that will be sad. Maybe the new policy will apply only for later 6.x LTS releases?
 I guess they want to kill off 5 ASAP for people who are not prepared to pay.
 So the announcement needs removal of ‘minor’ word. … There is a related discussion on the ML, which I will follow.
 I can see the logic. It is just a bit cynical
 Yeah, I see that logic too. Nothing critical for us — we can always cherry-pick important fixes manually. And I guess someone will create a fork of 5.15 branch on GitHub when it gets closed.
 Urgh. mailing list archives are so hard to follow!
 @mitya57 [Yeah, I see that logic too. Nothing critical for us — we can always cherry-pick …], It will also make our current stays with LTS or go with newer, a less big choice
 Right
[17:54] <fvogt> Yeah, the commericial-only LTS change needs some clarification. If it happens for 5.15 already, I'd propose that KDE forks it once Qt 6 is out
 KDE has already set up mirrors, I don't know whether they will be kept as mirrors or repositories with commit access after Qt 6 is released though.
[22:09] <valorie> There is ongoing discussion between the Qt Company and the KDE Free Qt Foundation about this ^^^
[22:10] <valorie> and that's all I can say
[22:10] <valorie> discussion/negotiation