[cmake-developers] What to do with the RESOLVED issues ?

[Dave Partyka]

In all of the bug tracking systems I have participated in, it is usually the
role of the reporter to verify and close, or at least confirm somehow that
the bug is fixed and then the project manager closes the bug.

On Tue, Sep 28, 2010 at 5:26 AM, David Cole <david.cole at kitware.com> wrote:

> When I fix a bug, I mark it as "resolved."
>
> I expect that somebody else who cares about the bug will come along behind
> me and double-check me on it. So... I leave it to the reporter or some other
> interested party to "close" it.
>
> If there is consensus that this approach is undesirable, I'd be happy to
> just "close" them instead of "resolving" them.
>
> Why does it matter, as long as they are not "open" anymore?
>
>
> On Sat, Sep 25, 2010 at 3:06 PM, Alexander Neundorf <neundorf at kde.org>wrote:
>
>> Hi,
>>
>> there are currently 169 RESOLVED issues for cmake:
>> http://public.kitware.com/Bug/view_all_bug_page.php?filter=40216
>>
>> Should they all just be changed to CLOSED ?
>>
>> Alex
>> _______________________________________________
>> cmake-developers mailing list
>> cmake-developers at cmake.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>>
>
>
> _______________________________________________
> cmake-developers mailing list
> cmake-developers at cmake.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20100928/97a93147/attachment.html>