X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C3FF.6C2911EB@onstor-exch02.onstor.net>; Wed, 11 Jul 2007 13:07:00 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C3FF.6C2911EB"
References: <20070711135733.12f3728d@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: switching to cougar branch - time line needed
Date: Wed, 11 Jul 2007 13:07:00 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D42C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: switching to cougar branch - time line needed
Thread-Index: AcfD/hqJdY+yHjNUTyqj6lspkzm2EwAAF1k/
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Jay Michlin" <jay.michlin@onstor.com>

This is a multi-part message in MIME format.

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

You bet, anytime y'all are ready. I'll plan on locking Zonda in the =
morning then...Brian, any particular time?

Sequence of events would be:

-Lock Zonda at cutoff time ( I'll check the nightly buildlogs from the =
night before to make sure it's not busted )

-Push to main ( not much time needed, >30 minutes )

-Push to cougar ( Shall I start this merge and get as far as I can =
before soliciting a little dev help in conflict resolution, or would you =
prefer a cougar team member so this? I'm fine either way here )

If, say, we pick 9 or 10 AM to lock zonda and there are not many merge =
conflicts then cougar should be ready by noon or so.

Thanks,

-Ken


-----Original Message-----
From: Andy Sharp
Sent: Wed 7/11/2007 1:57 PM
To: Ken Renshaw
Cc: Larry Scheer; Tim Gardner; Brian DeForest; Jay Michlin
Subject: switching to cougar branch - time line needed
=20
So, we have approvals from all involved to switch from zonda to cougar
branch, we just need a timeline from the person doing the work, which
is Ken.

In order to keep zonda developers locked out of perforce for the
shortest time possible, the merge/integrate from zonda branch to main,
and then main to cougar needs to be done in a timely fashion and at a
specific time.  That would mean, among other things, that Ken is all
set and ready to go.

I'm proposing that starting tomorrow morning, we lock the zonda branch,
label it at that point, do the integrates to main and then to cougar,
and declare cougar open for zonda business.

If we are all agreed, then I will send out the announcement emails to
dl-software after the software eng. meeting so that everyone here and
in India will know what's happening.

Ken, please let me know if you are ready to proceed.  I've been told
that you are but I'd like to hear it directly ~:^)

Thanks everyone!

a


------_=_NextPart_001_01C7C3FF.6C2911EB
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: switching to cougar branch - time line needed</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>You bet, anytime y'all are ready. I'll plan on locking =
Zonda in the morning then...Brian, any particular time?<BR>
<BR>
Sequence of events would be:<BR>
<BR>
-Lock Zonda at cutoff time ( I'll check the nightly buildlogs from the =
night before to make sure it's not busted )<BR>
<BR>
-Push to main ( not much time needed, &gt;30 minutes )<BR>
<BR>
-Push to cougar ( Shall I start this merge and get as far as I can =
before soliciting a little dev help in conflict resolution, or would you =
prefer a cougar team member so this? I'm fine either way here )<BR>
<BR>
If, say, we pick 9 or 10 AM to lock zonda and there are not many merge =
conflicts then cougar should be ready by noon or so.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Wed 7/11/2007 1:57 PM<BR>
To: Ken Renshaw<BR>
Cc: Larry Scheer; Tim Gardner; Brian DeForest; Jay Michlin<BR>
Subject: switching to cougar branch - time line needed<BR>
<BR>
So, we have approvals from all involved to switch from zonda to =
cougar<BR>
branch, we just need a timeline from the person doing the work, =
which<BR>
is Ken.<BR>
<BR>
In order to keep zonda developers locked out of perforce for the<BR>
shortest time possible, the merge/integrate from zonda branch to =
main,<BR>
and then main to cougar needs to be done in a timely fashion and at =
a<BR>
specific time.&nbsp; That would mean, among other things, that Ken is =
all<BR>
set and ready to go.<BR>
<BR>
I'm proposing that starting tomorrow morning, we lock the zonda =
branch,<BR>
label it at that point, do the integrates to main and then to =
cougar,<BR>
and declare cougar open for zonda business.<BR>
<BR>
If we are all agreed, then I will send out the announcement emails =
to<BR>
dl-software after the software eng. meeting so that everyone here =
and<BR>
in India will know what's happening.<BR>
<BR>
Ken, please let me know if you are ready to proceed.&nbsp; I've been =
told<BR>
that you are but I'd like to hear it directly ~:^)<BR>
<BR>
Thanks everyone!<BR>
<BR>
a<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7C3FF.6C2911EB--
