cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sudha Ponnaganti <sudha.ponnaga...@citrix.com>
Subject RE: QA Process Question
Date Mon, 11 Feb 2013 15:19:21 GMT
A component field is available JIRA to track defects in certain areas. Linking may require
additional workflow. 
Often times people do not really categorize them properly and link them to incorrect problem
areas ie Components.  However having 2 levels of categorization would help a lot. 
Thanks for bringing it up for discussion. 

Would it be agreeable to use component and sub-component fields for this purpose?

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com] 
Sent: Monday, February 11, 2013 6:36 AM
To: Donal Lafferty
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: QA Process Question

On Mon, Feb 11, 2013 at 02:31:01PM +0000, Donal Lafferty wrote:
> Maybe it help to take the example of the Javelin refactor and ask where did it's QA issues
get tracked before the code was merged to master?
>

Bugs should be tracked in http://issues.apache.org/jira/browse/CLOUDSTACK.

I don't know if Javelin branch specific bugs were tracked anywhere.  I think that it was just
done as the collaborators working together to resolve issues.

> DL
> 
> > Also, this raises a bit of a concern in my mind.  We really don't 
> > want lots of development outside the project, than then gets 
> > "donated".  Can you be more specific about what you are talking about here?
> > 
> > -chip
> 

Mime
View raw message