X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C70438.51FC70D6@onstor-exch02.onstor.net>; Thu, 9 Nov 2006 11:50: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: Clio, Lamborghini, and DeLorean project branches and current checkin policy
Date: Thu, 9 Nov 2006 11:50:34 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E014FEAE8@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04EC2DDA6@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Clio, Lamborghini, and DeLorean project branches and current checkin policy
thread-index: Acb+shRY4cULn1kMQHmy73NpAJmOOQFg+q6wAABQTiYAADGEsA==
From: "Brian DeForest" <brian.deforest@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>

I think that makes sense Ken, for you to sync the Clio and Lambo trees
after each Clio submittal (at least).

Thanks.
Brian

-----Original Message-----
From: Ken Renshaw=20
Sent: Thursday, November 09, 2006 11:43 AM
To: Brian DeForest; Tim Gardner
Subject: Re: Clio, Lamborghini, and DeLorean project branches and
current checkin policy

Thanks, I should push the Clio sub 2 from yesterday  into lambo. I could
just automatically ( kinda... ) do that after each submittal if you
want.

-Ken

=20

-----Original Message-----
From: Brian DeForest
To: Ken Renshaw; Tim Gardner
Sent: Thu Nov 09 11:38:25 2006
Subject: RE: Clio, Lamborghini, and DeLorean project branches and
current checkin policy

We need to consider if Clio and Lambo branches need to be kept in sync,
such that Lambo is a superset of Clio.   For example, if a fix needs to
go into both Clio and Lambo branches, we'll need to determine if the
developer or someone else (Ken?) will sync the branches.

One person indicated that DMIP is broken in Lambo because a fix from Max
is in Clio and not in Lambo.   I haven't verified this and am not sure
if this is correct or not, but this seems like a possible scenario.

If you're already on top of this, you can ignore my email.

Brian

-----Original Message-----
From: Ken Renshaw=20
Sent: Thursday, November 02, 2006 11:13 AM
To: dl-Software; dl-QA
Cc: Paul Hammer; Jay Michlin; Jerry Lopatin; Andrew LeFebvre
Subject: Clio, Lamborghini, and DeLorean project branches and current
checkin policy

Hi Everyone.

As most know, we've spent the last week or so merging 1.3.3 and 2.0 into
a Clio 2.1 project and it went very well. We released Submittal 1 of the
merged code yesterday. I have setup three branches for the next few
projects based on this codeline.=20

The current defined projects and release vehicles are:

Clio release:               2.1.0.0
Clio branch:                //depot/R2_1_X_work/...
Clio checkin policy:        branch locked, only MF Clio allowed
Clio deliverables:          Shore up the merged 1.3.3/2.0 code and fix
the dozen or so MF Clio's and get it out the door.

Lamborghini release:        2.1.1.0
Lamborghini branch:         //depot/FB-LAMBORGHINI/...
Lamborghini checkin policy: branch locked, only MF Lamborghini and set
features allowed
Lamborghini deliverables:   DMIP features

DeLorean release:           2.2.0.0
DeLorean branch:            //depot/FB-DELOREAN/...
DeLorean checkin policy:    branch open to all ( be gentle so this does
not become a dumping ground )
DeLorean delieverables:     feature set not yet decided upon

All three branches are currently the same, i.e. represent the Clio 2.1
Submittal 1 code. As MF work is assigned to Clio and Lamborghini I will
place the developers assigned the work onto the access lists for the
various branches. Dev leads, if there is a small set of people you know
you need on a particular branch, please send me that information and I
will add those developers now. If there is any question as to where
particular coding work should be done please ask your manager, or
Sandrine or I and we can probablyg et it figured out.

Thanks, and please let me know if there are any questions or concerns.
As we go forward, I will be synching the maturing Clio code into the two
child branches to keep them up to date. I will do this probably within a
day of releasing Clio Submittals.

-Ken

