X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C6FEBE.841A44DF@onstor-exch02.onstor.net>; Thu, 2 Nov 2006 12:36:04 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6FEBE.841A44DF"
References: <BB375AF679D4A34E9CA8DFA650E2B04E01335E57@onstor-exch02.onstor.net> <20061102122958.05c6a3c0@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Clio, Lamborghini, and DeLorean project branches and current checkin policy
Date: Thu, 2 Nov 2006 12:33:46 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E01335E5E@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+vcMGF1gB6/WmSXWMVzY/lujI5wAAG9Py
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andrew Sharp" <andy.sharp@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Jay Michlin" <jay.michlin@onstor.com>,
	"Jerry Lopatin" <jerry.lopatin@onstor.com>,
	"Andrew LeFebvre" <andrew.lefebvre@onstor.com>

This is a multi-part message in MIME format.

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

Thanks Andy. The directory layouts are common between branches and =
should definitely be outlined and posted in the howtodev wiki additions. =
The status and deliverables though, maybe better on a per-project =
page...we do use \\mightydog\QE\Projects for containing all the =
submittal notes, test plans, etc. already.

Thanks,

-Ken


-----Original Message-----
From: Andrew Sharp [mailto:andy.sharp@onstor.com]
Sent: Thu 11/2/2006 12:29 PM
To: Ken Renshaw
Cc: dl-Software; dl-QA; Paul Hammer; Jay Michlin; Jerry Lopatin; Andrew =
LeFebvre
Subject: Re: Clio, Lamborghini, and DeLorean project branches and =
current checkin policy
=20

This would be a good candidate for information that should go onto a
wiki page (directory layout?  branch descriptions/status?), in addition
to emailing it around.

Cheers,

a

 On Thu, 2 Nov 2006 11:13:22 -0800 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> Hi Everyone.
>=20
> 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
>=20
> The current defined projects and release vehicles are:
>=20
> 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.
>=20
> 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
>=20
> 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
>=20
> 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.
>=20
> 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.
>=20
> -Ken
>=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.28">
<TITLE>RE: Clio, Lamborghini, and DeLorean project branches and current =
checkin policy</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Thanks Andy. The directory layouts are common between =
branches and should definitely be outlined and posted in the howtodev =
wiki additions. The status and deliverables though, maybe better on a =
per-project page...we do use \\mightydog\QE\Projects for containing all =
the submittal notes, test plans, etc. already.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andrew Sharp [<A =
HREF=3D"mailto:andy.sharp@onstor.com">mailto:andy.sharp@onstor.com</A>]<B=
R>
Sent: Thu 11/2/2006 12:29 PM<BR>
To: Ken Renshaw<BR>
Cc: dl-Software; dl-QA; Paul Hammer; Jay Michlin; Jerry Lopatin; Andrew =
LeFebvre<BR>
Subject: Re: Clio, Lamborghini, and DeLorean project branches and =
current checkin policy<BR>
<BR>
<BR>
This would be a good candidate for information that should go onto a<BR>
wiki page (directory layout?&nbsp; branch descriptions/status?), in =
addition<BR>
to emailing it around.<BR>
<BR>
Cheers,<BR>
<BR>
a<BR>
<BR>
&nbsp;On Thu, 2 Nov 2006 11:13:22 -0800 &quot;Ken Renshaw&quot;<BR>
&lt;ken.renshaw@onstor.com&gt; wrote:<BR>
<BR>
&gt; Hi Everyone.<BR>
&gt;<BR>
&gt; As most know, we've spent the last week or so merging 1.3.3 and =
2.0<BR>
&gt; into a Clio 2.1 project and it went very well. We released =
Submittal<BR>
&gt; 1 of the merged code yesterday. I have setup three branches for =
the<BR>
&gt; next few projects based on this codeline.<BR>
&gt;<BR>
&gt; The current defined projects and release vehicles are:<BR>
&gt;<BR>
&gt; Clio =
release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; 2.1.0.0<BR>
&gt; Clio =
branch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; //depot/R2_1_X_work/...<BR>
&gt; Clio checkin policy:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
branch locked, only MF Clio allowed<BR>
&gt; Clio =
deliverables:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Shore up the merged 1.3.3/2.0 code and<BR>
&gt; fix the dozen or so MF Clio's and get it out the door.<BR>
&gt;<BR>
&gt; Lamborghini release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2.1.1.0<BR>
&gt; Lamborghini branch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
//depot/FB-LAMBORGHINI/...<BR>
&gt; Lamborghini checkin policy: branch locked, only MF Lamborghini =
and<BR>
&gt; set features allowed Lamborghini deliverables:&nbsp;&nbsp; DMIP =
features<BR>
&gt;<BR>
&gt; DeLorean =
release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2.2.0.0<BR>
&gt; DeLorean =
branch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 //depot/FB-DELOREAN/...<BR>
&gt; DeLorean checkin policy:&nbsp;&nbsp;&nbsp; branch open to all ( be =
gentle so this<BR>
&gt; does not become a dumping ground ) DeLorean delieverables:<BR>
&gt; feature set not yet decided upon<BR>
&gt;<BR>
&gt; All three branches are currently the same, i.e. represent the =
Clio<BR>
&gt; 2.1 Submittal 1 code. As MF work is assigned to Clio and =
Lamborghini<BR>
&gt; I will place the developers assigned the work onto the access =
lists<BR>
&gt; for the various branches. Dev leads, if there is a small set of<BR>
&gt; people you know you need on a particular branch, please send me =
that<BR>
&gt; information and I will add those developers now. If there is =
any<BR>
&gt; question as to where particular coding work should be done please =
ask<BR>
&gt; your manager, or Sandrine or I and we can probablyg et it figured =
out.<BR>
&gt;<BR>
&gt; Thanks, and please let me know if there are any questions or<BR>
&gt; concerns. As we go forward, I will be synching the maturing Clio =
code<BR>
&gt; into the two child branches to keep them up to date. I will do =
this<BR>
&gt; probably within a day of releasing Clio Submittals.<BR>
&gt;<BR>
&gt; -Ken<BR>
&gt;<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6FEBE.841A44DF--
