AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<tim.gardner@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E097CC466@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 18 Apr 2008 14:16:03 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>
Subject: Re: Branch policies
Message-ID: <20080418141603.2120cc59@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E097CC466@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E097CC466@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 17 Apr 2008 15:54:39 -0700 "Tim Gardner"
<tim.gardner@onstor.com> wrote:

> 
> I propose to send the following email to the software team.
> Please provide your input before I do so.
> 
> Tim
> 
> 
> 
> 
> 
> 
> 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. 
> 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. 
> *	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:
> *	test the change
> *	complete a code review
> *	check the change into the dev branch
> *	integrate the change to a beta_cg branch workspace
> *	test the change
> *	notify me of the change. I will act as the reviewer for all
> checkins to the beta branch.
> 
> 
> 
> 
> 
