Qt 5.7 Release Candidate Surfaces

[phoronix]

Phoronix: Qt 5.7 Release Candidate Surfaces

Similar to past Qt5 tool-kit releases, Qt 5.7 has been running behind schedule but they are now out with a release candidate and hope to officially ship this update later in June...

http://www.phoronix.com/scan.php?page=news_item&px=Qt-5.7-Release-Candidate

[bug77]

Are these guys insane? Everybody's waiting for 5.6.1 to close some glaring bugs in what's supposed to be a LTS release and they announce 5.7 instead?

[Steffo]

Are these guys insane? Everybody's waiting for 5.6.1 to close some glaring bugs in what's supposed to be a LTS release and they announce 5.7 instead?

If I am the network module maintainer and there is a bug in my network module, why should every developer freeze, because I have a network bug?

[bug77]

If I am the network module maintainer and there is a bug in my network module, why should every developer freeze, because I have a network bug?

This isn't about an isolated bug fix. It's about not fixing a few critical bugs (there's like 3-4 left right now) and instead spending the available resources on a whole new friggin' release.

[Emdek]

Qt WebEngine is updated against Chromium and supports features like drag-n-drop / spellchecking / print to PDF / HTML5 DRM protected video

There is no spell checking support in QtWebEngine for 5.7, it was postponed.
Perhaps we would get it now if Chromium would use standard formats for dictionaries...

[Awesomeness]

Are these guys insane? Everybody's waiting for 5.6.1 to close some glaring bugs in what's supposed to be a LTS release and they announce 5.7 instead?

Did you expect no feature releases at all during 5.6's support cycle?
Bug fixes get applied to both branches.

[Steffo]

This isn't about an isolated bug fix. It's about not fixing a few critical bugs (there's like 3-4 left right now) and instead spending the available resources on a whole new friggin' release.

Again, there are certain developer who are responsible for fixing these bugs. What are you suggesting? Every Qt developer should spent his time with these 3-4 bugs? This is not very efficient...

[Noee]

This isn't about an isolated bug fix. It's about not fixing a few critical bugs (there's like 3-4 left right now) and instead spending the available resources on a whole new friggin' release.

Fwiw, there's also this 5.6.1 release comment. Looks like the blockers are resolved and we'll get officicial 5.6.1 within a week.

[bug77]

Again, there are certain developer who are responsible for fixing these bugs. What are you suggesting? Every Qt developer should spent his time with these 3-4 bugs? This is not very efficient...

That's what we do. Fix our crap before moving forward, bringing in guys from other areas of the project if needed. Then again, our products are commercial and our clients don't tolerate (critical) bugs that well.

Noee If you go here: https://bugreports.qt.io/browse/QTBU...%20%3D%205.6.1 there's still important stuff that hasn't been fixed.
And if you check the P0s and P1s reported against 5.6.0 that still await a fix, the list is much, much longer

[RahulSundaram]

That's what we do. Fix our crap before moving forward, bringing in guys from other areas of the project if needed. Then again, our products are commercial and our clients don't tolerate (critical) bugs that well.

Perhaps they have more customers who need the new features and less of them affected by the open bug reports. Not every commercial product has the same requirements to prioritize bug fixes over everything else.