X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C798B0.E5CE0D3C@onstor-exch02.onstor.net>; Thu, 17 May 2007 11:26:34 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C798B0.E5CE0D3C"
References: <20070517112333.354890f5@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: upgrade fixes in respun 1.3.3.16 patch
Date: Thu, 17 May 2007 11:25:16 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D0E7@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: upgrade fixes in respun 1.3.3.16 patch
Thread-Index: AceYsHsrZnWJEf4tT0S0LGSj6CYy0QAADwm4
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Ed Kwan" <ed.kwan@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C798B0.E5CE0D3C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I thought the plan was to put them into 2.2.3.0 and make that a =
mandatory stepping stone from 1.3.3.x or 2.2.x...notwithstanding the =
single-step upgrade we hope to actually use the most.

-Ken


-----Original Message-----
From: Andy Sharp
Sent: Thu 5/17/2007 11:23 AM
To: Ed Kwan
Cc: Larry Scheer; Ken Renshaw
Subject: upgrade fixes in respun 1.3.3.16 patch
=20
Since we are going to respin the 1.3.3.16 patch, can we please add the
upgrade fixes?  Larry or Ken, can you dig up the changelist #s for
those?  If not I think I can find them.  I know we "aren't planning any
more patches" but then that's the definition of a patch, isn't it?  An
unplanned upgrade.

Thanks,

a


------_=_NextPart_001_01C798B0.E5CE0D3C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: upgrade fixes in respun 1.3.3.16 patch</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I thought the plan was to put them into 2.2.3.0 and =
make that a mandatory stepping stone from 1.3.3.x or =
2.2.x...notwithstanding the single-step upgrade we hope to actually use =
the most.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Thu 5/17/2007 11:23 AM<BR>
To: Ed Kwan<BR>
Cc: Larry Scheer; Ken Renshaw<BR>
Subject: upgrade fixes in respun 1.3.3.16 patch<BR>
<BR>
Since we are going to respin the 1.3.3.16 patch, can we please add =
the<BR>
upgrade fixes?&nbsp; Larry or Ken, can you dig up the changelist #s =
for<BR>
those?&nbsp; If not I think I can find them.&nbsp; I know we =
&quot;aren't planning any<BR>
more patches&quot; but then that's the definition of a patch, isn't =
it?&nbsp; An<BR>
unplanned upgrade.<BR>
<BR>
Thanks,<BR>
<BR>
a<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C798B0.E5CE0D3C--
