The 444 defects is an overwhelming number. Most of those automated tools detect things that turn to be valid code (upon closer inspection). Could you start by listing, say, the first 5 defects that actually make sense and are indeed flawed code that should be fixed?
Dawid On Tue, Jul 14, 2015 at 4:33 PM, Rishabh Patel <[email protected]> wrote: > Hello! > > I scanned the Lucene project with Coverity scanner. 444 defects have been > detected. > Please check the attached report on the breakup of the issues. Some of the > issues are false positives. > > I would like to volunteer for fixing these defects. > > Before I start, could you please tell me whether I should I create a single > JIRA for a kind of issue (e.g. "Concurrent data access" or "Null pointer > exception") or should multiple issues be created according to the module of > the files to be modified? > > -- > Sincerely, > Rishabh Patel > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
