X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C413.E5BE15F1@onstor-exch02.onstor.net>; Wed, 11 Jul 2007 15:33:34 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Zonda branch going away tomorrow at 9 AM
Date: Wed, 11 Jul 2007 15:33:34 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E047C361D@onstor-exch02.onstor.net>
In-Reply-To: <20070711160334.2afd5a97@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Zonda branch going away tomorrow at 9 AM
Thread-Index: AcfED7Uz1+iiSVkURMKRmElCPFDkpQAAD8vQ
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D436@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E047C35DE@onstor-exch02.onstor.net> <20070711160334.2afd5a97@ripper.onstor.net>
From: "Brian DeForest" <brian.deforest@onstor.com>
To: <dl-software>

Just for clarification and to avoid confusion about terminology, as Ken
pointed out, the "dev" branch will be a single branch for both Zonda
(BSD) and Cougar (Linux) development.  The Zonda and Cougar branches
will be very short-lived and builds will start coming from the "dev"
branch. =20

The Cougar team will be responsible for Linux porting and testing.  If
you are not part of the Cougar team, you are not responsible for
installing and testing Linux builds.  However existing Linux code should
not break as a result of any Zonda-specific checkins.  Likewise any
Cougar-specific checkins should not break Zonda builds.  So it is
everyone's responsibility to verify code builds on both DBG/OPT builds
of BSD (BC/CH) and Linux.

This will help make a common branch strategy successful.

-----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
>=20
> Did that get your attention? :)
>=20
> 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.
>=20
> The plan going forward is this, worked out with Larry and the cougar
> team:
>=20
> # 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.
>=20
> 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.
>=20
> 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.
>=20
> If there are any questions please let me know.
>=20
> Thanks also to Larry for all his work and brainstorming with me on
> this.
>=20
> -Ken
>=20
>=20
>=20
>=20
