X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B4FF.D0F5A98E@onstor-exch02.onstor.net>; Fri, 22 Jun 2007 11:02:01 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B4FF.D0F5A98E"
References: <6041AEBD8A3E264785ABDA2F60B52DB447554B3D@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E043613BB@onstor-exch02.onstor.net><20070620164405.0e3f0018@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D2F0@onstor-exch02.onstor.net><20070620171052.3aa49eab@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D2F3@onstor-exch02.onstor.net> <20070622113444.152ca56c@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: Building patches: Was: RE: EverON 2.2.2.10 available
Date: Fri, 22 Jun 2007 11:02:01 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D322@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Building patches: Was: RE: EverON 2.2.2.10 available
Thread-Index: Ace0/AHmosaS8+IvSAi/cLFFwnXlBAAAMu3p
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"dl-Customer-Engineering" <dl-Customer-Engineering@onstor.com>,
	"dl-Engineering" <dl-engineering@onstor.com>

This is a multi-part message in MIME format.

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

On building current 2.2.2 and 2.2.3 series EverON patches
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D

NOTE: ONStor process up to this point defines the release manager as =
owner of the release branches, and also the construction of the patches. =
Ongoing discussions are evolving to meet future needs that may change =
this. In the meantime, please bear in mind the processes for patch =
building are tailored to the up-to-now sole user, i.e., me. Due to =
current interest we can start putting things in place to make it easier =
to follow what I've done, such as standardized branching and labeling =
conventions which I would be happy to do.

2.2.3 series:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

R2_2_0_rel was the original branch created off main to support =
Lamborghini project patches. It is a fully self-contained branch, e.g. =
you just checkout the entire branch //depot/R2_2_0_rel/... and build the =
universe as in any ONStor project branch. Perforce client view mapping =
would look something like:

View:
        //depot/R2_2_0_rel/... //yourclient/R2_2_0_rel/...

If you checked out the treetops here you'd be building the current =
shipping 2.2.3.x patch, 2.2.3.0 in this case.

2.2.2 series:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The patch codeline for Lamborghini support diverged with the addition of =
the maintenance release 2.2.3.0 while patches based on 2.2.2.x were =
still being called for. Thus R2_2_2_x_rel was branched off of the parent =
R2_2_0_rel. This branch is assumed to collapse back in during the =
2.2.x.y patch series at some point soon. It is *not* a full branch, but =
only the nfx-tree subsection, so you need a view mapping like this one:

View:
        //depot/FB-LAMBORGHINI/... //kenr-R2_2_2_x_rel/R2_2_2_x_rel/...
        -//depot/FB-LAMBORGHINI/nfx-tree/... =
//kenr-R2_2_2_x_rel/R2_2_2_x_rel/nfx-tree/...
        //depot/R2_2_2_x_rel/nfx-tree/... =
//kenr-R2_2_2_x_rel/R2_2_2_x_rel/nfx-tree/...

This view keeps the 2.2.2.x patches based in FB-LAMBORGHINI, because the =
parent branch R2_2_0_rel/openbsd diverged. You can also of course not =
build the BSD yourself and point to =
/n/Build-Trees/BSD/openbsd-latest-222.

All you need do is setup your client and sync it, then build BSD and =
EverON as usual. The top of the tree is what you should probably use, as =
it's always tested, and at this point represents 2.2.2.10.=20

That's all there is to it. Let me know if you need to know anything =
else, but it's not as hard as some may have thought.

-Ken

-----Original Message-----
From: Andy Sharp
Sent: Fri 6/22/2007 11:34 AM
To: Ken Renshaw
Subject: Re: EverON 2.2.2.10 available
=20
Ping.

a

