X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8A1B8.8DEBDAB0@onstor-exch02.onstor.net>; Fri, 18 Apr 2008 17:59:00 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Branch policies
Date: Fri, 18 Apr 2008 17:59:00 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E056C9571@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E098A6F87@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Branch policies
Thread-Index: Acihrnx2v91Mw1ZwQqi6R3MZGPYYGQAACcJAAAI1SLA=
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>


Look at the change lists coming into dev you will see that coverity
fixes are still going in (yesterday, change # 28858) and Jobi's team are
still adding file system features to the development branch or changes
with no defect number assigned to them. For instance look at changes
28892, 28895, 28874, to point out a recent few.=20

This appears to run counter to what we heard Bob say in meeting after
meeting. If this work is part of the cougar deliverables it is not
anything that was communicated to us. Perhaps this just a communication
problem with Paul's group where we don't know what his teams are doing
and how it fits into the cougar release. It would be nice to know what
is going on and why.

Larry

-----Original Message-----
From: Brian Stark=20
Sent: Friday, April 18, 2008 4:50 PM
To: Andy Sharp; Tim Gardner
Cc: Larry Scheer
Subject: RE: Branch policies

Guys,

Besides the coverity work, escalations, and quals, who else in Dev is
working on things outside of Cougar?  We've sent the message loud and
clear that this shouldn't be happening.  I'd like to know if there are
folks who haven't understood this message.


Brian


> -----Original Message-----
> From: Andy Sharp=20
> Sent: Friday, April 18, 2008 4:47 PM
> To: Tim Gardner
> Cc: Brian Stark; Larry Scheer
> Subject: Re: Branch policies
>=20
> Just a short note after having a quick chat with Larry who=20
> informed me of some things I wasn't exactly up to speed on,=20
> if there are people that just can't be made to do the right=20
> thing and work on Cougar, then I really don't care where they=20
> stick their changes, but they're not going into dev, until=20
> possibly after GA or whatever.  Makes me frustrated.
>=20
> On Thu, 17 Apr 2008 15:54:39 -0700 "Tim Gardner"
> <tim.gardner@onstor.com> wrote:
>=20
> >=20
> > I propose to send the following email to the software team.
> > Please provide your input before I do so.
> >=20
> > Tim
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20
> > Over the past few weeks we have been working hard to=20
> develop a branch=20
> > strategy that will enable us to deliver a quality cougar=20
> product, have=20
> > a successful cougar beta program, and continue to support=20
> non-cougar=20
> > work such as escalation fixes. I thank you all for the=20
> valuable input=20
> > that you have provided during this process.
> >=20
> > As of now I would like to institute the following policies:
> >=20
> > 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=20
> > 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=20
> > may be asked to hold the change in your workspace or=20
> utilize a feature=20
> > 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.
> >=20
> > 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.
> >=20
> >=20
> >=20
> >=20
> >=20
>=20
