It appears they've moved forward to Qt5 but they're still running on QtWebKit. This is a bad situation since QtWebKit has been deprecated (read: nobody has publicly committed to writing any new code for it, not least Digia) in favour of QtWebEngine, which doesn't have even 10% of the API richness of the old module.<p>WebEngine implements process separation and is based on Blink, whereas WebKit was in-process and e.g. allowed direct access to DOM from C++.<p>The job of moving PJS to WebEngine, if possible, when it happens will basically be the same effort as a rewrite. This release looks like a stopgap to get the best of the old WebKit line, but calling it 2.0 seems a bit shortsighted -- 2.0 should be kept for the WebEngine series if/when it happens.