X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7043C.FA68F5C0@onstor-exch02.onstor.net>; Thu, 9 Nov 2006 12:23:54 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7043C.FA68F5C0"
Content-class: urn:content-classes:message
Subject: RE: Clio, Lamborghini, and DeLorean project branches and current checkin policy
Date: Thu, 9 Nov 2006 12:23:54 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E01335ED8@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+q6wAABQTiYAAMLQcAAAeTcJ
References: <BB375AF679D4A34E9CA8DFA650E2B04E014FEB05@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>

This is a multi-part message in MIME format.

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

I just finished this Tim. I've updated both FB-LAMBORGHINI and =
FB_DELOREAN with the Clio submittal 2 code. This will fix DMIP in both =
of those branches. After each Clio submittal from now on I will =
automatically push the code into the 2.1.1.0 and 2.2.0.0 branches unless =
I hear otherwise. I will typically do this about a day after the =
submittal is out so that we know it passes AT and is not a risk to the =
other branches to do so.=20
=20
I am not, however, planning to cascade the lambo code into the delorean =
branch yet. I'm open to when we start doing this, but I figure once Clio =
is finished next month would be a good time, unless we need it sooner.
=20
Thanks, and let me know if I can do anything else to make things run =
more smoothly between the three concurrent projects.
=20
-Ken

________________________________

From: Tim Gardner
Sent: Thu 11/9/2006 12:06 PM
To: Ken Renshaw; Brian DeForest
Subject: RE: Clio, Lamborghini, and DeLorean project branches and =
current checkin policy



Ken,

I believe that this is the right thing to do. I don't want
developers putting changes directly into both branches.
Please push clio into lambo when you get a chance. Need this
as soon as possible to unblock the lambo developers.

Tim


-----Original Message-----
From: Ken Renshaw
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



-----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
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.

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




------_=_NextPart_001_01C7043C.FA68F5C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: Clio, Lamborghini, and DeLorean project =
branches and current checkin policy</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText31920 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I just =
finished this Tim. I've updated both FB-LAMBORGHINI and FB_DELOREAN with =
the Clio submittal 2 code. This will fix DMIP in both of those branches. =
After each Clio submittal from now on I will automatically push the code =
into the 2.1.1.0 and 2.2.0.0 branches unless I hear otherwise. I will =
typically do this about a day after the submittal is out so that we know =
it passes AT and is not a risk to the other branches to do so. =
</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I am not, however, planning =
to cascade the lambo code into the delorean branch yet. I'm open to when =
we start doing this, but I figure once Clio is finished next month would =
be a good time, unless we need it sooner.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks, and let me know if I =
can do anything else to make things run more smoothly between the three =
concurrent projects.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Ken</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Tim Gardner<BR><B>Sent:</B> =
Thu 11/9/2006 12:06 PM<BR><B>To:</B> Ken Renshaw; Brian =
DeForest<BR><B>Subject:</B> RE: Clio, Lamborghini, and DeLorean project =
branches and current checkin policy<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Ken,<BR><BR>I believe that this is the right thing to =
do. I don't want<BR>developers putting changes directly into both =
branches.<BR>Please push clio into lambo when you get a chance. Need =
this<BR>as soon as possible to unblock the lambo =
developers.<BR><BR>Tim<BR><BR><BR>-----Original Message-----<BR>From: =
Ken Renshaw<BR>Sent: Thursday, November 09, 2006 11:43 AM<BR>To: Brian =
DeForest; Tim Gardner<BR>Subject: Re: Clio, Lamborghini, and DeLorean =
project branches and current checkin policy<BR><BR>Thanks, I should push =
the Clio sub 2 from yesterday&nbsp; into lambo. I could just =
automatically ( kinda... ) do that after each submittal if you =
want.<BR><BR>-Ken<BR><BR><BR><BR>-----Original Message-----<BR>From: =
Brian DeForest<BR>To: Ken Renshaw; Tim Gardner<BR>Sent: Thu Nov 09 =
11:38:25 2006<BR>Subject: RE: Clio, Lamborghini, and DeLorean project =
branches and current checkin policy<BR><BR>We need to consider if Clio =
and Lambo branches need to be kept in sync, such that Lambo is a =
superset of Clio.&nbsp;&nbsp; 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.<BR><BR>One person =
indicated that DMIP is broken in Lambo because a fix from Max is in Clio =
and not in Lambo.&nbsp;&nbsp; I haven't verified this and am not sure if =
this is correct or not, but this seems like a possible =
scenario.<BR><BR>If you're already on top of this, you can ignore my =
email.<BR><BR>Brian<BR><BR>-----Original Message-----<BR>From: Ken =
Renshaw<BR>Sent: Thursday, November 02, 2006 11:13 AM<BR>To: =
dl-Software; dl-QA<BR>Cc: Paul Hammer; Jay Michlin; Jerry Lopatin; =
Andrew LeFebvre<BR>Subject: Clio, Lamborghini, and DeLorean project =
branches and current checkin policy<BR><BR>Hi Everyone.<BR><BR>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.<BR><BR>The current defined projects and release =
vehicles are:<BR><BR>Clio =
release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; 2.1.0.0<BR>Clio =
branch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; //depot/R2_1_X_work/...<BR>Clio checkin =
policy:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; branch locked, only MF =
Clio allowed<BR>Clio =
deliverables:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
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.<BR><BR>Lamborghini =
release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2.1.1.0<BR>Lamborghini =
branch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
//depot/FB-LAMBORGHINI/...<BR>Lamborghini checkin policy: branch locked, =
only MF Lamborghini and set features allowed<BR>Lamborghini =
deliverables:&nbsp;&nbsp; DMIP features<BR><BR>DeLorean =
release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2.2.0.0<BR>DeLorean =
branch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 //depot/FB-DELOREAN/...<BR>DeLorean checkin policy:&nbsp;&nbsp;&nbsp; =
branch open to all ( be gentle so this does not become a dumping ground =
)<BR>DeLorean delieverables:&nbsp;&nbsp;&nbsp;&nbsp; feature set not yet =
decided upon<BR><BR>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.<BR><BR>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.<BR><BR>-Ken<BR><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7043C.FA68F5C0--