On Wed, 20 Jun 2007 17:14:14 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> Ja.
>=20
> I'm working on getting zonda going and as soon as I';m done I'll send
> you a HOWTO Andy.
>=20
> Thanks,
>=20
> -Ken
>=20
>=20
> -----Original Message-----
> From: Andy Sharp
> Sent: Wed 6/20/2007 5:10 PM
> To: Ken Renshaw
> Subject: Re: EverON 2.2.2.10 available
> =20
> I'm after the ability to build this release myself.  Any release from
> 2.2.2.7 onwards is probably OK, but since this is the latest one, I
> might as work with this one, ja?
>=20
> On Wed, 20 Jun 2007 17:04:02 -0700 "Ken Renshaw"
> <ken.renshaw@onstor.com> wrote:
>=20
> > Hey Andy, is this for handling some customer issue or something?
> > Just trying to figure out what you're after...
> >=20
> > Thanks,
> >=20
> > -Ken
> >=20
> >=20
> > -----Original Message-----
> > From: Andy Sharp
> > Sent: Wed 6/20/2007 4:44 PM
> > To: Eric Barrett
> > Cc: Ken Renshaw; dl-Customer-Engineering; Ed Kwan; dl-Engineering
> > Subject: Re: EverON 2.2.2.10 available
> > =20
> > Hi Eric,
> >=20
> > I would like to build this release/branch/whatever myself.  Can
> > someone please provide me with complete instructions on how to do
> > that?  You may assume that I know how to build our software.
> >=20
> > Thanks,
> >=20
> > a
> >=20
> > On Wed, 20 Jun 2007 16:30:29 -0700 "Eric Barrett"
> > <eric.barrett@onstor.com> wrote:
> >=20
> > > 2.2.2.10 has been promoted to be publicly visible on ASSIST and
> > > the FTP site.
> > > =20
> > >=20
> > > -----Original Message-----
> > > From: Eric Barrett=20
> > > Sent: Tuesday, June 19, 2007 12:13 PM
> > > To: dl-se; dl-Customer-Engineering; Frontline Support;
> > > dl-Engineering Subject: EverON 2.2.2.10 available
> > >=20
> > > EverON 2.2.2.10 has been posted in the "early" (hidden) section of
> > > the FTP site.
> > >=20
> > > This release is accessible through the following URL:
> > >=20
> > > ftp://ftp.onstor.com/outbound/software/EverON/early/2.2.2.10
> > >=20
> > > The public README file is here:
> > >=20
> > > =
ftp://ftp.onstor.com/outbound/software/EverON/early/2.2.2.10/Documents/R
> > > eadMe-2.2.2.10.txt
> > >=20
> > > --
> > > Eric Barrett - ONStor Support - 1-408-963-2407 - eric@onstor.com
> > >=20
> > > ONStor US Support:
> > > Phone: 1-866-726-3453; email: support@onstor.com
> >=20
>=20




