AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
FMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB5175A7F5316@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 31 Oct 2008 18:25:17 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Subject: Fw: TuxRx Project Proposal
Message-ID: <20081031182517.6d4b38bb@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

erg....


Begin forwarded message:

Date: Fri, 31 Oct 2008 15:43:43 -0700
From: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Subject: RE: TuxRx Project Proposal


That would require a full pass in all areas, and depending on what we
choose to support maybe even new cases for ipv6 and other pieces. 
I would expect all the low level to be tested by dev with unit tests.
So it's probably a 3 months thing from QA's perspective to get it right.
If we have a bunch of areas automated we might save some time, but for
every new code change that comes in, it usually takes 3 passes to get
over the major bugs. Since this is core and impacts all features, that's
why it would take a while to test it. I maybe optimistic with 3 months,
it also depends how many people I would have available for this!

-----Original Message-----
From: Andy Sharp 
Sent: Thursday, October 30, 2008 11:52 AM
To: Sandrine Boulanger
Subject: TuxRx Project Proposal

Hi Sandrine,

Attached is a copy of the project proposal I told you about.  If you
have some time today I'd like to hear your thoughts on what the
QA/testing implications would be.

Thanks,

a

