AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070406111422.116d1797@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<jerry.lopatin@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E01440354@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 6 Apr 2007 11:15:23 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Jerry Lopatin" <jerry.lopatin@onstor.com>
Subject: Re: Change lists for 2.2.X maintenance (?patch?) release.
Message-ID: <20070406111523.3c1f5c63@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E01440354@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E01440354@onstor-exch02.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

Simply because the engineers working on it are otherwise working on
Cougar, and the distraction factor alone is causing perennial slippage
on the delivery end of the schedule.  The engineer(s) doing the work
would otherwise be settling into a rhythm working on their cougar tasks.

Jay has said that he has made his decision on this and I have to go
with that.  The one thing I don't understand is how this solution is a
better experience for the customer than sending out new flash cards
with Delorean installed on them.  A single reboot v. two upgrades?  Oh
well, I guess I don't have to understand everything.

a


On Fri, 6 Apr 2007 00:08:01 -0700 "Jerry Lopatin"
<jerry.lopatin@onstor.com> wrote:

> Andy,
> 
> Can hoe help explain how this conflicts with the.  Cougar direction?
> 
> Jerry
> --------------------------
> Sent from my Blackberry; please excuse my typing! 
> 
> -----Original Message-----
> From: Paul Hammer
> To: Jerry Lopatin
> Sent: Thu Apr 05 19:42:26 2007
> Subject: FW: Change lists for 2.2.X maintenance (?patch?) release.
> 
> 
> Fwding.
>  
> 
> -----Original Message-----
> From: Andy Sharp
> To: Ed Kwan
> CC: Larry Scheer; Jay Michlin; Sandrine Boulanger; Ken Renshaw; Tim
> Gardner; Caeli Collins Sent: Thu Apr 05 13:56:51 2007
> Subject: Re: Change lists for 2.2.X maintenance (?patch?) release.
> 
> Besides the fact that this whole direction is a slap to the Cougar
> project, IMHO, and therefore folly, this might be the opportune time
> to dovetail the 1.3.3 customers to 2.2 code line.
> 
> If the original plan to merge the Lambo upgrade code into 1.3.3 line
> had ever been executed on, I might disagree.  But the fact is that
> 1.3.3 still is burdened with the prone-to-file-corruption upgrade
> process, and the sooner we get customers off of that, the better.
> Better one upgrade step to do that than two.  More like 1.5, since if
> file corruption is found, and it often is, they will have to upgrade
> twice.
> 
> a
> 
> On Thu, 5 Apr 2007 13:36:44 -0700 "Ed Kwan" <ed.kwan@onstor.com>
> wrote:
> 
> > What about customers upgrading from 1.3.3.x or earlier?  
> > 
> > _____________________________________________
> > From: Larry Scheer 
> > Sent: Thursday, April 05, 2007 1:11 PM
> > To: Ken Renshaw; Tim Gardner; Ed Kwan
> > Cc: Jay Michlin; Andy Sharp
> > Subject: Change lists for 2.2.X maintenance (?patch?) release.
> > 
> > Ken, Ed,
> >     The following change lists will give you the files to back-port
> > the Upgrade and compact flash repartitioning features that are in
> > Delorean. These changes are needed to give customers the ability to
> > upgrade to Delorean and get the new compact flash layout.
> > 
> > Change 23306 - Files that implement new compact flash layout and
> > support upgrade with the layout.
> > Change 23359 - Fixes to verify_install.sh
> > Change 23362 - Changes to cmd_upgrade to run verify_install.sh from
> > distribution
> > Change 23363 - Fix to quiet chatty system copy commands
> > 
> > After this release is built we will need to rev the top level
> > Makefile in the 2.2. Release tree to produce BOM files that are the
> > new format, but not now. We only want to do this when this release
> > is in the field.
> > 
> > If you have any more questions don't hesitate to ask.
> > 
> > Larry.
> > 
> > P.S. I need to leave will be back around 4 PM.
