On Tue, Sep 28, 2010 at 4:04 PM, Bill Hoffman wrote:
> On 9/28/2010 4:53 PM, James Bigler wrote:
>
>
>> I feel a bug shouldn't be closed until the fix can be found in a CMake
>> release. The bug should also make it clear which release the fix should
>> be found in. Pushing the fix to "next" does
On 9/28/2010 4:53 PM, James Bigler wrote:
I feel a bug shouldn't be closed until the fix can be found in a CMake
release. The bug should also make it clear which release the fix should
be found in. Pushing the fix to "next" doesn't qualify as being closed,
because I can't expect my customers
On Tue, Sep 28, 2010 at 12:26 PM, Bill Hoffman wrote:
> On 9/28/2010 2:18 PM, Alexander Neundorf wrote:
>
>> On Tuesday 28 September 2010, David Cole 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
>>>
On 9/28/2010 2:18 PM, Alexander Neundorf wrote:
On Tuesday 28 September 2010, David Cole 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 inte
On Tuesday 28 September 2010, David Cole 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 i
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 wrote:
> When I fix a bug, I mark it a
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
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@cmake.org
http://public.kitware.
