X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C510.B4E4D2A1@onstor-exch02.onstor.net>; Thu, 12 Jul 2007 21:43:14 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C510.B4E4D2A1"
Content-class: urn:content-classes:message
Subject: RE: Cougar branch has just been updated with the Zonda code
Date: Thu, 12 Jul 2007 21:40:16 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03E56A49@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar branch has just been updated with the Zonda code
Thread-Index: AcfE1MqEjcOullSlRMO8IwuvvvKMJQAO4A4x
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D440@onstor-exch02.onstor.net>
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"dl-Engineering" <dl-engineering@onstor.com>

This is a multi-part message in MIME format.

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

Thanks Ken, good stuff.
=20
Very minor change, the Zonda QA team will report any issue they see to =
Brian D (or more accurately to CQ), the Zonda QA test folks do not know =
anything about this thing you call Cougar, thus can't make the call if =
it is a Zonda or Cougar branching issue.=20
=20
-Paul
=20

________________________________

From: Ken Renshaw
Sent: Thu 7/12/2007 8:50 PM
To: dl-Engineering
Subject: Cougar branch has just been updated with the Zonda code



I've just finished merging, building, testing, and checking in the merge =
of Zonda and Cougar for all Zonda targets, i.e. OpenBSD-based cheetah =
and bobcat debug and opt builds. I have built submittal 3 for Zonda out =
of this merge space, it has passed build verification testing, and will =
be handed off to QA for Acceptance Testing a little later this evening. =
The Cougar branch is now unlocked as well.

I have built and posted the top-of-tree BSD build here:

/n/Build-Trees/BSD/openbsd-071207-310

Which is what this:

/n/Build-Trees/BSD/openbsd-latest-310

points to for convenience. If you just set your /usr/openbsd.new symlink =
to point to the second path above you'll automatically keep in sync with =
any new builds that come out. For those that build and maintain there =
own BSD images, nevermind...

For Zonda, builds and installs all have been verified to perform without =
change, so you shouldn't see any problems, but please let me or a Cougar =
team member know ASAP if you hit one. I am using the current build I =
have for submittal 3 of Zonda and will be handing it off for Acceptance =
Testing later this evening. The cheetah debug and opt builds have been =
loaded up on my cluster and are running stress tests without issue so =
far.

The Cougar branch is now in an integration phase, after which we will =
collapse the Cougar branch and create the dev branch where we will be =
working from now on. At the point we create the dev branch, all Zonda =
developers will be responsible for not breaking any of the Cougar make =
targets ( and vice versa ). Until that time is reached, Zonda developers =
are simply responsible for making sure that their code compiles for =
cheetah/bobcat, opt/dbg as usual.

If there are any questions or problems please let me and the Cougar dev =
team know ASAP.

Thanks,

-Ken






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

<HTML dir=3Dltr><HEAD><TITLE>Cougar branch has just been updated with =
the Zonda code</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText78193 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Thanks Ken, =
good stuff.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Very minor =
change, the Zonda QA&nbsp;team will report any issue they see to Brian D =
(or more accurately to CQ), the Zonda QA test folks do not know anything =
about this thing you call Cougar, thus can't make the call if it is a =
Zonda or Cougar branching issue. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Paul</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Ken Renshaw<BR><B>Sent:</B> =
Thu 7/12/2007 8:50 PM<BR><B>To:</B> dl-Engineering<BR><B>Subject:</B> =
Cougar branch has just been updated with the Zonda =
code<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I've just finished merging, building, testing, and =
checking in the merge of Zonda and Cougar for all Zonda targets, i.e. =
OpenBSD-based cheetah and bobcat debug and opt builds. I have built =
submittal 3 for Zonda out of this merge space, it has passed build =
verification testing, and will be handed off to QA for Acceptance =
Testing a little later this evening. The Cougar branch is now unlocked =
as well.<BR><BR>I have built and posted the top-of-tree BSD build =
here:<BR><BR>/n/Build-Trees/BSD/openbsd-071207-310<BR><BR>Which is what =
this:<BR><BR>/n/Build-Trees/BSD/openbsd-latest-310<BR><BR>points to for =
convenience. If you just set your /usr/openbsd.new symlink to point to =
the second path above you'll automatically keep in sync with any new =
builds that come out. For those that build and maintain there own BSD =
images, nevermind...<BR><BR>For Zonda, builds and installs all have been =
verified to perform without change, so you shouldn't see any problems, =
but please let me or a Cougar team member know ASAP if you hit one. I am =
using the current build I have for submittal 3 of Zonda and will be =
handing it off for Acceptance Testing later this evening. The cheetah =
debug and opt builds have been loaded up on my cluster and are running =
stress tests without issue so far.<BR><BR>The Cougar branch is now in an =
integration phase, after which we will collapse the Cougar branch and =
create the dev branch where we will be working from now on. At the point =
we create the dev branch, all Zonda developers will be responsible for =
not breaking any of the Cougar make targets ( and vice versa ). Until =
that time is reached, Zonda developers are simply responsible for making =
sure that their code compiles for cheetah/bobcat, opt/dbg as =
usual.<BR><BR>If there are any questions or problems please let me and =
the Cougar dev team know =
ASAP.<BR><BR>Thanks,<BR><BR>-Ken<BR><BR><BR><BR></FONT></P></DIV></BODY><=
/HTML>
------_=_NextPart_001_01C7C510.B4E4D2A1--
