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

Stefan Seefeld wrote:
> Ben Bucksch wrote:

> > 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...

I agree completely about the base-class in terms of implementation but
not for the interface, but anyhow...

When a bug is entered, is a matching task also generated, which
essentially is a 'bug fix' task? If not automatically generated, IMO it
would be useful to have a way of specifying which task might solve it.
Basically each bug has one (and only one?) matching task which
would/will solve it.

To be clear, is the intention for bugs to contain just observations of a
problem? and for tasks (incl bug fixes) to just contain the solutions?

Users see (listings of) bugs; tasks are (mostly) for developers, or
those who would like to take more of an interest in the project. Bugs
don't get modified directly, except perhaps for importance, etc. -
things like the % fixed of a bug is something that could be controlled
through the task instead? (though still stored in the bug; ie. bugs have
only the equivalent of a get_percent_done(), with the setting done via
its 'friend' task)

It might be useful to have a 'bug listing' in the users (or status?)
section and a 'task listing' in the developers section of the web-site,
following this logic, though that is not to say that there shouldn't be
a fuller interface as at issues.fresco.org.

This is what seems to make sense for me, but I'm not sure this is how
RoundUp (is that the name for the issue tracker?) treats things ATM;
perhaps this is already how things are, since I've not done too much
with it as yet!

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

Hopefully this is not fruitless ;)

-- 
Neil