X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7CF16.8BB3B9A7@onstor-exch02.onstor.net>; Wed, 25 Jul 2007 15:50:14 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CF16.8BB3B9A7"
References: <BB375AF679D4A34E9CA8DFA650E2B04E02215912@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E04AFA3A0@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E04AFA3B0@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Time table for new dev branch
Date: Wed, 25 Jul 2007 15:48:49 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D544@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Time table for new dev branch
Thread-Index: AcfPEKd4w2tcJuVZTmK0g1efsK7i1wAABrmbAABUh7AAAGHtoAAAHewQAACRUGA=
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Charissa Willard" <charissa.willard@onstor.com>
Cc: "Jay Michlin" <jay.michlin@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>

This is a multi-part message in MIME format.

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

What would y'all like the new branch called, dev, Dev, DEV, =
delta-epsilon-??

It makes no never-mind to me, I just thought I'd asked.

Thanks,

-Ken


-----Original Message-----
From: Charissa Willard
Sent: Wed 7/25/2007 4:36 PM
To: Ken Renshaw
Cc: Jay Michlin; Andy Sharp; Tim Gardner; Larry Scheer; Brian DeForest
Subject: RE: Time table for new dev branch
=20
So Ken, can you send your usual email out to alert engineers to the fact =
that the branch will be locked on Monday so you can build the dev =
branch?

=20

-Charissa

=20

-----Original Message-----
From: Tim Gardner=20
Sent: Wednesday, July 25, 2007 4:29 PM
To: Larry Scheer; Ken Renshaw; Charissa Willard; Andy Sharp; Jay Michlin
Subject: RE: Time table for new dev branch

=20

Sounds good to me.

=20

-----Original Message-----

From: Larry Scheer=20

Sent: Wednesday, July 25, 2007 4:29 PM

To: Ken Renshaw; Charissa Willard; Tim Gardner; Andy Sharp; Jay Michlin

Subject: RE: Time table for new dev branch

=20

I am thinking it may be best to target the switch to the development =
branch and locking the cougar branch on Monday. This *should* give ample =
time for developers including HCL to get any outstanding code reviewed =
and submitted. This also leaves the weekend clear in case something goes =
wrong.

=20

Charissa was looking over my shoulder just now and agreed with this =
time-table.

=20

Larry

=20

-----Original Message-----

From: Ken Renshaw=20

Sent: Wednesday, July 25, 2007 4:09 PM

To: Larry Scheer

Cc: Charissa Willard; Tim Gardner; Andy Sharp; Jay Michlin

Subject: RE: Time table for new dev branch

=20

Thanks for all the info Larry, I *was* in a wait loop to hear back on =
this as matter of fact.

=20

Since there is no merging to be done, simply moving cougar->main->dev, I =
don't need much time at all to get this done. I can do it tonight, first =
thing in the morning ( say 9 AM lock time ), or any other time of your =
choosing. Just let me know your team's preference.

=20

Thanks,

=20

-Ken

=20

=20

-----Original Message-----

From: Larry Scheer

Sent: Wed 7/25/2007 4:08 PM

To: Ken Renshaw

Cc: Charissa Willard; Tim Gardner; Andy Sharp; Jay Michlin

Subject: Time table for new dev branch

=20

Hi Ken,

    Everyone in software development is awaiting the arrival of the =
official development branch. If you were waiting for the "official" word =
to get started on creating the development branch let this email serve =
as that notice.=20

=20

In case you didn't get the word Charissa has taken the reins from Brian =
De Forest as the Zonda project leader. Charissa, along with Tim, Andy =
and I want to see a smooth and expedient transition to the new branch.=20

=20

The developers need a time table for when to get their outstanding =
changes checked in to the cougar branch. HCL will also need to have =
adequate notice.

=20

Will you please provide engineering with a schedule and appropriate =
notice when the cougar branch will be locked and integrations to main =
and the new branch will occur and any other detail that would be =
helpful?=20

=20

If you need anything from me please ask.

=20

Thanks,

=20

Larry

=20

=20



