[Development] Staging of qtdeclarative changes has been blocked while we try to unpin the qtbase SHA1

[Richard Moore]

On 12 March 2012 17:56,  <kent.hansen at nokia.com> wrote:
> Besides flaky tests, we also have the general/recurring problem of changes going into qtbase that break qtdeclarative (and possibly/likely other modules). While I realize it's time-consuming for everyone to manually build and run the qtdeclarative tests (or entire qt5.git) when you're working on qtbase, please at least take the time to consider how your change might affect other modules. If you're unsure and/or would like someone else's opinion on the possible impact, feel free to send an email to this list, or ask on IRC. Thanks.

Do you have any idea of how many of these were due to QtDeclarative
making assumptions that aren't part of the defined API, vs how many
were changes in expected behaviour? If you have identified cases of
the latter then we should be adding unit tests for them, if we have
cases of the former then tbh that's a bug in QtDeclarative.

Cheers

Rich.