I think it adds more confusion that meaning and in Bazaar we just don't use it.
I think the closest word for the intended meaning is "Accepted" - I've seen at least one other tracker to use that to mean "the team accepts that this is a bug and they will eventually fix it." It is possible (but maybe rare) that there are widely confirmed bugs that the team does not accept. It's also a bit like "ready to code" - all the data is there to start fixing it. However I think this is only weakly related to status and more strongly related to other things. Launchpad already has access control on the targeting and priority fields, so the team can more clearly express their intention to fix the bug, or not, at that level. This intention then remains even if the bug changes status to be incomplete or reopened. Also, contentious bugs, which seem to be the only place where this matters, already flap between being wontfix/confirmed/invalid/etc. So having only one status that the team can set doesn't seem to help. If you want a 'ready to code' concept for bugs that need no more discussion that seems better done by a tag. -- bug status "triaged" is ambiguous https://bugs.launchpad.net/bugs/238143 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
