On Sat, Feb 7, 2015 at 10:31 PM, Jean-Marc Lasgouttes <[email protected]> wrote: > Le 07/02/15 03:41, Liviu Andronic a écrit : >> >> Dear all, >> Following on this very old proposal, I went ahead and submitted the >> LyX code for static analysis to Coverity: >> https://scan.coverity.com/projects/4164 >> >> Coverity has uncovered ~250 implementation defects in the LyX code >> base, with 10 or so of high severity (memory corruption, resource >> leaks, etc.) To view the defects, you need to connect with your Github >> account (or create one with Coverity) and request 'Add me to project' >> (which I shall then approve). Coverity provides overall metrics like >> defect density (LyX scores a respectable 0.53), but also classifies >> uncovered bugs by type and severity, and provides a nice UI trying to >> explain to the devels the specifics of the bug and how to address it >> (e.g. where it happens, why it's an issue, etc.) > > > That is really a great idea. Lots of things to fix, yum! > Yay! Glad you all like it! :)
I propose that whenever someone finds some item particularly yummy, and they start looking more closely into the issue, that they nominally assign themselves to that item so that others would know that someone is already working on it. (OK, that was unnecessarily verbose, even if surprisingly precise, but I hope it's excusable given that it's quite late here...) Cheers, Liviu > JMarc > -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
