Budgeting & investing in features ...
slacka
lukebenes at hotmail.com
Sun Dec 11 23:52:19 UTC 2016
Here are some ideas
* Regular scan-build reports like we do with CppCheck[1]
* Improve CppCheck (uncheck low priority/quality warnings, show new detected
problem since last run, and [2]).
* More variety in Jenkins bots like switching 1 of Linux to 32-bit or adding
64-bit MSVC 2015
* Improve tinderboxes so they are better at reporting when a commit range
broke them
[1] https://wiki.documentfoundation.org/Development/Clang_Code_Analysis
[2]
http://nabble.documentfoundation.org/Re-Libreoffice-commits-core-git-cppcheck-style-fix-for-noExplicitConstructor-in-writerfilter-tp4201803.html
--
View this message in context: http://nabble.documentfoundation.org/Budgeting-investing-in-features-tp4202090p4202424.html
Sent from the Dev mailing list archive at Nabble.com.
More information about the LibreOffice
mailing list