AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090729163541.52fb4bc0@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB3137CE2BA69@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 29 Jul 2009 16:36:02 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Sandrine Boulanger <sandrine.boulanger@onstor.com>
Subject: Re: tuxrx dev plan
Message-ID: <20090729163602.768ae1f6@ripper.onstor.net>
In-Reply-To: <102AB4F33EBBDB4C91915B145C8E9FB3137CE2BA69@exch1.onstor.net>
References: <20090729100431.1529f802@ripper.onstor.net>
	<102AB4F33EBBDB4C91915B145C8E9FB3137CE2BA69@exch1.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: quoted-printable

OK, that's some good feedback, let me think about that.

Just to clarify some things, this was not meant to cover any QA
testing, only Dev testing prior to the first QA code drop.

=46rom my perspective, I can't imagine that we can do targeted testing in
QA as an overall plan: it would seem to be a full sweep at some point.
Not sure if that's a dog that won't hunt but we can discuss that.

The builds will be done by Larry in the usual way, we will be building
from the tuxrx branch.

As for the rest of the junk-ola in dev, that's probably something we
need to kick around at tomorrow's chat, in addition to what is and
isn't possible in the QA plan.  I will be taking a lot of stuff from
dev, but I'm open to the idea of excluding certain specific things you
might want left out.

Cheers,

a

On Wed, 29 Jul 2009 14:48:00 -0700 Sandrine Boulanger
<sandrine.boulanger@onstor.com> wrote:

> Well, this plan is very high level and does not explain which areas
> are impacted. There are also sections that say test but only for some
> items, we need to be able to test all the items eventually from a
> unit test perspective. We can start QA in parallel, probably not more
> than 1 or 2 persons to begin with. You should also plan to run some
> of the automated tests before the drop to QA if possible. Is this
> really the exhaustive list of tasks? We need to figure out which area
> of the code (from a black-box perspective) is impacted by each of
> those changes. Also, from which branch will we get the builds from?
> The dev build has already extra code from India about mirror check
> pointing and tree quota on populated directory, which would add quite
> a lot to the testing, and who knows what else has been dropped in
> there!
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, July 29, 2009 10:05 AM
> To: Sandrine Boulanger
> Subject: tuxrx dev plan
>=20
> Hi Sandrine,
>=20
> I've put together the beginnings of a Dev plan, but it seems to be
> missing stuff, I'm hoping you can tell me what.  Do I need to make a
> list of code drops and what is expected to be in them and like that or
> is that silly?  It would be just a bunch of major guesswork.  There
> was a spreadsheet or something like that for the Cougar project, but
> of course this project is much different.
>=20
> Cheers,
>=20
> a
>=20
> PS You can find a link to the Dev plan on the wiki page:
>=20
> http://wiki.onstor.net/wiki/TuxRx
>=20
