AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090729164030.4679ab0d@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<bfisher@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 29 Jul 2009 16:41:44 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Bill Fisher <bfisher@onstor.com>
Subject: dev plan mods
Message-ID: <20090729164144.37acf93a@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

So, I'm hearing you saying that you think the testing time estimate is
too low as represented in the Dev plan, and put together with what you
sent me, I'm thinking I need to make some mods.  I want to get your
input on that.

Should I add, say, 2 weeks, as a separate new task for testing?  Or
should I add a new sub-task to task #2 that breaks out another bunch of
testing and change 5 weeks for #2 to 7 weeks?  In task #2, I've said
that work on RMC tests (2.6) will begin after the first QA code drop, so
keep that in mind.  That means that after the first QA code drop,
several weeks can be put into RMC test development and debugging, and
also possibly other tests.

Thanks,

a
