X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7D2DF.A16EE5CA@onstor-exch02.onstor.net>; Mon, 30 Jul 2007 11:27:13 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D2DF.A16EE5CA"
Content-class: urn:content-classes:message
Subject: New dev branch open and ready for business - Was: RE: Monday 9 AM - Cougar branch locked and EOL and creation of Dev branch
Date: Mon, 30 Jul 2007 11:24:14 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D590@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New dev branch open and ready for business - Was: RE: Monday 9 AM - Cougar branch locked and EOL and creation of Dev branch
Thread-Index: AcfPFx14vA10to4YS8Ops/NZW12RzgDuPxDKAAPHVG8=
X-Priority: 1
Priority: Urgent
Importance: high
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D545@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E02F3D582@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@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_01C7D2DF.A16EE5CA
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Okay, we're all set. The spec to use is:

//depot/dev/...

I am currently building the universe our of this branch and will post =
the BSD tree for zonda developers to code against. Going forward once we =
start using linux developers will be responsible for building their own =
OS, but I will keep copies of shipping releases and probably submittal =
builds for cougar as well, once the project ramps up outside of core dev =
naturally.

Please let me know if you see any issues with the new dev branch.

Thanks,

-Ken


-----Original Message-----
From: Ken Renshaw
Sent: Mon 7/30/2007 10:36 AM
To: Ken Renshaw; dl-Engineering
Subject: RE: Monday 9 AM - Cougar branch locked and EOL and creation of =
Dev branch
=20
Good morning. The cougar branch is locked for good and I'm pushing the =
code into main and creating the dev branch. The new branch should be =
opened for business before noon. I'll send out one last email once the =
new branch is available.

Thanks,

-Ken


-----Original Message-----
From: Ken Renshaw
Sent: Wed 7/25/2007 4:54 PM
To: dl-Engineering
Subject: Monday 9 AM - Cougar branch locked and EOL and creation of Dev =
branch
=20
Good afternoon all.

This coming Monday at 9 AM I am going to lock the cougar branch, sync it =
to main and then branch the final dev branch that we hope to play in for =
a long while. In preparation for this, please have all your intended =
work checked in before you leave Friday, or alternatively over the =
weekend but before Monday morning. At 9 AM sharp I am going to lock =
//depot/cougar/... and any opened changelists will have to be imported =
into the new branch manually.

I will be checking the buildlogs so please don't break the build over =
the weekend...you will be hunted down if so ;)

Thanks, and I'll send out a reminder after lunch on Friday reminding =
everyone of this.

-Ken



------_=_NextPart_001_01C7D2DF.A16EE5CA
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>New dev branch open and ready for business - Was: RE: Monday 9 AM =
- Cougar branch locked and EOL and creation of Dev branch</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Okay, we're all set. The spec to use is:<BR>
<BR>
//depot/dev/...<BR>
<BR>
I am currently building the universe our of this branch and will post =
the BSD tree for zonda developers to code against. Going forward once we =
start using linux developers will be responsible for building their own =
OS, but I will keep copies of shipping releases and probably submittal =
builds for cougar as well, once the project ramps up outside of core dev =
naturally.<BR>
<BR>
Please let me know if you see any issues with the new dev branch.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Mon 7/30/2007 10:36 AM<BR>
To: Ken Renshaw; dl-Engineering<BR>
Subject: RE: Monday 9 AM - Cougar branch locked and EOL and creation of =
Dev branch<BR>
<BR>
Good morning. The cougar branch is locked for good and I'm pushing the =
code into main and creating the dev branch. The new branch should be =
opened for business before noon. I'll send out one last email once the =
new branch is available.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Wed 7/25/2007 4:54 PM<BR>
To: dl-Engineering<BR>
Subject: Monday 9 AM - Cougar branch locked and EOL and creation of Dev =
branch<BR>
<BR>
Good afternoon all.<BR>
<BR>
This coming Monday at 9 AM I am going to lock the cougar branch, sync it =
to main and then branch the final dev branch that we hope to play in for =
a long while. In preparation for this, please have all your intended =
work checked in before you leave Friday, or alternatively over the =
weekend but before Monday morning. At 9 AM sharp I am going to lock =
//depot/cougar/... and any opened changelists will have to be imported =
into the new branch manually.<BR>
<BR>
I will be checking the buildlogs so please don't break the build over =
the weekend...you will be hunted down if so ;)<BR>
<BR>
Thanks, and I'll send out a reminder after lunch on Friday reminding =
everyone of this.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7D2DF.A16EE5CA--
