X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7044A.FAC276C6@onstor-exch02.onstor.net>; Thu, 9 Nov 2006 14:04:08 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7044A.FAC276C6"
Content-class: urn:content-classes:message
Subject: RE: Clio, Lamborghini, and DeLorean project branches and current checkin policy
Date: Thu, 9 Nov 2006 14:04:07 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E014FEBB4@onstor-exch02.onstor.net>
In-Reply-To: <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+q6wAABQTiYAAMLQcAAAeTcJAAOuNwA=
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Ken Renshaw" <ken.renshaw@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_01C7044A.FAC276C6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Ken. I agree that there is no need to merge into delorean until
after clio is done.

=20

________________________________

From: Ken Renshaw=20
Sent: Thursday, November 09, 2006 12:24 PM
To: Tim Gardner; Brian DeForest
Cc: dl-Software; dl-QA
Subject: RE: Clio, Lamborghini, and DeLorean project branches and
current checkin policy

=20

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

=20

________________________________

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_01C7044A.FAC276C6
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: Clio, Lamborghini, and DeLorean project branches and current =
checkin
policy</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dnavy>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks Ken. I agree that there is =
no need
to merge into delorean until after clio is =
done.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ken =
Renshaw <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, November =
09, 2006
12:24 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Tim Gardner; Brian =
DeForest<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> dl-Software; =
dl-QA<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Clio, =
Lamborghini,
and DeLorean project branches and current checkin =
policy</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div id=3DidOWAReplyText31920>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>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. </span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>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.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks, and let me know if I can do anything else to =
make
things run more smoothly between the three concurrent =
projects.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Ken</span></font><o:p></o:p></p>

</div>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Tim
Gardner<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thu 11/9/2006 12:06 =
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Ken Renshaw; Brian =
DeForest<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Clio, =
Lamborghini,
and DeLorean project branches and current checkin =
policy</span></font><o:p></o:p></p>

</div>

<div>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>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</span></font><o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7044A.FAC276C6--
