Most places I've worked, and I think the redhat guys, use the following rule of thumb.
P1 must:
1) Be in a currently supported production version (not EOL'd or beta/preview/rc release)
2) Must be a bug, not an enhancement
3) Must be consistently reproducable, with steps to reproduce attached to the bug
4) Must be a blocker, with no workaround.
Just an FYI there :)
--- On Sun, 12/7/09, Eduardo Pelegri-Llopart <pelegri@sun.com> wrote:
> From: Eduardo Pelegri-Llopart <pelegri@sun.com>
> Subject: Re: Dissapointed
> To: users@glassfish.dev.java.net, "Eduardo Pelegri-Llopart" <pelegri@sun.com>
> Received: Sunday, 12 July, 2009, 7:24 AM
> Let me talk with some folks on Monday
> about what we can do on the triage/evaluation front.
>
> At Sun we traditionally use separate concepts of priority
> and severity, one indicating the impact on the user
> (user-controled value) and the other the prioritized impact
> (team-controlled value). Bugzilla only has one value,
> which is a problem.
>
> - eduard/o
>
>
> Adam Jenkins wrote:
>
> > May I suggest that you modify bugzilla so that the
> general public can't submit P1 issues?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
____________________________________________________________________________________
Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
Show me how:
http://au.mobile.yahoo.com/mail