AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080327171729.6c98cd20@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>,<tim.gardner@onstor.com>,<sripal.surendiran@onstor.com>,<manohar.divate@onstor.com>,<vikas.saini@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 27 Mar 2008 17:18:06 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Sandrine Boulanger <sandrine.boulanger@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>
Subject: Desired goal of in-branch testing of FTI/migration
Message-ID: <20080327171806.7ee80a6a@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

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
