incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Animesh Chaturvedi <animesh.chaturv...@citrix.com>
Subject RE: [DISCUSS]Jira process for sub-features
Date Wed, 23 Jan 2013 21:53:26 GMT


> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Wednesday, January 23, 2013 1:39 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS]Jira process for sub-features
> 
> On Wed, Jan 23, 2013 at 1:27 PM, Animesh Chaturvedi
> <animesh.chaturvedi@citrix.com> wrote:
> > Folks
> >
> > As we are approaching 4.1 code freeze, we should clarify the process on
> features that are not complete yet but a sub set of functionality that is useful
> is complete. Jira supports sub-tasks and we have used it for few longer and
> complex features like IPv6 and seems an obvious choice.
> >
> > I have following questions:
> > 1) Parent Task 'Fix Version' :  Should this field continue to reflect the
> release it was originally targeted like 4.1 or it should reflect the 'Fix release' of
> the most recent sub-task that is in progress or  to 'Future'?
> > 2) Parent Task 'Status' : If few sub-tasks are 'In Progress' should
> > parent status be 'In Progress' too? Or it should be left at 'Open' I
> > don't think parent task automatically track sub-task status
> >
> > We also need to remember to include sub-task in the report of issues for a
> release.
> >
> > Thanks
> > Animesh
> 
> One other request...  when moving things around, please be sure to move
> the QA and Doc sub tasks (as well as the design and requirement wiki pages)
> to the new target release.
[Animesh>] Sure will do that, Ram Ganesh, Abhi please make a note of this

Mime
View raw message