Hi,
I would like to provide a small status of the coverity builds and ask for some
help. The last weekend
the analysis failed because lower than a threshold of C++ code could be parsed.
The coverity analysis
tool is executed alongside the compiler when building qt5. This has occurred in
the past and I dealt
with it by first trying to upgrade the analysis tool and then ending up
disabling C++1X support in Qt.
Now disabling C++1X isn't an option anymore but luckily the new analysis tool
can parse enough of
Qt to generate a scan result and the new results were uploaded, analyzed and we
have a ton of new
potential issues raised by it. It would be great if we could have a look and
try to clear these new issues
quickly.
The build is done every Saturday on a Ubuntu 14.04 system and the result is
then uploaded to coverity,
the build is always done from the dev branch and I wonder if in front of a
release we shouldn't be tracking
the release branch instead. Preferable the dev->release->dev switch would be
done something that does
happen automatically. Shall we build the release branch close to a release? Is
there an indicator a script
could see if we are close to the release?
kind regards
holger
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
