Hi! API review seems to be still ongoing. Please make sure all reviews are ready at the end of next week (4th October EOB).
br, Jani ________________________________________ From: Development <development-boun...@qt-project.org> on behalf of Jani Heikkinen <jani.heikki...@qt.io> Sent: Monday, September 16, 2019 1:32 PM To: Edward Welbourne; development@qt-project.org Subject: Re: [Development] 5.14 API change reviews Hi all, It seems this is still badly ongoing. Even Alpha isn't out yet we should be able to finalize these as soon as possible. So please do reviews now & get reviews approved as soon as possible. br, Jani ________________________________________ From: Development <development-boun...@qt-project.org> on behalf of Edward Welbourne <edward.welbou...@qt.io> Sent: Monday, August 26, 2019 7:14 PM To: development@qt-project.org Subject: [Development] 5.14 API change reviews Hi all, As some have clearly noticed unprompted, I've now posted the first drafts of the 5.14 API change reviews [0], in accordance with QUIP 10 [1]. Please file bugs in Jira for any changes you object to and link those bugs to QTBUG-77839 [2], blocking it. Please tag any changes you make to fix issues noticed in review, either with Fixes: for such a bug report or with a Task-number: QTBUG-77839 footer. As ever, remember that these reviews filter out lots of trivial changes, so check the actual 5.14 (and, where relevant, 5.13.1) sources if in doubt about what's really there. The boring changes filtered out of qtbase totalled more than twice the residue presented for review. [0] https://codereview.qt-project.org/q/topic:%2522api-change%2522+status:open [1] https://quips-qt-io.herokuapp.com/quip-0010-API-review.html [2] https://bugreports.qt.io/browse/QTBUG-77839 Feature freeze has happened, so please make no changes to 5.14's public APIs other than fixes in response to these reviews. If you know a module has had material changes requiring an update to the review, please either read the commit message (it says how to update it) or drop me a line, Eddy. _______________________________________________ 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 _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development