cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7708) Triage and fix Coverity defects
Date Thu, 09 Jul 2015 09:08:04 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620157#comment-14620157
] 

Daan Hoogland commented on CLOUDSTACK-7708:
-------------------------------------------

[~santhoshe] [~kishan] This seems more like a running task then an issue to me. I think we
should triage coverity and create a jira ticket if one of the findings merits it. i.e. is
to much work for a single commit marked with the coverity finding id.

I sugest we close this ticket as 'won't fix', ok?

> Triage and fix Coverity defects
> -------------------------------
>
>                 Key: CLOUDSTACK-7708
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7708
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Santhosh Kumar Edukulla
>            Assignee: Kishan Kavala
>             Fix For: Future
>
>
> 1. We have Coverity setup available, running as scheduled and individual owners are assigned
with analyzed bugs.
> 2. As part of this bug, please triage and fix the relevant Coverity bugs assigned. It
could be a count as small as 25 bugs.
> 3. First start with high impact in order to others later.
> 4. We can either triage them accordingly as fix required or false positive or not a bug
accordingly. But, triage and fix accordingly wherever relevant and applicable.



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

Mime
View raw message