X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AF01.C4252A57@onstor-exch02.onstor.net>; Thu, 14 Jun 2007 20:00:52 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AF01.C4252A57"
Content-class: urn:content-classes:message
Subject: Perforce branches FB-DELOREAN, support, and cougar unlocked and ready for business.
Date: Thu, 14 Jun 2007 20:00:52 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D297@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Perforce branches FB-DELOREAN, support, and cougar unlocked and ready for business.
Thread-Index: AcevAcQlVDaBJo/wSG6ezswVMKgdhw==
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "dl-Engineering" <dl-engineering@onstor.com>

This is a multi-part message in MIME format.

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

The aforementioned branches have been unlocked and are ready for use. =
The FB-DELOREAN branch has the same ACL as Brian had specified before =
the upgrade and you still are required to get his approval before =
checking anything into the project branch.

In the case of FB-DELOREAN and support, I have manually entered the last =
few changes in so the top-of-tree should be what you expect. I created =
new changelists and entered the original descriptions so there shouldn't =
be any problems tracing things. WRT cougar, the branch is as it was =
before the crash, and does not include the corrupted main->cougar merge =
Larry worked so hard on. Once branching decisions are reached we will =
proceed in the proper order.

There should not be any issues building or using these branches, please =
do let me know ASAP if there are....like you wouldn't :)

I have test-built DeLorean and diffed it with the 061207 build and there =
are no differences, as a bit of security blanket that the tree has been =
rebuilt in good shape. Likewise the Perforce pre-commit triggers are in =
place, but I need to do some mail configuration on the new server before =
automated Perforce emails are sent out, but rest assured when it's =
working you'll get the entire delta.

I still have more work to do with ZONDA, R2_2_0_rel, R2_2_2_x_rel, and =
FB-NOSAMBA, and will keep you posted on the progress there.

One other thing, we are running the 2007.2 latest release of Perforce so =
if you haven't upgraded you4 p4 and p4v binaries in a while you might =
want to do so to be able to use any new features and to take advantage =
of all the bug fixes. You can get the appropriate binary here:

http://www.perforce.com/perforce/loadprog.html

For an exhaustive and exhausting list of all the new features, you can =
read the release notes for 2007.2 here:

http://www.perforce.com/perforce/doc.072/user/relnotes.txt

Everyhing after 2002.1 is applicable, roughly the first tow-thirds of =
the release note.=20

Thanks,

-Ken

------_=_NextPart_001_01C7AF01.C4252A57
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>Perforce branches FB-DELOREAN, support, and cougar unlocked and =
ready for business.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>The aforementioned branches have been unlocked and are =
ready for use. The FB-DELOREAN branch has the same ACL as Brian had =
specified before the upgrade and you still are required to get his =
approval before checking anything into the project branch.<BR>
<BR>
In the case of FB-DELOREAN and support, I have manually entered the last =
few changes in so the top-of-tree should be what you expect. I created =
new changelists and entered the original descriptions so there shouldn't =
be any problems tracing things. WRT cougar, the branch is as it was =
before the crash, and does not include the corrupted main-&gt;cougar =
merge Larry worked so hard on. Once branching decisions are reached we =
will proceed in the proper order.<BR>
<BR>
There should not be any issues building or using these branches, please =
do let me know ASAP if there are....like you wouldn't :)<BR>
<BR>
I have test-built DeLorean and diffed it with the 061207 build and there =
are no differences, as a bit of security blanket that the tree has been =
rebuilt in good shape. Likewise the Perforce pre-commit triggers are in =
place, but I need to do some mail configuration on the new server before =
automated Perforce emails are sent out, but rest assured when it's =
working you'll get the entire delta.<BR>
<BR>
I still have more work to do with ZONDA, R2_2_0_rel, R2_2_2_x_rel, and =
FB-NOSAMBA, and will keep you posted on the progress there.<BR>
<BR>
One other thing, we are running the 2007.2 latest release of Perforce so =
if you haven't upgraded you4 p4 and p4v binaries in a while you might =
want to do so to be able to use any new features and to take advantage =
of all the bug fixes. You can get the appropriate binary here:<BR>
<BR>
<A =
HREF=3D"http://www.perforce.com/perforce/loadprog.html">http://www.perfor=
ce.com/perforce/loadprog.html</A><BR>
<BR>
For an exhaustive and exhausting list of all the new features, you can =
read the release notes for 2007.2 here:<BR>
<BR>
<A =
HREF=3D"http://www.perforce.com/perforce/doc.072/user/relnotes.txt">http:=
//www.perforce.com/perforce/doc.072/user/relnotes.txt</A><BR>
<BR>
Everyhing after 2002.1 is applicable, roughly the first tow-thirds of =
the release note.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7AF01.C4252A57--
