Every state implies too much. The whole problem we're running into here
is that people are reading too much into one word.
Maybe "CLOSED SEECOMMENT" is the right way to go.
--g
_____________________ ____________________________________________
Greg DeKoenigsberg ] [ the future masters of technology will have
Community Relations ] [ to be lighthearted and intelligent. the
Red Hat ] [ machine easily masters the grim and the
] [ dumb. --mcluhan
Red Hat Summit ] [
New Orleans ] [ Learn. Network. Experience Open Source.
June 1/2/3 2005 ] [ (And Make Your Boss Pay For It.)
[ http://www.redhat.com/promo/summit/
On Sun, 29 May 2005, Michael Schwendt wrote:
> On Sun, 29 May 2005 11:49:35 -0400 (EDT), Greg DeKoenigsberg wrote:
>
> >
> > Maybe the real answer is that there should be bug state for bugs that are
> > closed without having been fixed:
> >
> > CLOSED NOTFIXED.
> >
> > Not judgmental, just factual. And for comments, check the bug.
>
> It implies too much. It can be inaccurate (false even) and misleading
> again in all the cases where a reporter didn't reply to NEEDINFO.
>
> --
> Fedora-maintainers mailing list
> Fedora-maintainers@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-maintainers
>
