X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C79805.5DAF63AE@onstor-exch02.onstor.net>; Wed, 16 May 2007 14:58:41 -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 14:58:41 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03C0BCC6@onstor-exch02.onstor.net>
In-Reply-To: <20070516142420.57ce3b67@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Memo: 1.3.3 upgrade issue
Thread-Index: AceYAJDtWO6hnyamQrCeGT5k8lsXXQABME5Q
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

you should have included paul and ed on this email.

-----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

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.

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.

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.

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.

Thank you,

Andrew Sharp
