X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C406.440464C9@onstor-exch02.onstor.net>; Wed, 11 Jul 2007 13:55:59 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C406.440464C9"
Content-class: urn:content-classes:message
Subject: Zonda branch going away tomorrow at 9 AM
Date: Wed, 11 Jul 2007 13:55:59 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D436@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Zonda branch going away tomorrow at 9 AM
Thread-Index: AcfEBA2sFFqKz8TzSsWByk4HD6NMRg==
X-Priority: 1
Priority: Urgent
Importance: high
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_01C7C406.440464C9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Did that get your attention? :)

As most already know, we are going to be merging the project branches =
for Zonda and cougar and going forward using a single branch for EverON =
development. Tomorrow morning at 9 AM I will be locking the Zonda branch =
for good and pushing the code through main and into the cougar branch. =
This means that whatever opened work you have against the Zonda branch =
must be checked in tonight or you will have to migrate the changes =
manually into a new workspace.

The plan going forward is this, worked out with Larry and the cougar =
team:

# Get developers to submit any outstanding Zonda change lists
# Lock the ZONDA branch (it is now dead)
# Integrate latest in ZONDA to main
# Integrate cougar with latest in main
# Developers submit all outstanding work/changes for the cougar branch
# Fix any last minute build issues, etc.
# Zonda submittal three comes from the cougar branch
# The cougar branch is locked and at end of life (avoid the problem of =
check-ins after submittal)
# The cougar branch is pushed to main
# The dev branch is created from main
# All future Zonda submittals come from the dev branch until the Zonda =
release branch is created.

I'm not sure at this time when the third submittal for Zonda will be =
requested, but as noted above it will come out of the cougar branch. =
After a successful Zonda submittal the rest of the plan will be carried =
out, effectively closing all open project branches and creating a single =
branch called 'dev' for all ongoing EverON development.

I will check the nightly buildlogs in the morning to make sure the Zonda =
code builds cleanly and if so I'll lock the branch and that will be =
that. I will send out an email in the morning once the process has =
begun, and another once the cougar branch is ready for Zonda developers.

If there are any questions please let me know.

Thanks also to Larry for all his work and brainstorming with me on this.

-Ken





------_=_NextPart_001_01C7C406.440464C9
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>Zonda branch going away tomorrow at 9 AM</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Did that get your attention? :)<BR>
<BR>
As most already know, we are going to be merging the project branches =
for Zonda and cougar and going forward using a single branch for EverON =
development. Tomorrow morning at 9 AM I will be locking the Zonda branch =
for good and pushing the code through main and into the cougar branch. =
This means that whatever opened work you have against the Zonda branch =
must be checked in tonight or you will have to migrate the changes =
manually into a new workspace.<BR>
<BR>
The plan going forward is this, worked out with Larry and the cougar =
team:<BR>
<BR>
# Get developers to submit any outstanding Zonda change lists<BR>
# Lock the ZONDA branch (it is now dead)<BR>
# Integrate latest in ZONDA to main<BR>
# Integrate cougar with latest in main<BR>
# Developers submit all outstanding work/changes for the cougar =
branch<BR>
# Fix any last minute build issues, etc.<BR>
# Zonda submittal three comes from the cougar branch<BR>
# The cougar branch is locked and at end of life (avoid the problem of =
check-ins after submittal)<BR>
# The cougar branch is pushed to main<BR>
# The dev branch is created from main<BR>
# All future Zonda submittals come from the dev branch until the Zonda =
release branch is created.<BR>
<BR>
I'm not sure at this time when the third submittal for Zonda will be =
requested, but as noted above it will come out of the cougar branch. =
After a successful Zonda submittal the rest of the plan will be carried =
out, effectively closing all open project branches and creating a single =
branch called 'dev' for all ongoing EverON development.<BR>
<BR>
I will check the nightly buildlogs in the morning to make sure the Zonda =
code builds cleanly and if so I'll lock the branch and that will be =
that. I will send out an email in the morning once the process has =
begun, and another once the cougar branch is ready for Zonda =
developers.<BR>
<BR>
If there are any questions please let me know.<BR>
<BR>
Thanks also to Larry for all his work and brainstorming with me on =
this.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7C406.440464C9--
