Nathan L. Adams posted <[EMAIL PROTECTED]>, excerpted below, on Fri, 08 Jul 2005 07:42:23 -0400:
> Duncan wrote: >> >> Well, not blocker <g>, but ... >> http://bugs.gentoo.org/show_bug.cgi?id=73181 >> >> > This brings up a point that really irks me. In the bug, I believe the dev > implies that the reported bug has merit /yet he closes the bug before > actually doing something about it/. And I don't mean to pick on Jeffrey; > this seems to be a common habit among Gentoo devs. OK... as the one that filed the bug... I agree with how this was handled. resolved-remind was appropriate. The bug had been open for some months (IIRC), and it /was/ a long-term bug, I knew that when I filed it. resolved-remind is IMO an appropriate resolution for that, getting it off the immediate list, acknowledging it needs investigated further, but indicating "not now". Also note that the bug is NOT "closed", only /resolved/. There /is/ a not insignificant technical difference, altho it /does/ seem Gentoo doesn't seem to actually close bugs that often. "Resolved" is technically (as I understand it) that state at which the resolution is there (or put off, if status remind), but not yet "shipping". With conventional resolutions, that would roughly coincide with resolved-inCVS. "Closed" indicates not only that a solution has been found, but that it has been verified to work, and shipped, which in Gentoo parlance would mean there has been an official release either incorporating it or since it was put in the tree. Perhaps unfortunately, Gentoo QA doesn't always extend to that degree and it seems resolved==closed for all intents and purposes to us. However, given that Gentoo is a community based distribution, that may be practical reality -- it may not be practical to enforce rigid "closed" QA standards and definitions on us, if there isn't the necessary QA resources to actually follow up on all those "resolved" bugs and close them or re-open them to full-open status, if necessary. Anyway, I'm basically satisfied with resolved-remind, which is of course exactly what I did, when the issue came up once again, and there was focus on it. My remaining question, of course, would be whether it's appropriate to re-open the bug at this point now that it's being worked on, or not. Technically, I'd say yes, "remind" at this point is exactly what should be done. However, socially/practically may be a different matter, particularly with another bug on the same thing, now. With work on it already underway, it's possible reopening the bug now would just complicate things needlessly, and/or even insult the poor dev working on it, who could interpret the reopening as if I don't like his efforts -- VERY far from the truth, I have been VERY impressed with the work to the product selection page! Opinions? -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