------_=_NextPart_001_01C7CF16.8BB3B9A7
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: Time table for new dev branch</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>What would y'all like the new branch called, dev, Dev, =
DEV, delta-epsilon-??<BR>
<BR>
It makes no never-mind to me, I just thought I'd asked.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Charissa Willard<BR>
Sent: Wed 7/25/2007 4:36 PM<BR>
To: Ken Renshaw<BR>
Cc: Jay Michlin; Andy Sharp; Tim Gardner; Larry Scheer; Brian =
DeForest<BR>
Subject: RE: Time table for new dev branch<BR>
<BR>
So Ken, can you send your usual email out to alert engineers to the fact =
that the branch will be locked on Monday so you can build the dev =
branch?<BR>
<BR>
<BR>
<BR>
-Charissa<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Tim Gardner<BR>
Sent: Wednesday, July 25, 2007 4:29 PM<BR>
To: Larry Scheer; Ken Renshaw; Charissa Willard; Andy Sharp; Jay =
Michlin<BR>
Subject: RE: Time table for new dev branch<BR>
<BR>
<BR>
<BR>
Sounds good to me.<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
<BR>
From: Larry Scheer<BR>
<BR>
Sent: Wednesday, July 25, 2007 4:29 PM<BR>
<BR>
To: Ken Renshaw; Charissa Willard; Tim Gardner; Andy Sharp; Jay =
Michlin<BR>
<BR>
Subject: RE: Time table for new dev branch<BR>
<BR>
<BR>
<BR>
I am thinking it may be best to target the switch to the development =
branch and locking the cougar branch on Monday. This *should* give ample =
time for developers including HCL to get any outstanding code reviewed =
and submitted. This also leaves the weekend clear in case something goes =
wrong.<BR>
<BR>
<BR>
<BR>
Charissa was looking over my shoulder just now and agreed with this =
time-table.<BR>
<BR>
<BR>
<BR>
Larry<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
<BR>
From: Ken Renshaw<BR>
<BR>
Sent: Wednesday, July 25, 2007 4:09 PM<BR>
<BR>
To: Larry Scheer<BR>
<BR>
Cc: Charissa Willard; Tim Gardner; Andy Sharp; Jay Michlin<BR>
<BR>
Subject: RE: Time table for new dev branch<BR>
<BR>
<BR>
<BR>
Thanks for all the info Larry, I *was* in a wait loop to hear back on =
this as matter of fact.<BR>
<BR>
<BR>
<BR>
Since there is no merging to be done, simply moving =
cougar-&gt;main-&gt;dev, I don't need much time at all to get this done. =
I can do it tonight, first thing in the morning ( say 9 AM lock time ), =
or any other time of your choosing. Just let me know your team's =
preference.<BR>
<BR>
<BR>
<BR>
Thanks,<BR>
<BR>
<BR>
<BR>
-Ken<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
<BR>
From: Larry Scheer<BR>
<BR>
Sent: Wed 7/25/2007 4:08 PM<BR>
<BR>
To: Ken Renshaw<BR>
<BR>
Cc: Charissa Willard; Tim Gardner; Andy Sharp; Jay Michlin<BR>
<BR>
Subject: Time table for new dev branch<BR>
<BR>
<BR>
<BR>
Hi Ken,<BR>
<BR>
&nbsp;&nbsp;&nbsp; Everyone in software development is awaiting the =
arrival of the official development branch. If you were waiting for the =
&quot;official&quot; word to get started on creating the development =
branch let this email serve as that notice.<BR>
<BR>
<BR>
<BR>
In case you didn't get the word Charissa has taken the reins from Brian =
De Forest as the Zonda project leader. Charissa, along with Tim, Andy =
and I want to see a smooth and expedient transition to the new =
branch.<BR>
<BR>
<BR>
<BR>
The developers need a time table for when to get their outstanding =
changes checked in to the cougar branch. HCL will also need to have =
adequate notice.<BR>
<BR>
<BR>
<BR>
Will you please provide engineering with a schedule and appropriate =
notice when the cougar branch will be locked and integrations to main =
and the new branch will occur and any other detail that would be =
helpful?<BR>
<BR>
<BR>
<BR>
If you need anything from me please ask.<BR>
<BR>
<BR>
<BR>
Thanks,<BR>
<BR>
<BR>
<BR>
Larry<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7CF16.8BB3B9A7--
