> -----Original Message----- > From: Prasanna Santhanam [mailto:t...@apache.org] > Sent: 24 July 2013 10:02 > To: dev@cloudstack.apache.org > Subject: Re: New Components on JIRA > > On Tue, Jul 23, 2013 at 05:23:03PM +0000, Ram Ganesh wrote: > > > -----Original Message----- > > > From: Prasanna Santhanam [mailto:t...@apache.org] > > > Sent: 23 July 2013 22:36 > > > To: CloudStack Dev > > > Subject: New Components on JIRA > > > > > > The following new components have been added to JIRA to narrow down > > > issues into the right buckets. > > > > > > (name, description) > > > --- > > > * Infra - Infrastructure managed by the project - CloudStack - > > > (jenkins, builds, repos, mirrors) > > > * SystemVM - SystemVM appliances, images, scripts, ssvm, cpvm > > > * Virtual Router - Anything related to the Virtual Router appliance > > > * XCP - Xen Cloud Platform > > > --- > > > > > > Anyone see any problems? > > > > Prasanna, > > > > How about - automation-product and automation-script components? > > Automation-product for all product bugs discovered by the automation > > engine and automation-script for all automation script issues? > > > > Right now - that distinction is not clear at least from the bug reports. We're > reusing the same report for both script and product failure. So anything filed > from an automated test failure should just be automation and on further > analysis if it is found to be product failure, a clearer bug report would be > necessary within the right component of the product - api, network, > systemvm etc. >
Yes you are right. Component is not the right field. Maybe we could use Label. A JIRA report which reports product issues discovered out of automation will be very valuable. Maybe label is a field for that. > -- > Prasanna., > > ------------------------ > Powered by BigRock.com
