intrigeri:
> As far as I can tell, the main purpose of "Fix committed" is to allow
> us to list issues that the next Tails release will fix. If we instead
> close such issues as "Resolved", we can get the same list, by looking
> at the list of "Resolved" tickets with Target version == next release.
> I've looked at our doc and it seems to me that all use cases for "Fix
> committed" would be satisfied just as well that way.
>
> Did I miss anything? Is there any problem that "Fix committed" solves
> for you, on which we would regress if we dropped that status?
"Fix committed" is pretty much the same as "Resolved" from a developer's
perspective: it means "no more work to be done". But it's very different
from a user's perspective: "Fix committed" is not solved for users yet.
This might be relevant for help desk for example or to the few power
users who actually check "the list of things that will be in the next
release", as per /support. But I'm not sure that this is worth blocking
the simplification that you are proposing here.
--
sajolida
Tails —
https://tails.boum.org/
UX · Fundraising · Technical Writing
