X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C4A3.2601DA07@onstor-exch02.onstor.net>; Thu, 12 Jul 2007 08:38:59 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: The Zonda branch has been locked - Was: RE: Zonda branch going away tomorrow at 9 AM
Date: Thu, 12 Jul 2007 08:38:59 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E047C38EF@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D436@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: The Zonda branch has been locked - Was: RE: Zonda branch going away tomorrow at 9 AM
Thread-Index: AcfEBA2sFFqKz8TzSsWByk4HD6NMRgAnqgDw
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"dl-Engineering" <dl-engineering@onstor.com>

Good morning.=20

The Zonda nightly compilation passed so I have locked //depot/ZONDA/...
against any more writes and am pushing the code to main and then to
cougar.

If you have any opened work against the old Zonda branch you sill have
to recreate a new changelist against //depot/cougar/..., or
//depot/dev/... once it's been created.=20

I will send out another email once the Zonda code has been pushed
through to cougar and the branch is ready to go for Zonda submittal 3
checkins.

Thanks,

-Ken

-----Original Message-----
From: Ken Renshaw=20
Sent: Wednesday, July 11, 2007 2:56 PM
To: dl-Engineering
Subject: Zonda branch going away tomorrow at 9 AM
Importance: High

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




