Launchpad bug statuses

HggdH hggdh2 at gmail.com
Wed Oct 3 13:44:37 UTC 2007


From: Stefan Potyra <sistpoty at ubuntu.com>
Date: Wed, 3 Oct 2007 14:46:11 +0200

> (2) Bug statuses that are self-explanatory, so that a user/triager/developer 
> will do the right thing w.o. having to read the aforementioned page in the 
> first place. I guess the lengthy discussion in this thread showed that this 
> is not the case with your proposal.

I am not sure this would be possible -- meaning depends on context.
Your interpretation (given the context you are working under) will
probably be slightly different from mine (given the context I am
working under). Cristian, on his piece [1], gives out the meaning for
each of them under the context of bug work. He is also giving out
(implicitly) a state machine that regulates how we move from one word
(status) to another.

Of course, some words have rather heavy interpretation on day-today
(clerical) usage, and a BTS that disregards it will face comprehension
issues. So, for example, closing a bug 'Invalid' gives the feeling that
the bug does not have merit -- which is not always the case (per [1]).

We may discuss if the different stati are enough to cover all options,
propose more, or request a different meaning. But, at the end, for each
status word, we have to have a precise meaning.

---

So it seems that on LP as it is today, a bug can be closed with one of
the (Fix Released, Invalid, Wont Fix) stati. Perhaps we could be better
of with a breakdown of 'Invalid' in (for example) 'No Response' and
'Invalid'.

And so forth.

Cheers,

..hggdh..




[1] http://news.launchpad.net/general/of-bugs-and-statuses


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20071003/77792724/attachment.sig>


More information about the Ubuntu-devel-discuss mailing list