X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8A3FF.29B3B490@onstor-exch02.onstor.net>; Mon, 21 Apr 2008 15:29:29 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8A3FF.29B3B490"
Content-class: urn:content-classes:message
Subject: Branch policies
Date: Mon, 21 Apr 2008 15:29:28 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E098A751B@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Branch policies
Thread-Index: Acij/ylxWbzXaw4BTC+OErggBS8BYw==
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "dl-Cougar" <dl-Cougar@onstor.com>,
	"dl-Software" <dl-software@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8A3FF.29B3B490
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Over the past few weeks we have been working hard to develop a branch
strategy that will
enable us to deliver a quality cougar product, have a successful cougar
beta program, and
continue to support non-cougar work such as escalation fixes. I thank
you all for the
valuable input that you have provided during this process.

As of now I would like to institute the following policies:

dev branch
*	Unrestricted for any fixes for cougar defects. As always, the p4
change description must contain the defect number.
*	Unrestricted for any fixes done by the escalation team.=20
I do ask that the escalation team communicate to me any significant
changes or changes that pose high
risk for regression.
*	Unrestricted for unit tests and automated test code
(nfx-tree/test).
*	For any other changes I ask that you first talk to me so that I
can understand the potential impact the change
presents. You may be asked to hold the change in your workspace or
utilize a feature branch until after
cougar beta or cougar GA.=20
At this time all developers are supposed to be working on cougar
defects. Coverity work has been halted.
All non-test related checkins are expected to be associated with a
defect number. This is needed to help QA and dev
determine potential regression impact.
*	All changes must be tested and code reviewed. The code review
must involve a discussion about how the change was tested.

beta_cg
*	The cougar beta branch is restricted to fixes for cougar beta MF
defects.
This branch is currently the same as submittal 18.
*	After fixing a beta MF defect a developer must:
*	check the change into the dev branch
*	integrate the change to a beta_cg branch workspace
*	test the change using the beta_cg code base
*	notify me of the change. I will act as the reviewer for all
checkins to the beta branch.


If anyone has any comments or questions about this, lets discuss them at
the Cougar project team meeting on Tuesday at 1:30.






------_=_NextPart_001_01C8A3FF.29B3B490
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Branch policies</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Over the past few weeks we have been =
working hard to develop a branch strategy that will</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">enable us to deliver a quality cougar =
product, have a successful cougar beta program, and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">continue to support non-cougar work =
such as escalation fixes. I thank you all for the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">valuable input that you have provided =
during this process.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As of now I would like to institute the =
following policies:</FONT>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">dev branch</FONT></B>
<UL>
<UL>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Unrestricted for any fixes for cougar =
defects. As always, the p4 change description must contain the defect =
number.</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">Unrestricted for any fixes done by the =
escalation team.<BR>
I do ask that the escalation team communicate to me any significant =
changes or changes that pose high<BR>
risk for regression.</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">Unrestricted for</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">unit tests and automated test code =
(nfx-tree/test).</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">For any other changes I ask that you =
first talk to me so that I can understand the potential impact the =
change<BR>
presents. You may be asked to hold the change in your workspace or =
utilize a feature branch until after<BR>
cougar beta or cougar GA.<BR>
At this time all developers are supposed to be working on cougar =
defects. Coverity work has been halted.<BR>
All non-test related checkins are expected to be associated with a =
defect number. This is needed to help QA and dev<BR>
determine potential regression impact.</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">All changes must be tested and code =
reviewed. The code review must involve a discussion about how the change =
was tested.</FONT></LI>
<BR>
</UL></UL>
<P><B><FONT SIZE=3D2 FACE=3D"Arial">beta_cg</FONT></B>
<UL>
<UL>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The cougar beta branch is restricted =
to fixes for cougar beta MF defects.</FONT><B><BR>
</B><FONT SIZE=3D2 FACE=3D"Arial">This branch is currently the same as =
submittal 18.</FONT><B></B></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">After fixing a beta MF defect a =
developer must:</FONT><B></B></LI>

<UL>
<LI><FONT SIZE=3D2 FACE=3D"Arial">check the change into the dev =
branch</FONT><B></B></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">integrate the change to a beta_cg =
branch workspace</FONT><B></B></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">test the change using the beta_cg code =
base</FONT><B></B></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">notify me of the change. I will act as =
the reviewer for all checkins to the beta branch.</FONT><B></B></LI>
<BR>
<BR>
</UL></UL></UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">If anyone has any comments or questions =
about this, lets discuss them at the Cougar project team meeting on =
Tuesday at 1:30.</FONT></P>
<BR>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C8A3FF.29B3B490--
