cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prasanna Santhanam <>
Subject Re: [ACS41][QA]QA Scrum MoM - 1/8/2013
Date Thu, 10 Jan 2013 05:50:33 GMT
Super! Thanks for sending these out. May be I can drag myself out of
bed for this at least next time round.

Some questions and remarks inline:

On Wed, Jan 09, 2013 at 04:50:02PM -0500, Sudha Ponnaganti wrote:
> QA Scrum MoM  1/8/2013:
> Resources:
> ACS 41 QA wiki:
> MoM will be posted on wiki :
> MoM:
> 0. This is very first meeting to kick off ACS  4.1 QA
> 1.Sudha is working on updating JIRA QA Subtasks for New
> features/Improvements with QA owners. David and Chip have already
> created several subtasks. Sudha created a few.  Few features already
> have QA owners. Will be finishing up rest shortly.
> 2. QA is reviewing FS and they will start working on Test plans and
> will post them to community for review.

Good to see the reviews coming out for PRDs and FS proposals. Once
Chip has finalized the full feature set for 4.1 would be better to
start on test planning, right? Just wondering - what if a feature gets
vetoed and tests have been churned out.

> 3. Builds are being done for ACS Master and setting up automation (
> Junit/BVTs and Regression) to ensure sanity of master branch.

You mean - Apart from [1] and [2]?

> 4. Discussion happened around number of features and Jan 31 code
> complete deadline. This is something that will be discussed in
> mailing list as everyone has similar concerned. Chip mentioned that
> we will go with time based release only.
> 5. Also discussed test code donation and current pending tasks. Chip
> has given over  the process of submission and approval.

w00t! there are more tests that can be put up apart from the ones I
pushed for VOTE?

> 6. Sailaja wanted to confirm if we still follow the same install
> matrix that we did for previous releases and Sudha confirmed that
> there is no change.
> 7. Abhinav wanted to get developer drops so he can work on
> automation. Sudha advised to bring this up in community forum to get
> builds. Should not be an issue .
> 8. Mike T informed forum that he started to attending meetings and
> he may contribute more in future.



View raw message