Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sudha.ponnaganti@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Sudha Ponnaganti <sudha.ponnaganti@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Wed, 2 Jan 2013 13:28:29 -0800
Subject: RE: [ACS41][QA] Testing process for 4.1.0
Thread-Topic: [ACS41][QA] Testing process for 4.1.0
Thread-Index: Ac3pLyGtKLDM/RfPSwa+6By/MgsO1wAAB1MA
Message-ID: 
 <7914B38A4445B34AA16EB9F1352942F1012F142D0690@SJCPMAILBOX01.citrite.net>
References: 
 <CA+96GG7Eaq-siNS3VtuxZ3EAS+kCCTnZnFMw3H2sDNKM+Xnc7g@mail.gmail.com>
In-Reply-To: 
 <CA+96GG7Eaq-siNS3VtuxZ3EAS+kCCTnZnFMw3H2sDNKM+Xnc7g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Chip,

I am working on the areas to be tested and plan of execution as we speak - =
will be publishing it shortly.  I have been following all the threads poste=
d so I have context for areas to be tested.=20
If there are no objections (or volunteers), I definitely would like to take=
 up QA Lead  role for 4.1.

Thanks
/Sudha

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]=20
Sent: Wednesday, January 02, 2013 1:21 PM
To: cloudstack-dev@incubator.apache.org
Subject: [ACS41][QA] Testing process for 4.1.0

Hi all,

In our continued efforts to improve our community processes, I'd like to pr=
opose a little bit of a change in how we go about the QA process for our re=
leases (to take effect in the 4.1.0 release cycle).

My motivations are to increase:
1) the visibility of test engineers that have already been working on the p=
roject (especially those that happen to work for Citrix, but that aren't ve=
ry visible to the larger community)
2) the diversity of the community members formally testing the releases (e.=
g.: provide an opportunity for non-Citrix contributors to be part of the fo=
rmal QA processes)

So what I'd like to propose is that someone volunteer to be the "QA lead" f=
or the release (Sudha, I'm looking in your general direction...
;-) ).  The QA lead can then pull together the list of test cases (or gener=
al areas of testing).  The list and actual test scenarios would need to be =
public.

Once the basic test strategy is in place, we hold "a call for testers"
to get the volunteer test army assembled.  (I'd love to see contributors fr=
om throughout the community step up to own some test
cases.)  I'd suggest that we do this as a process of assignment via volunte=
ering, so that the opportunity exists for new community members to grab a t=
est or two.

I know the changes aren't really that significant...  but the idea is to ge=
t the testing process opened up completely as a community activity.

Does this make sense?  Thoughts?  Comments?  Flames?

-chip