[Releasing] [Development] Change file process & improvement proposal

Edward Welbourne edward.welbourne at qt.io
Fri Nov 11 11:14:26 CET 2016

On Thu, Nov 10, 2016 at 12:38:41PM +0000, Jani Heikkinen wrote:
>> Lately it has been quite hard to get change files done for the releases.
and Ossi replied:
> oh, it's that time of the year again. :D

Speaking of which, it's also hard to get API reviews done, even though
they are now much easier (because they get represented properly as
gerrit reviews that show the change properly).  See recent mail: of 17
modules with API reviews, one has a +2 and one a +1 on the latest PS;
one has +1 on the previous; two are new reviews (I may have lost an
earlier review) with no comments; three have comments on earlier PSs;
qtwebengine's team concocted a better review (that's rather out of date)
and have reviewed it; qtserialbus's maintainers note the need for a full
API review; but seven add-on modules have had no comments.  (Three of
these were new in 5.7; the rest have been add-ons since at least 5.6.)

Gerrit's diffs between patch sets work for you here: if you've reviewed
an earlier patch set, you can review the change since in the usual
useful way.  No rebasing has happened.

Please review (changelogs and) changes to your module APIs,


More information about the Releasing mailing list