Re: [Fresco-devel] Explanation of relation between bugs/tasks? (in issues.f.o)

Ben Bucksch wrote:
>  I'd give Task and Bug a common base type. Both track work related to a 
> certain software.
> 
> Compare the properties at the top and bottom of the schema 
> <http://issues.fresco.org//reports/schema.html>. Task and Bug share a 
> lot of properties and relations; in fact, many differences are arguable 
> (Why no Platform for tasks? Why "Resolution" in one case and "Result" in 
> another?).

Very good point ! You argue that both will have an outcome, so that 
should be reflected in a common base type with an 'outcome' attribute,
which corresponds to 'Resolution' for bugs and 'Result' for tasks.

If ever that justifies anything, it is a common *implementation*, but 
not a common *interface*. Interfaces are all about semantics, and it is
precisely the interpretation of what 'outcome' actually means that makes
the difference here. The same applies to all the other attributes, too.


> The schema doesn't mention comments. Most of the discussion part should 
> be identical: Tasks and Bugs both have comments / comment threads.

You are quite right, which is why both are implemented by means of a 
common base class (the python representation uses 'IssueClass'...).
While it is arguable that 'has a history' and 'is discussed in a thread 
of messages' is a semantic commonality, I don't see any added value in
exposing that in the schema itself.

> Both also have a notion of progress (30% finished), although that might 
> differ in details (a bug must usually be reproduced and found first 
> before it can be fixed).

right, and it is that 'detail' which makes the semantic difference here.
In fact, if you want to bring both closer, you should replace 'bug' with
'bug fix', where 'bug fix' is a work in progress. But wait, that is 
already covered ! Tasks have a 'solves' relationship to bugs...

Regards,
		Stefan

PS: oh well, please let's not start another fruitless thread. Let's work
     on M3 instead...