Hi Tuuka, By that link I didn't mean QTBUG-102962 exactly, but 23 matching bugs for a single component (which is not even one of the top-wanted components). On vanilla 6.2.4, QCamera simply doesn't work on many Android devices. All these issues were resolved for 6.2.5. Coincident?
> We are no holding back on bug fixes, though. > so the fix is in Qt 6.3.1 Technically you aren't. But in fact you are! That is what I called "please stick to unstable, semi-functional versions of Qt, test them and report bugs". 6.3 brought a bunch of new bugs and regressions, and some of them still aren't fixed. As for example, look at -- https://bugreports.qt.io/browse/QTBUG-98964?jql=text%20~%20%22Binding%20on%20contentItem%20is%20not%20deferred%20as%20requested%20by%20the%20DeferredPropertyNames%20class%20info%20because%20one%20or%20more%20of%20its%20sub-objects%20contain%20an%20id%22 -- (and not only at QTBUG-98964). Fixed in 6.3.0? Sure it is. But it is still reproducible in dev... Maybe it is not really important? Well, I personally can live with it. Until I get a hang/crash report in release due to this issue... And that's just a single example of many. Okay, perhaps I should stick back to 6.2.4, keep my eye on commits picked-up to mysterious 6.2.5 and apply them manually. Thanks, cherry-picking monkey is a job I was dreaming of! When I chose Qt for developing my apps, it was "Code less, create more[, deploy everywhere]". I was ok with building Qt from sources when you started selling binaries to your commercial folks. Waste of an hour of my machine power per several months was not a big price for stability update. But we definitely didn't choose to be your free testing crowd! Regards, Unhappy monkey пн, 19 сент. 2022 г. в 20:15, Tuukka Turunen <tuukka.turu...@qt.io>: > Hi Konstantin, > > > > I am sorry to hear that you are unhappy with Qt 6.2 moving to the > commercial-only long-term-support phase with release of Qt 6.2.5. > > > > We are no holding back on bug fixes, though. > > > > All applicable bug fixes go to dev and are picked to all active branches. > The fix to QTBUG-102962 was merged to 6.3 branch at the end of April, so > the fix is in Qt 6.3.1 released in June, as well as in the latest Qt 6.3.2 > release as well as the soon-to-be released Qt 6.4.0 release. > > > > Yours, > > > > Tuukka > > > > > > *From: *Development <development-boun...@qt-project.org> on behalf of > Konstantin Ritt <ritt...@gmail.com> > *Date: *Monday, 19. September 2022 at 15.46 > *To: *development@qt-project.org <development@qt-project.org> > *Subject: *Re: [Development] Commercial-only 6.2 LTS phase starts: > Closing the 6.2 branch(es) on 20th April > > It is probably the most destructive and annoying thing you did! > > > > I'll try to rephrase what you said in that announcement: "Dear community, > please stick to unstable, semi-functional versions of Qt, test them and > report bugs you've found (for free), so we could better support our > valuable customers (not you). Your contributions are welcomed (but you have > to pay some money to us to get any gain from your fixes, unless you're ok > with sticking to some newer semi-functional version of Qt). Thanks for > everything you did for Qt project (we don't appreciate that). That's how > Open Governance works, b???h!" > > > > Am I exaggerating? Let's briefly look at > https://bugreports.qt.io/browse/QTBUG-102962?jql=project%20%3D%20QTBUG%20AND%20component%20%3D%20Multimedia%20and%20fixVersion%20%3D%206.2.5 > > > > Okay, you won: I'll buy your commercial license, just to share your > commercial-only repositories to everyone! > > > Regards, > Konstantin > > > > > > ср, 20 апр. 2022 г. в 10:01, Tarja Sundqvist <tarja.sundqv...@qt.io>: > > Hi, > > > > With Qt 6.3.0 released and the first patch release (Qt 6.3.1) coming soon, > it is time to enter the commercial-only LTS phase for Qt 6.2 LTS. All the > existing 6.2 branches remain publicly visible, but they are closed for new > commits and cherry-picks. The exception is the Qt WebEngine, which has a > 3rd party LGPL dependency. > > > > Closing happens today, 20th April 2022. After this, the cherry-picks go to > another repository that will be available only for the commercial license > holders. We will arrange repository access to the commercial license > holders, so in addition to the official releases, it is possible to use the > repositories. > > > > The first commercial-only Qt 6.2.5 LTS patch release is planned to be > released in May. > > > > The external module maintainers that have access to the Qt 5.15 > commercial-only repositories, will also have access to the Qt 6.2 > commercial-only repositories. If you notice that you don’t have access even > if you should have, please contact me (tarja.sundqv...@qt.io) as I am the > release manager for the commercial-only LTS releases. > > > > Best regards, > > Tarja Sundqvist > > Release manager > > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > >
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
