X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8906F.3A8447C0@onstor-exch02.onstor.net>; Thu, 27 Mar 2008 18:01:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Desired goal of in-branch testing of FTI/migration
Date: Thu, 27 Mar 2008 18:01:17 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05C7458E@onstor-exch02.onstor.net>
In-Reply-To: <20080327171806.7ee80a6a@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Desired goal of in-branch testing of FTI/migration
Thread-Index: AciQaTIwoGFuZDivQtqdCQHwzSxJpAABUPcg
From: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>,
	"Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Manohar Divate" <manohar.divate@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>,
	"John Keiffer" <john.keiffer@onstor.com>

Thanks Andy, more details is always better, and this way we have some
criteria set for the merge to dev branch.
Yes we've already started down this path.=20
Vikas/Manny/John, we should have a summary of results for those.
I know that John went directly to FTI after upgrading to this in-branch
build, this is something we don't want to see if we merge it to dev.

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, March 27, 2008 5:18 PM
To: Sandrine Boulanger
Cc: Tim Gardner; Sripal Surendiran (HCL); Manohar Divate; Vikas Saini
Subject: Desired goal of in-branch testing of FTI/migration

Hi Sandrine,

I'm sending this as a follow up to the remarks in the core team meeting
regarding the in-branch testing of the FTI/migration code.

It seemed like everyone was having a hard time understanding what I was
trying to say, so I will summarize here for everyone.  Hopefully I will
be clearer this time.

We need to get the FTI/migration code merged into the dev branch as soon
as possible.  The criteria for that is as follows:

A) The changes don't disrupt or represent a substantial risk to
currently functioning features or workflows in the dev tree.

B) The proper functioning of the new migration features or Linux FTI
capabilities are not important -- these can be dealt with in the dev
branch, as long as (A) is observed.  If these things have problems, then
the beta branch can be created without this change, and after the
problems resolved then it all can be integrated to the beta branch.

So basically this translates to:

* do in-branch testing to see if current functionality on Bobcat/BSD
  still works and isn't broken.

* Test things that have broken in the past, like doing an upgrade, and
  afterwards the user gets the FTI menu/screen whenever s/he logs in as
  admin user, even though the filer is already configured.

* Do basic smoke and sanity checking with regards to things like
  _system copy config_; _system copy init_; _system upgrade_;
  flash_install (FTI menu/screen comes up and is functional).

If that kind of in-branch testing passes, then we can merge that branch
into dev, and then test the functionality of merge and the full
functionality of FTI on Cougar/Linux.

I'm sure you've already started down this path already, but I just
wanted to make sure that I had expressed everything clearly.  Let me
know if something still needs clarifying.

Cheers,

a
