Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 14 Oct 2014 10:52:34 +0000 (UTC)
From: "Santhosh Kumar Edukulla (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12747988.1413283936000.261932.1413283954629@Atlassian.JIRA>
In-Reply-To: <JIRA.12747988.1413283936000@Atlassian.JIRA>
References: <JIRA.12747988.1413283936000@Atlassian.JIRA>
 <JIRA.12747988.1413283936350@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-7707) Triage and fix Coverity defects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Santhosh Kumar Edukulla updated CLOUDSTACK-7707:
------------------------------------------------
    Assignee: Jayapal Reddy  (was: Santhosh Kumar Edukulla)

> Triage and fix Coverity defects
> -------------------------------
>
>                 Key: CLOUDSTACK-7707
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7707
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Santhosh Kumar Edukulla
>            Assignee: Jayapal Reddy
>             Fix For: 4.5.0
>
>
> 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)