[jira] [Updated] (MESOS-2777) Treatment of new Coverity issues

["Joerg Schad (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Schad updated MESOS-2777:
-------------------------------
    Description: 
[Coverity|http://www.coverity.com/] is an static code checker. Being an open source project Mesos is scanned for free in regular intervals, but the report is only send to people registered to the coverity project (https://scan.coverity.com/projects/711).

Currently the report is usually forwarded to the dev mailing list and people create Jira tickets for the severe issues. Still, we should define a more formal approach to dealing with these reports.




  was:
Coverity is an static code checker. Being an open source project Mesos is scanned for free in regular intervals, but the report is only send to people registered to the coverity project (https://scan.coverity.com/projects/711).

Currently the report is usually forwarded to the dev mailing list and people create Jira tickets for the severe issues. Still, we should define a more formal approach to dealing with these reports.





> Treatment of new Coverity issues
> --------------------------------
>
>                 Key: MESOS-2777
>                 URL: https://issues.apache.org/jira/browse/MESOS-2777
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Joerg Schad
>
> [Coverity|http://www.coverity.com/] is an static code checker. Being an open source project Mesos is scanned for free in regular intervals, but the report is only send to people registered to the coverity project (https://scan.coverity.com/projects/711).
> Currently the report is usually forwarded to the dev mailing list and people create Jira tickets for the severe issues. Still, we should define a more formal approach to dealing with these reports.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)