Hi Andrea
Thank you for the quick answer. I'm wondering if I'm missing something or development really stopped/slowed >> down since the 4.1.1 release? >> > > I can't speak for the others. But since the latest visible commit is mine, > I've been working more on the website in recent days. > Actually my question was more in the sense "Am I looking at the right statistics?" because I find it hard to believe that with so much to be done and so many people participating, there hasn't been a code change in 7 days... > > On a separate note, from a Quality perspective it would probably would be >> a >> good idea if Apache OpenOffice code was scanned by one of these Coverity >> analysis >> > > The Apache OpenOffice code is scanned by Coverity, and (since this is > considered security-relevant) data are privately accessible to some > developers. Is it possible to make public the "project's defect density" for Apache OpenOffice? I'm quite curious since I find AOO more stable than LO. > If I recall correctly (I've never seen them), most of the reports and > metrics did not seem very useful, since they included a lot of false > positives; one could silence those warnings by writing extra code or extra > assertions just to help the analyzer understand that nothing was wrong, but > this would be merely to please the analyzer and not to enhance the real > quality. That makes sense. But there are possibly some real leaks and bugs that could be attended... > I haven't read the article you linked to yet, but if your point was > "Coverity should scan Apache OpenOffice" the answer is "This is already > happening". > Actually I meant some sort of scan, but since AOO is also scanned by Coverity then it would be interesting to know how the two compare. Regards, Pedro
