Jani Heikkinen (6 September 2017 06:53) > Meeting minutes from Qt Release Team meeting 5th September 2017 > > Qt 5.10 status: [...] > - API review to be started immediately when Alpha content in place
No API changes found in: qtsvg, qtactiveqt, qtscript, qttools, qtxmlpatterns, qtsensors, qtimageformats, qtgraphicaleffects, qtquickcontrols, qtserialport, qtmacextras, qtwinextras, qtwebsockets, qtwebchannel, qtcanvas3d, qtwebview, qtquickcontrols2, qtpurchasing, qtcharts, qtdatavis3d, qtvirtualkeyboard, qtgamepad, qtspeech. If you believe there have been changes to APIs in these modules, between v5.9.0 and the 5.10 branch, please bring them to my attention. Note that the introduction of QStringView is in this review. I was surprised to find qtbase/src/3rdparty/zlib/ contributing; but it is indeed mentioned in sync.profile, so got included. Change reviews generated: https://codereview.qt-project.org/205317 -- qtbase https://codereview.qt-project.org/205318 -- qtdeclarative https://codereview.qt-project.org/205319 -- qtmultimedia https://codereview.qt-project.org/205320 -- qtlocation https://codereview.qt-project.org/205321 -- qtconnectivity https://codereview.qt-project.org/205322 -- qtwayland https://codereview.qt-project.org/205323 -- qt3d https://codereview.qt-project.org/205324 -- qtserialbus https://codereview.qt-project.org/205325 -- qtx11extras https://codereview.qt-project.org/205326 -- qtandroidextras https://codereview.qt-project.org/205327 -- qtwebengine https://codereview.qt-project.org/205328 -- qtscxml https://codereview.qt-project.org/205329 -- qtnetworkauth https://codereview.qt-project.org/205330 -- qtremoteobjects Please note that the API review, though presented as a change to 5.10, is in fact a simplified diff between v5.9.0 and the current 5.10 branch, in which certain kinds of "boring" change are ignored. This can lead to the end-state you're shown not matching what you know the code currently says; this is just because the script tried to leave out irrelevant differences between 5.9.0 and 5.10, so that you can focus on how the API and ABI might have changed. I've restored constexpr changes to being shown - allegedly we can't retract those once added. I believe Q_INVOKABLE is also genuinely API-relevant, so it is also not filtered. Should Q_DECL_CONST_FUNCTION changes be ignored ? Q_NORETURN ? The currently aren't. I have arranged for the script to ignore #if QT_CONFIG(token) replacing #ifndef QT_NO_TOKEN (complete with the various ways that can be spelt, but without the matching handling of #endif comments). There were a lot of those in this review, otherwise; likewise for while (0) being turned into while (false). Eddy. _______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing
