X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C6FEB4.1E7896E3@onstor-exch02.onstor.net>; Thu, 2 Nov 2006 11:21:38 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Assignments for Clio
Date: Thu, 2 Nov 2006 11:21:38 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E01384461@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04EBC8C1C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Assignments for Clio
thread-index: Acb+GOMx8F9TLuWLTaeEJsZxleB40QAiPWlJAARRDHA=
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "Paul Hammer" <paul.hammer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Jerry Lopatin" <jerry.lopatin@onstor.com>

Paul and cc's,

This is excellent. A few specific comments below, in the text.

jay=20

-----Original Message-----
From: Paul Hammer=20
Sent: Thursday, November 02, 2006 9:27 AM
To: Jay Michlin; Andy Sharp
Cc: Jerry Lopatin
Subject: FW: Assignments for Clio

Hi Folks,
=20
FYI: After the resource balancing activity done by Sandrine for Clio;
test complete is now on 12/7, this is a week later than I was hoping
for. We do not have any wiggle room on this one from a QA perspective,
as noted in my earlier mails we have to be vigilant (that is make tough
calls right from the beginning) not to take in anything that is outside
of the scope of Clio as we have defined it.=20

Jay >> Still, it does support the 12/18 ship date providing we're
disciplined about sticking with that commitment and shedding features if
necessary to meet it. I think we're all agreed on that, and we're all
aligned in reminding the team about it regularly.
=20
As you can see from the strategy we are doing the core test pass first
to find the big problems early, after completion of core (in about 3
weeks) we will them move to the full set and will complete by 12/7. If
we reach RC by 12/7 we then will do a final regression pass in parallel
with running the RC on MD, testing will conclude on 12/17
=20
Should we lock the branch on Clio and only open it at the Dev leads
request for MF checkins so as to avoid things getting checked into the
wrong branch?

Jay >> That sounds right.
=20
BTW, is Tim still the lead for Clio now that we moved the DMIP stuff to
Lambo?

Jay >> Tim remains lead for this "Clio". In addition, Charissa remains
lead for all Web UI activity and decisions. We need to identify leads
for Lambo and Delorean.

The MF list is small right now, around 12 defects, this seems
manageable, love to get these all addressed in the first half of the
project.  So far we have found 4 showstopper bugs, good stuff finding
them so early, that was the plan. I recommend that we punt everything
that is on the Non-MF list that is not web ui specific. Any problems
with that?
=20
Web UI, do we need to support the latest versions of Firefox and ME
(both are just now being released)? We have already founds bugs that are
specific to these versions.

Jay >> Charissa decides.
=20
Please do not share these plans as Sandrine is still vetting them and
adjusting them based on feedback from HCL and her team, she will then
send out the plans and associated QA schedule.

Jay >> I'd love to share this message with Tim, Brian and Charissa
because it contains lots of excellent and consolidated information.
Also, it shows Sandrine giving nice direction to her HCL team in keeping
with what we asked. But I won't forward it unless you say it's okay.
=20
Jay, as you requested Sandrine has included the defect reporting
guidelines in this mail for all the QA folks (mostly intended for HCL,
but can't hurt to reiterate it locally)
=20
Thanks,
=20
-Paul

Jay >> End of my comments in the text (no more below).

________________________________

From: Sandrine Boulanger
Sent: Wed 11/1/2006 4:50 PM
To: dl-QA; dl-hcl-qa
Subject: Assignments for Clio



Please check the 2 attachments for the various tasks and assignments for
Clio. If we agree on this, we'll send it to Andy to create a schedule so
that we can track our progress.

We have a submittal coming up that will be the official Submittal#1 for
Clio, it will be released tonight.

For the problems that were already found with previous pre-build from
Sunday, file the defects against Submittal#1 but please indicate in the
defect (for example at the beginning of the description) which build
string you were using (from system show version).

Please make sure to include the steps to reproduce in each defect you
file, include location of core file if any, elogs (from all nodes if in
cluster), ndmp trace or any other log. For the elogs, please have a look
at them before attaching/copying them,  to frame the information that is
relevant to the defect (or indicate in the description the timestamps
where the problem starts/stops). Same thing goes for the cores. If you
can get the stack trace from gdb, that usually helps categorize the
problem area.

We'll provide information for the areas that are missing the test cases
location in the excel sheet (for example SSH Keys). There are also some
areas where we need to create more cases (for example data migration, we
need to extend the cases for rsync, and the -S volume option). I'll
follow that up in a separate email.

For the tests cases, start first with a core regression of each area.
Once you're done continue with the full regression (the remaining of the
test cases for each area).

For backup/restore, we'll do core for Legato, but a full for Veritas.

We still need to meet with elab to go over some of the configurations
we'll need.

Thanks and send me your concerns/comments if any.

Sandrine.

<<Regression_To_do_list.xls>> <<Resources.xls>>=20

