Hi all,

QML API review documents uploaded now, thanks to Max: 
https://codereview.qt-project.org/q/topic:%22api-change-review-6.3%22+(status:open%20OR%20status:merged)

br,
Jani

________________________________________
From: Development <development-boun...@qt-project.org> on behalf of Marc Mutz 
<marc.m...@qt.io>
Sent: Tuesday, February 1, 2022 4:47 PM
To: development@qt-project.org
Subject: Re: [Development] HEADS-UP: call for Qt 6.3 API review

Hi,

There were still several modules unreviewed, and quite some with issues
found (there are a few more now) which appear unfixed (link in the
review to the fix, please).

Since the hit rate was so high, I also went through the already-appoved
ones, and bingo, found the addition of a virtual function, approved now
for the second time (first when merged, now in review).

Please restrain from giving a +2 on the API reviews if you have not read
and understood
https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B#The_Do.27s_and_Don.27ts
first.

I sure hope we didn't miss something like that in 6.2's review (and if
we did, we now know how our users value the BC guarantee :)

Thanks,
Marc
________________________________
From: Development <development-boun...@qt-project.org> on behalf of Jani 
Heikkinen <jani.heikki...@qt.io>
Sent: Thursday, January 20, 2022 12:13 PM
To: development@qt-project.org <development@qt-project.org>
Subject: [Development] HEADS-UP: call for Qt 6.3 API review

Hi all,

It is time to do a API review for Qt 6.3 now. Diffs are here: 
https://codereview.qt-project.org/q/topic:%226.3+API+Review%22
Please do the review asap; we need to compete it as soon as possible.

Follow-up task in Jira: https://bugreports.qt.io/browse/QTBUG-99883

br,
Jani
_______________________________________________
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

Reply via email to