You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/07/28 13:05:40 UTC
DO NOT REPLY [Bug 15519] -
[beanutils] PropertyUtils.getPropertyType() for java.util.Collection
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?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Bugzilla RESOLVED vs CLOSED
Posted by Torsten Curdt <tc...@apache.org>.
>> 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.
>>
>
> Yes, but the thing is commons doesn't have a QA dept.
Usually I mark a bug as resolved and then ask
the initial submitter to verify and then close
the bug if it also works for him.
my 2 cents
--
Torsten
Re: Bugzilla RESOLVED vs CLOSED
Posted by Simon Kitching <sk...@apache.org>.
On Thu, 2005-07-28 at 14:16 +0200, Dennis Lundberg wrote:
> 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.
Yes, but the thing is commons doesn't have a QA dept.
> 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.
I believe there's a script that automatically does this. Certainly
emails regularly get posted to the dev list which just fix the subject
line, and they always come from one person [whose name I can't
remember]. If it's being done by hand they are very persistent...
> 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.
You are suggesting modifying the script that generates the "Bug report
for Commons" emails to ignore RESOLVED issues for commons? I would
definitely agree with that.
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Bugzilla RESOLVED vs CLOSED
Posted by Thomas Dudziak <to...@gmail.com>.
> 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.
FYI, the general concensus with the bug tracking software that I have
used (to name one example: the Apache Infrastructure JIRA) is that
once the developers think they have fixed the bug/implemented the
change, they set the bug/CR to RESOLVED. Then the person that made the
entry (for open source projects anyway) verifies that the bug is no
longer there/the change has been correctly implemented. He/she then
sets the status to VERIFIED (if supported by the bug tracking system)
or to some other status if the solution is not (yet) appropriate. If
the status is VERIFIED, the developers then can CLOSE the bug.
Likewise, for regressions, the bug than can be REOPENED etc.
This way, a large part of the release notes can be created fully
automatically by entering every bug, change request, improvement,
feature request into the bug tracking software (even if found and
immediately fixed by a developer).
regards,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Bugzilla RESOLVED vs CLOSED
Posted by Dennis Lundberg <de...@mdh.se>.
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
Bugzilla RESOLVED vs CLOSED
Posted by Simon Kitching <sk...@apache.org>.
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.
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.
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org