AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080505150257.6bffe537@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>,<paul.hammer@onstor.com>,<vikas.saini@onstor.com>,<raj.kumar@onstor.com>,<jonathan.goldick@onstor.com>,<tim.gardner@onstor.com>,<brian.stark@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	BB375AF679D4A34E9CA8DFA650E2B04E09CB7EE3@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 5 May 2008 15:03:13 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Cc: "Paul Hammer" <paul.hammer@onstor.com>, "Vikas Saini"
 <vikas.saini@onstor.com>, "Raj Kumar" <raj.kumar@onstor.com>, "Jonathan
 Goldick" <jonathan.goldick@onstor.com>, "Tim Gardner"
 <tim.gardner@onstor.com>, Brian Stark <brian.stark@onstor.com>
Subject: Re: CQ Cleanup
Message-ID: <20080505150313.189bf784@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E09CB7EE3@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E09CA562F@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E09CB7EE3@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

Would it be possible to utilize the "Must Fix in Release" field to
indicate beta MF bugs?  For instance, add a release "Cougar_Beta" to
that list.

That way, individual developers can see/sort their bug list and have
beta MF bugs easily identifiable, without having to run the canned
query for Cougar Beta MF in DEV, and then try and match those by
eyeball to bugs in their own list.

This would be a nice optimization for individual developers.

Cheers,

a

On Fri, 2 May 2008 16:14:24 -0700 "Sandrine Boulanger"
<sandrine.boulanger@onstor.com> wrote:

> I'll start the problem area and priority cleanup for the defects filed
> after 1/1/2007.
> I'll add 2 new fields to CQ to manage blocker and editable tag for
> defects. This will require a schema change and DB upgrade, so might
> not be available right away.
> See other comments inline below.
> 
> _____________________________________________
> From: Paul Hammer 
> Sent: Friday, May 02, 2008 2:24 PM
> To: Sandrine Boulanger; Vikas Saini; Raj Kumar; Jonathan Goldick; Tim
> Gardner; Andy Sharp
> Subject: RE: CQ Cleanup
> 
> We should exclude ECR's and partner owned defects since neither of
> these has a direct engineering impact. Leave those defects alone.
> 
> I am okay with the cutoff being release 2.2 and greater and defects
> submitted after 12/31/2006 (being the ones left open). 
> 
> Like the blocker field, could just be yes or no toggle. I would keep
> MF for Beta and GA a separate field.
> 
> Think that all defects that are in QA (only 14) we should retest.
> => OK
> 
> How do you suggest we tag all of the defects that were closed as part
> of this effort? Move them all to Limbo, create a new state, put a tag
> in the notes field?
> => move them to Limbo, and assign them to dummy user named
> "No_longer_valid" or something like that. But there are still a few I
> would like to keep around, as mentioned below.
> 
> _____________________________________________
> From: Sandrine Boulanger 
> Sent: 2008-05-01 17:25
> To: Paul Hammer; Vikas Saini; Raj Kumar; Jonathan Goldick; Tim
> Gardner; Andy Sharp
> Subject: CQ Cleanup
> 
> I ran a few queries to find out the scale of the cleanup. Please give
> your feedback on how to proceed. For the first 2 categories, do you
> agree with the query and the state?
> 
> 
> Priority cleanup
> 453 defects (I removed ECR) that are in states Opened, Reviewed,
> Re-opened, Failed, More-Info, Assigned or WIP do not have a priority.
> Number reduces to 168 if I pick only defects filed after 1/1/2007
> 
> Problem area cleanup
> Same query as above for states, non ECR, filed after 1/1/2007 gives
> 178 for Problem area=SW-System
> 40 for Problem area=Other
> 
> Close defects where project < 2.2 and submittal date < 1/1/2007:
> 685 defects in DEV and TRIAGE (out of which 117 are ECR, and another
> 114 are reported by Customers)
> 44 defects in Support
> 14 in QA (NR, DUP, Fixed)
> 49 are PARTNERS issues
> 
> Don't know if we can blindly close them, here are a few examples:
> autogrow is not triggered when restoring a big file
> Vscan breaks if NFS is disabled for a given virtual server
> Vscan sever did not scan the files while under stress
> Can't access widelink pointing to autocreated share from another
> autocreated share
> Execution Priv/deny from CIFS domain and allow from NIS domain is not
> properly  enforced
> Vscan is not working if interface is created with nfs=disable
> Large cluster DB size (27MB) breaks cluster communication
> Quota rebuild performance is terrible
> Can't delete a duplicate interface IP on the SSC
> 
> Way to prioritize defects instead of adding strings in Notes that
> cannot be removed:
> => add a new field with editable list where we can add "Blocker for
> Beta, MF for Beta, Blocker for GA" etc...