------_=_NextPart_001_01C7B4FF.D0F5A98E
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>Building patches: Was: RE: EverON 2.2.2.10 available</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>On building current 2.2.2 and 2.2.3 series EverON =
patches<BR>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<BR>
<BR>
NOTE: ONStor process up to this point defines the release manager as =
owner of the release branches, and also the construction of the patches. =
Ongoing discussions are evolving to meet future needs that may change =
this. In the meantime, please bear in mind the processes for patch =
building are tailored to the up-to-now sole user, i.e., me. Due to =
current interest we can start putting things in place to make it easier =
to follow what I've done, such as standardized branching and labeling =
conventions which I would be happy to do.<BR>
<BR>
2.2.3 series:<BR>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>
<BR>
R2_2_0_rel was the original branch created off main to support =
Lamborghini project patches. It is a fully self-contained branch, e.g. =
you just checkout the entire branch //depot/R2_2_0_rel/... and build the =
universe as in any ONStor project branch. Perforce client view mapping =
would look something like:<BR>
<BR>
View:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //depot/R2_2_0_rel/... =
//yourclient/R2_2_0_rel/...<BR>
<BR>
If you checked out the treetops here you'd be building the current =
shipping 2.2.3.x patch, 2.2.3.0 in this case.<BR>
<BR>
2.2.2 series:<BR>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>
<BR>
The patch codeline for Lamborghini support diverged with the addition of =
the maintenance release 2.2.3.0 while patches based on 2.2.2.x were =
still being called for. Thus R2_2_2_x_rel was branched off of the parent =
R2_2_0_rel. This branch is assumed to collapse back in during the =
2.2.x.y patch series at some point soon. It is *not* a full branch, but =
only the nfx-tree subsection, so you need a view mapping like this =
one:<BR>
<BR>
View:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //depot/FB-LAMBORGHINI/... =
//kenr-R2_2_2_x_rel/R2_2_2_x_rel/...<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-//depot/FB-LAMBORGHINI/nfx-tree/... =
//kenr-R2_2_2_x_rel/R2_2_2_x_rel/nfx-tree/...<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
//depot/R2_2_2_x_rel/nfx-tree/... =
//kenr-R2_2_2_x_rel/R2_2_2_x_rel/nfx-tree/...<BR>
<BR>
This view keeps the 2.2.2.x patches based in FB-LAMBORGHINI, because the =
parent branch R2_2_0_rel/openbsd diverged. You can also of course not =
build the BSD yourself and point to =
/n/Build-Trees/BSD/openbsd-latest-222.<BR>
<BR>
All you need do is setup your client and sync it, then build BSD and =
EverON as usual. The top of the tree is what you should probably use, as =
it's always tested, and at this point represents 2.2.2.10.<BR>
<BR>
That's all there is to it. Let me know if you need to know anything =
else, but it's not as hard as some may have thought.<BR>
<BR>
-Ken<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Fri 6/22/2007 11:34 AM<BR>
To: Ken Renshaw<BR>
Subject: Re: EverON 2.2.2.10 available<BR>
<BR>
Ping.<BR>
<BR>
a<BR>
<BR>
On Wed, 20 Jun 2007 17:14:14 -0700 &quot;Ken Renshaw&quot;<BR>
&lt;ken.renshaw@onstor.com&gt; wrote:<BR>
<BR>
&gt; Ja.<BR>
&gt;<BR>
&gt; I'm working on getting zonda going and as soon as I';m done I'll =
send<BR>
&gt; you a HOWTO Andy.<BR>
&gt;<BR>
&gt; Thanks,<BR>
&gt;<BR>
&gt; -Ken<BR>
&gt;<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: Andy Sharp<BR>
&gt; Sent: Wed 6/20/2007 5:10 PM<BR>
&gt; To: Ken Renshaw<BR>
&gt; Subject: Re: EverON 2.2.2.10 available<BR>
&gt;&nbsp;<BR>
&gt; I'm after the ability to build this release myself.&nbsp; Any =
release from<BR>
&gt; 2.2.2.7 onwards is probably OK, but since this is the latest one, =
I<BR>
&gt; might as work with this one, ja?<BR>
&gt;<BR>
&gt; On Wed, 20 Jun 2007 17:04:02 -0700 &quot;Ken Renshaw&quot;<BR>
&gt; &lt;ken.renshaw@onstor.com&gt; wrote:<BR>
&gt;<BR>
&gt; &gt; Hey Andy, is this for handling some customer issue or =
something?<BR>
&gt; &gt; Just trying to figure out what you're after...<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks,<BR>
&gt; &gt;<BR>
&gt; &gt; -Ken<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; -----Original Message-----<BR>
&gt; &gt; From: Andy Sharp<BR>
&gt; &gt; Sent: Wed 6/20/2007 4:44 PM<BR>
&gt; &gt; To: Eric Barrett<BR>
&gt; &gt; Cc: Ken Renshaw; dl-Customer-Engineering; Ed Kwan; =
dl-Engineering<BR>
&gt; &gt; Subject: Re: EverON 2.2.2.10 available<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; Hi Eric,<BR>
&gt; &gt;<BR>
&gt; &gt; I would like to build this release/branch/whatever =
myself.&nbsp; Can<BR>
&gt; &gt; someone please provide me with complete instructions on how to =
do<BR>
&gt; &gt; that?&nbsp; You may assume that I know how to build our =
software.<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks,<BR>
&gt; &gt;<BR>
&gt; &gt; a<BR>
&gt; &gt;<BR>
&gt; &gt; On Wed, 20 Jun 2007 16:30:29 -0700 &quot;Eric =
Barrett&quot;<BR>
&gt; &gt; &lt;eric.barrett@onstor.com&gt; wrote:<BR>
&gt; &gt;<BR>
&gt; &gt; &gt; 2.2.2.10 has been promoted to be publicly visible on =
ASSIST and<BR>
&gt; &gt; &gt; the FTP site.<BR>
&gt; &gt; &gt;&nbsp;<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; -----Original Message-----<BR>
&gt; &gt; &gt; From: Eric Barrett<BR>
&gt; &gt; &gt; Sent: Tuesday, June 19, 2007 12:13 PM<BR>
&gt; &gt; &gt; To: dl-se; dl-Customer-Engineering; Frontline =
Support;<BR>
&gt; &gt; &gt; dl-Engineering Subject: EverON 2.2.2.10 available<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; EverON 2.2.2.10 has been posted in the &quot;early&quot; =
(hidden) section of<BR>
&gt; &gt; &gt; the FTP site.<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; This release is accessible through the following URL:<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; <A =
HREF=3D"ftp://ftp.onstor.com/outbound/software/EverON/early/2.2.2.10">ftp=
://ftp.onstor.com/outbound/software/EverON/early/2.2.2.10</A><BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; The public README file is here:<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; <A =
HREF=3D"ftp://ftp.onstor.com/outbound/software/EverON/early/2.2.2.10/Docu=
ments/R">ftp://ftp.onstor.com/outbound/software/EverON/early/2.2.2.10/Doc=
uments/R</A><BR>
&gt; &gt; &gt; eadMe-2.2.2.10.txt<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; --<BR>
&gt; &gt; &gt; Eric Barrett - ONStor Support - 1-408-963-2407 - =
eric@onstor.com<BR>
&gt; &gt; &gt;<BR>
&gt; &gt; &gt; ONStor US Support:<BR>
&gt; &gt; &gt; Phone: 1-866-726-3453; email: support@onstor.com<BR>
&gt; &gt;<BR>
&gt;<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B4FF.D0F5A98E--
