RE: [sv-bc] Issue Review Buckets - Reviews due by April 10

IMHO, Priority and Severity are independent classifications.

Priority is analogous to the stratified event queue. The committee
should only be discussing immediate issues, followed by urgent issues,
and so on. The higher priority you give, the faster it should go through
rthe committee.

Severity describes the impact the issue will have on the end user or
implementer, regardless of whether it is an errata or enhancement. It's
mainly for the benefit of the people reading the proposal.

A Clarification indicates no real change in functionality, and should
only have one of the 't' severities, text, trivial, or tweak.


> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
> Bresticker, Shalom
> Sent: Saturday, April 01, 2006 9:54 PM
> To: sv-bc@eda.org
> Subject: RE: [sv-bc] Issue Review Buckets - Reviews due by April 10
> 
> Also, 'Type' field allows value 'Clarification' as well as Errata and
> Enhancement. Maybe we should use that classification as well.
> 
> > How should 'severity' be used for enhancement requests?
> >
> > What other severities besides 'major' and what other priorities
> > besides
> > 'immediate' should we use?
> 
> Shalom