is it OK for everybody that I release 2.17 in the weekend?
There are many bugfixes that I would like to share with our users.
I will take a quick look at our crashes (http://cppcheck1.osuosl.org:8000/crash.html) before starting the release process.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On Windows 11, when Cppcheck 2.17.1 is in dark mode, the "Warning Details" edit window is still in light mode, while "Analysis Log" output is in dark mode.
I suggest that we start preparing for cppcheck 2.17 release.
feel free to continue merging larger refactorings and improvements for 1-2 weeks more . and after that I suggest a focus on fixing bugs.
maybe we can release 2.17 in end of january
is it OK for everybody that I release 2.17 in the weekend?
There are many bugfixes that I would like to share with our users.
I will take a quick look at our crashes (http://cppcheck1.osuosl.org:8000/crash.html) before starting the release process.
No objections from my side. The known crashes should be fixed by now.
i see the new release with QT6
how about make release with QT5 ?
On Windows 11, when Cppcheck 2.17.1 is in dark mode, the "Warning Details" edit window is still in light mode, while "Analysis Log" output is in dark mode.
I filed https://trac.cppcheck.net/ticket/13677 about this.
I cannot reproduce the issue on my system (Windows 10) but are seeing different issues.