Re: [Fresco-devel] issue tracking: Request For Comments

Patrick Mauritz wrote:
> On Fri, Jul 26, 2002 at 10:06:33AM -0400, Stefan Seefeld wrote:
> 
>>* status: new, open, closed
> 
> reopened ("huh, I thought I fixed this")
> pending ("I know of this, I'm working on it, but I need some time")
> (both from debian bts)

what is 'pending' vs. 'open' ? 'later' vs. 'working on it' ?
And why is it important to know that a bug had previously been closed ?
Why isn't it enough (for the status) to know that it is currently open.
The rest is available in the bug's history...

>>* priority: immediate, urgent, high, normal, low
> 
> priority is  imho... "urgent priority" but "minor severity" ?

huh ?

> 
> 
>>* severity: critical, major, normal, minor
> 
> "wishlist" severity would be nice (from debian bts)

we are talking about bugs here, not tasks. I can imagine
people sending in a wishlist, i.e. a set of tasks they wish
to be worked on. But again, that's for the 'task' entity, not 'bug'.

>>* type: crashes, resource usage, rendering, behavior
> 
> probably "API" ("hey, I think that part of the API doesn't scale")

hmm, good point. Here the distinction between bug and task/feature isn't
really clear. Don't forget that most other BTS you are comparing with
only have a single entity. We have 'Bug' *and* 'Task'.
Scalability issues should be addressed with tasks.

>>* component: build system, Prague, Babylon, Fresco, Berlin, kits...
> 
> clients

yes, the list isn't complete...


>>Tasks
> 
> new field "impact": multilink{component} 
>  (which other parts are affected)

that's pretty vague...

Stefan