Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A57D0E473 for ; Sun, 6 Jan 2013 08:09:42 +0000 (UTC) Received: (qmail 53685 invoked by uid 500); 6 Jan 2013 08:09:42 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 53366 invoked by uid 500); 6 Jan 2013 08:09:42 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 53342 invoked by uid 99); 6 Jan 2013 08:09:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Jan 2013 08:09:41 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of radhika.puthiyetath@citrix.com designates 203.166.19.134 as permitted sender) Received: from [203.166.19.134] (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Jan 2013 08:09:36 +0000 X-IronPort-AV: E=Sophos;i="4.84,419,1355097600"; d="scan'208";a="282344" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 06 Jan 2013 08:09:12 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.72]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Sun, 6 Jan 2013 13:39:11 +0530 From: Radhika Puthiyetath To: "cloudstack-dev@incubator.apache.org" Date: Sun, 6 Jan 2013 13:38:58 +0530 Subject: [UI] Sub-Task Vs New Defct --WAS (RE: [DOC] New Feature Documentation: Doc Defect Vs Sub-Task Under New Feature Defect) Thread-Topic: [UI] Sub-Task Vs New Defct --WAS (RE: [DOC] New Feature Documentation: Doc Defect Vs Sub-Task Under New Feature Defect) Thread-Index: Ac3r5QOYJ2IqiTg2QciazBrsYrLqtQ== Message-ID: <97F4356AEA71904482CD192135C038F901185E4B0321@BANPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org 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.shetty@citrix.com]=20 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 ass= ociated with a feature as well? This would help avoid confusion like this one - https://issues.apache.org/j= ira/browse/CLOUDSTACK-725. Thank you, Likitha > -----Original Message----- > From: Chip Childers [mailto:chip.childers@sungard.com] > Sent: Friday, January 04, 2013 5:40 PM > To: > Subject: Re: [DOC] New Feature Documentation: Doc Defect Vs Sub-Task=20 > Under New Feature Defect >=20 > Sub-task is best please. >=20 > - chip >=20 > Sent from my iPhone. >=20 > On Jan 4, 2013, at 6:41 AM, Radhika Puthiyetath=20 > wrote: >=20 > > 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:=20 > > Creating > an independent DOC-DEFECT for each feature that is going in for the=20 > release, or creating a SUB-TASK for the respective new feature defects. > > > > Thanks > > -Radhika > > > > > > > >