X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7D533.F4FE59B0@onstor-exch02.onstor.net>; Thu, 2 Aug 2007 10:35:53 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D533.F4FE59B0"
References: <BB375AF679D4A34E9CA8DFA650E2B04E04D20994@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E02F3D5B1@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E04D20A5F@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Branch for 3.0.1  (RE: Please respin patch 3.0.0.4)
Date: Thu, 2 Aug 2007 10:33:43 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D5B4@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Branch for 3.0.1  (RE: Please respin patch 3.0.0.4)
Thread-Index: AcfVKBq9oqPloUSgQySFqgTcQuEKbAACDIdwAACu/bAAACepdA==
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Ed Kwan" <ed.kwan@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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

Great, you know I prefer to branch early than disentangle things as we =
get further along.=20

The current branch R3_0_X_rel we will continue to use for the 3.0.0.x =
patch procession, and I'll create another one for 3.0.1.x as soon as I'm =
done rebuilding 3.0.0.4 for you. Shall I automatically assume I'm to =
roll forward all 3.0.0.x patches into the 3.0.1.x submittals?

Thanks,

-Ken


-----Original Message-----
From: Ed Kwan
Sent: Thu 8/2/2007 11:32 AM
To: Ken Renshaw
Cc: Andy Sharp
Subject: Branch for 3.0.1  (RE: Please respin patch 3.0.0.4)
=20
Yes, it will be good to have a separate 3.0.1.0 branch.  Andy & I were =
talking about it yesterday afternoon; he is planning to improve the =
installation code/script for 3.0.1.0.

> So like for 22x, we'll either need to create a 301 or 300 branch if we
> think there will be many patches in the time it takes to get 301 out.



------_=_NextPart_001_01C7D533.F4FE59B0
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: Branch for 3.0.1  (RE: Please respin patch 3.0.0.4)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Great, you know I prefer to branch early than =
disentangle things as we get further along.<BR>
<BR>
The current branch R3_0_X_rel we will continue to use for the 3.0.0.x =
patch procession, and I'll create another one for 3.0.1.x as soon as I'm =
done rebuilding 3.0.0.4 for you. Shall I automatically assume I'm to =
roll forward all 3.0.0.x patches into the 3.0.1.x submittals?<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ed Kwan<BR>
Sent: Thu 8/2/2007 11:32 AM<BR>
To: Ken Renshaw<BR>
Cc: Andy Sharp<BR>
Subject: Branch for 3.0.1&nbsp; (RE: Please respin patch 3.0.0.4)<BR>
<BR>
Yes, it will be good to have a separate 3.0.1.0 branch.&nbsp; Andy &amp; =
I were talking about it yesterday afternoon; he is planning to improve =
the installation code/script for 3.0.1.0.<BR>
<BR>
&gt; So like for 22x, we'll either need to create a 301 or 300 branch if =
we<BR>
&gt; think there will be many patches in the time it takes to get 301 =
out.<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7D533.F4FE59B0--
