commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <dennis.lundb...@mdh.se>
Subject Re: Bugzilla RESOLVED vs CLOSED
Date Thu, 28 Jul 2005 12:16:09 GMT
Simon Kitching wrote:
> On Thu, 2005-07-28 at 13:05 +0200, bugzilla@apache.org wrote:
> 
>>DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
>>RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
>><http://issues.apache.org/bugzilla/show_bug.cgi?id=15519>.
>>ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
>>INSERTED IN THE BUG DATABASE.
>>
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=15519
>>
>>
>>dennis.lundberg@mdh.se changed:
>>
>>           What    |Removed                     |Added
>>----------------------------------------------------------------------------
>>            Summary|PropertyUtils.getPropertyTyp|[beanutils]
>>                   |e() for java.util.Collection|PropertyUtils.getPropertyTyp
>>                   |                            |e() for java.util.Collection
>>
>>
>>
>>
>>------- Additional Comments From dennis.lundberg@mdh.se  2005-07-28 13:05 -------
>>This issue has been marked WONTFIX which has been accepted by the reporter.
>>Shouldn't it be closed in bugzilla?
>>
> 
> 
> For open bugs there is a radio button for "resolve bug", with a dropdown
> allowing FIXED, INVALID, WONTFIX etc. No separate "close" option. 
> 
> But these entries that Dennis has noted have quite a different set of
> options: 
>   LEAVE AS WONTFIX (or VERIFIED FIXED or whatever the status is)
>   REOPEN
>   CLOSE
> 
> It looks like the former are displayed for "open" bugs while the latter
> options are displayed for bugs that are already marked RESOLVED.
> 
> Maybe Bugzilla uses RESOLVED to mean it has been fixed in version
> control while CLOSED means that the issue no longer needs to be tracked
> (eg a release with that fix has now been issued)? If so, then that makes
> sense for corporates and maybe places like Mozilla but commons
> components don't traditionally track things like that AFAIK.

Here's a snippet from the bugzilla help regarding the STATUS of an 
issue. It explains it well.

RESOLVED
     A resolution has been taken, and it is awaiting verification by QA.
     From here bugs are either re-opened and become REOPENED, are marked
     VERIFIED, or are closed for good and marked CLOSED.
VERIFIED
     QA has looked at the bug and the resolution and agrees that the
     appropriate resolution has been taken. Bugs remain in this state
     until the product they were reported against actually ships, at
     which point they become CLOSED.
CLOSED
     The bug is considered dead, the resolution is correct. Any zombie
     bugs who choose to walk the earth again must do so by becoming
     REOPENED.

> Anyway, Dennis, how are you coming across these entries? Are you
> searching with everything selected in the STATUS list except CLOSED? If
> so I would just suggest excluding RESOLVED too. Certainly on the
> projects I'm aware of everyone just uses the "resolve bug" option in
> bugzilla [which presumably marks things as RESOLVED not CLOSED] then
> never looks at that entry again.

Actually I wasn't searching for these using a filter at all. When I was 
going through "Bug report for Commons [2005/07/25]", I was adding 
[component] in front of the ones that was missing it. When I looked at 
one of the issues at hand, it looked like it was "all done". So I 
checked the releasenotes for that commons component and indeed it had 
been both "resolved" and "shipped".

The reason for commenting on the issues was that they really shouldn't 
show up in the periodic "Bug report for Commons" e-mails. I figured they 
won't if they are closed.

Now I tried searching in bugzilla. You can specify Status 
[open|closed|all], Product and Words.

First try:
Status: open, Product: Commons and Words [beanutils]
Do *not* list the issues that I commented on

Second try:
Status: closed, Product: Commons and Words [beanutils]
Do list the issues that I commented on

So I now think that, from a bugzilla point of view, the issues can 
remain at their current status. But the "Bug report" e-mails, on the 
other hand, probably needs some tweaking.

--
Dennis Lundberg


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message