Likitha, you may change the Subject line to read something like this: [UI] Sub-Task Vs New Defct --WAS (RE: [DOC] New Feature Documentation: Doc Defect Vs Sub-Task Under New Feature Defect)
-----Original Message----- From: Likitha Shetty [mailto:likitha.she...@citrix.com] Sent: Sunday, January 06, 2013 12:08 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [DOC] New Feature Documentation: Doc Defect Vs Sub-Task Under New Feature Defect Similar to the sub tasks being created for functional testing and doc under each new feature, is it possible to include a sub-task for the UI work associated with a feature as well? This would help avoid confusion like this one - https://issues.apache.org/jira/browse/CLOUDSTACK-725. Thank you, Likitha > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Friday, January 04, 2013 5:40 PM > To: <cloudstack-dev@incubator.apache.org> > Subject: Re: [DOC] New Feature Documentation: Doc Defect Vs Sub-Task > Under New Feature Defect > > Sub-task is best please. > > - chip > > Sent from my iPhone. > > On Jan 4, 2013, at 6:41 AM, Radhika Puthiyetath > <radhika.puthiyet...@citrix.com> wrote: > > > Hi Community, > > > > Here is a query with respect to the new feature documentation tasks. > > > > What is the right process to submit a new feature documentation: > > Creating > an independent DOC-DEFECT for each feature that is going in for the > release, or creating a SUB-TASK for the respective new feature defects. > > > > Thanks > > -Radhika > > > > > > > >
