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

Neil Pilgrim wrote:

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

Is that really necessary ? As I argued with Ben, 'Bug'-the-entity is 
really a bit a 'bugfix'-task, i.e. it is an issue associated with an
actual bug. The task is thus implicit.
Sometimes that is not enough, at which point it makes sense to make
this relationship between bug and task explicit. Then you create a task
and add a 'solves' relationship. But often this will not be necessary.
Keep it simple.

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

obviously not. Or else a bug wouldn't need a history, a 'nosy list',
a status, etc. See above...

> 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

Yes ! Precisely !

(That's one reason why everybody can submit bugs, but only developers
can define new tasks.)

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

you are quite right. And I intend to have reports generated nightly
that are then linked to from the 'user' and 'developer' section of our
home page.

Regards,
		Stefan