db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: [jira] Resolved: (DERBY-2677) OnlineCompressTest failed reporting NullPointerException, actual problem in derby.log is a page checksum error.
Date Mon, 16 Jun 2008 12:26:22 GMT
Knut Anders Hatlen wrote:
> Kristian Waagan <Kristian.Waagan@Sun.COM> writes:
> 
>> Knut Anders Hatlen (JIRA) wrote:
>>>      [ https://issues.apache.org/jira/browse/DERBY-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
>>>
>>> Knut Anders Hatlen resolved DERBY-2677.
>>> ---------------------------------------
>>>
>>>     Resolution: Duplicate
>>>
>>> I don't think this failure has been seen after the fix for DERBY-3347 went in,
so I'm closing the issue. If it happens again, please reopen or file a new bug.
>> Do you mean close or resolve?
> 
> I meant resolve. Have updated the comment.
> 
>> And what is our policy on closing when it comes to issues resolved as
>> duplicates again?
> 
> I don't know if we have any formal policy, but I would expect that it's
> more or less the same as how it's normally done for issues that are
> resolved as fixed: The reporter verifies that the problem has been
> resolved and closes the issue, or reopens it if the problem is still
> present. If there is no feedback within a reasonable period of time, we
> just assume that the resolution is OK and go ahead and close the issue.
> 

I read this as that the duplicate should follow the state of the issue 
it duplicates.

I think I sometimes have closed the issues I have resolved as duplicates 
immediately. I suppose the motivation for this is that one should go to 
the original issue for details on the problem, and that these duplicates 
tend to remain lingering for a while. This is especially true if we 
don't add a duplicate link between the issues.

Note that creating a link is visible from both issues, whereas if one 
only adds a regular comment one must do it manually for both issues.



-- 
Kristian



Mime
View raw message