X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7981A.E90BCB3A@onstor-exch02.onstor.net>; Wed, 16 May 2007 17:32:54 -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: Memo: 1.3.3 upgrade issue
Date: Wed, 16 May 2007 17:32:54 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03C0BDF0@onstor-exch02.onstor.net>
In-Reply-To: <20070516171853.52c1a581@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Memo: 1.3.3 upgrade issue
Thread-Index: AceYGPOFPgeOMM6nT0ac4Gp9j3N3DgAAbtWg
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Jay Michlin" <jay.michlin@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Jerry Lopatin" <jerry.lopatin@onstor.com>,
	"Caeli Collins" <caeli.collins@onstor.com>,
	"Ed Kwan" <ed.kwan@onstor.com>

Andy, both things you heard were right.  We have a lot of people still
on it, but I think very few will upgrade to any *subsequent* 1.3.3
patches.  We strongly steer anybody doing an upgrade right now to
2.2.2.X.

If the effort is really that minimal, then sure, let's do it.  The
changes are inherently good.  Like I said, I'm not the one to make that
call, because I don't have a good sense of the scope of the work
required.


-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, May 16, 2007 5:19 PM
To: Eric Barrett
Cc: Jay Michlin; Paul Hammer; Tim Gardner; Jerry Lopatin; Caeli Collins;
Ed Kwan
Subject: Re: Memo: 1.3.3 upgrade issue

I'm not advocating a release just for this, only that these changes be
put in, in the highly unlikely event that there is another.  BTW, I
don't know why this wasn't done originally, but perhaps there was an
argument not to do it back then and it sounded a lot like this one?
We're now up to 1.3.3.16.  It can't hurt.  Not putting those changes in
back then is causing us a lot of pain now.

I get conflicting information on 1.3.3.  Some say "...a few hardcore
customers..." while others say we have a bunch of customers still on it.

At the risk of repeating myself, I don't know of any good reason not to
do it.  It's really very little work.  The exact perforce CL#s were
identified back in February.

Thanks,

a

On Wed, 16 May 2007 16:43:32 -0700 "Eric Barrett"
<eric.barrett@onstor.com> wrote:

> I'd like to add that any field upgrade with 1.3.3's "system upgrade
> -s" has "system compare -s" run manually after it.   This is
> documented in the upgrade guide and the release notes, and is known
> by everybody in Support, both front- and backline.  If the "system
> compare" fails, the upgrade is attempted a second time, and if that
> fails, we usually go to some extreme measure like shipping a flash
> card we've burned manually.
>=20
> We're pretty much done with 1.3.3.X except a few hardcore customers
> who refuse to move to 2.2 or have very very slow upgrade cycles (such
> as Time Inc.).  Those who are on it are on it and probably won't move
> to a new patch release.  At this stage of the game, the effort
> required to backport the fixes, even if moderate, may not outweigh
> the cost.  I'm not the one to make that call, of course, but if I
> were, I don't think I'd bother.
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Jay Michlin=20
> Sent: Wednesday, May 16, 2007 4:17 PM
> To: Paul Hammer
> Cc: Eric Barrett; Andy Sharp; Tim Gardner; Jerry Lopatin; Caeli
> Collins Subject: FW: Memo: 1.3.3 upgrade issue
>=20
> Paul,
>=20
> We did indeed decide that these fixes to upgrade would go into 1.3.3
> in addition to Lambo. They cured stop-ship-class install file
> corruptions. I asked Eric about this a couple of weeks ago, and he
> was aware that the fixes did not go into 1.3.3. He also recalled that
> we committed to them there, specifically at CS request. He didn't
> know why the fixes never went in, and I don't either.
>=20
> I think we need to do two things:
>=20
> 1. Get these fixes into 1.3.3.x and into the field.
>=20
> 2. Develop a process for following up and auditing items committed for
> patches. Right now I'm specifically concerned about the "upgrade to
> new flash format" we had planned for a "2.2.3" release. The Delorean
> core team requested this, and if that decision is to be reversed, it
> ought to require some process and discussion among those affected.
>=20
> jay
>=20
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, May 16, 2007 2:24 PM
> To: Jay Michlin
> Cc: Jerry Lopatin; Tim Gardner; Caeli Collins
> Subject: Memo: 1.3.3 upgrade issue
>=20
> It's come to my attention that the upgrade fixes have never been
> integrated into the 1.3.3 branch, but that we continue to release
> "patches" or point-point releases from that branch.
>=20
> I want to make it clear that there can be no good reason not to
> integrate these fixes.  The risk of file corruption when running the
> upgrade code in that branch is near 100%.  Even in the absence of
> exacerbating factors, like low memory condition,  the risk is still
> very high.  There's no reason to be taking this risk with our
> customers or our support resources.  The support implications of this
> problem are legion: random failures in any part of the system, often
> without any kind of telltale symptom.  I believe it's extremely
> likely we are taking a large support hit because of this, possibly
> without even knowing it.
>=20
> Three months ago Development, Support and QA met and decided that
> these fixes were going into 1.3.3.10, but it didn't happen for some
> reason. Therefore I don't think we need to gather a core team meeting
> or anything, we just need to cut the red tape.
>=20
> I don't know enough about the internal processes of this company to
> know who, but I strongly suggest that the right person(s) be directed
> to integrate those fixes into the 1.3.3 line.  It certainly won't
> hurt, and it might help a lot.
>=20
> Thank you,
>=20
> Andrew Sharp
