[systemd-bugs] [Bug 66664] journalctl boot reporting inconsistent

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=66664

--- Comment #13 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
(In reply to comment #11)
> FYI: Status of this bug had been NEEDINFO. Once I provided the requested
> info, I changed the status to ASSIGNED (since it seemed the most sensible of
> all available options). But now looking at the list of other open systemd
> bugs, I see that no others are in the ASSIGNED category, so it was probably
> a mistake for me to have changed it to that value. Apologies. Reverting it
> now to NEW, since that seems to be the most popular choice, even though I
> don't understand the semantics.
We use ASSIGNED to signal that we're working on something, i.e. for
communication between developers to avoid duplicate work. So the bug should
stay NEW until somebody actually starts working on the solution.

> Btw, clicking on the "help" link for the "Status" dropdown yields a page of
> essentially useless info, since it explains semantics only for tags
> CONFIRMED, UNCONFIRMED, and INPROGRESS, none of which are actually used on
> this site. Would be nice to have explanations for semantics of tags actually
> in use here, i.e. NEW, ASSIGNED, RESOLVED, and NEEDINFO.
https://bugs.freedesktop.org/show_bug.cgi?id=66887

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130714/439bb086/attachment-0001.html>