Re: New bug handling policy ?

I don't think this policy is very new. I've generally noticed that right =
before a major release people are eager to get rid of bugs. Maybe under =
Oracle developers are also evaluated with these metrics (number of =
open-bugs, etc) but I have no concrete information about this.

Harshness is also a matter of the person you are interacting with (and =
your own state of mind). For example, one might say David's reply was =
also a bit harsh although informative.

In my years of reporting bugs on NetBeans I've seen two things that =
annoy me to no end and they are not particularly new: leaving bugs =
untouched for a very long time and closing bugs as "works for me" when =
it's only been "fixed" in a nightly build.

That being said, closing an incomplete issue isn't a problem: you can =
always re-open the issue with more information.

As for moving to another category, that is something that I would expect =
to be done by the developers, if possible, especially given the fact =
that not all issue reporters know the internal design. One can also use =
the generic 'ide' category.

I guess examples could help to see what went wrong for your issues.

--emi

On Nov 12, 2012, at 6:08 PM, David Strupl wrote:

> Hello,
>=20
> the bug lifecycle is described here:
>=20
> http://wiki.netbeans.org/IssueLifeCycle
>=20
> Hope it helps explain at least a bit ...
>=20
> Br,
>=20
> David
>=20
> On 11/12/12 4:46 PM, [email protected] wrote:
>> I'm starting to wonder - is there a new policy or a metric on how =
bugs
>> are handled in bugzilla ? It seems that there is this eagerness from
>> the developers to close the issues as soon as they're created - even =
if
>> the issue is not confirmed, needs more information, etc. The other
>> aspect that's somewhat bothersome is developers closing an issue and
>> telling users that a new issue needs to be filed elsewhere to be =
looked
>> at - if it's obvious that something is an issue in the wrong =
category,
>> shouldn't the developer (who is familiar w/ the process of the issue
>> transitions and where the issue should really be) be the person who
>> creates the new issue, instead of closing the existing one and hoping
>> that a new issue wouldn't be created in the "proper" category ?
>>=20
>> I appreciate the quick response on issues - it's great to see that
>> someone is looking at issues soon after they're opened.  At the same
>> time, it feels a bit harsh when an issue I create is immediately
>> closed, even if it needs more information .
>>=20
>> Maybe I don't understand the states of issues in the netbeans =
bugzilla
>> and it's not a big deal when my issue is closed (e.g. when more
>> information is needed).  This seems like a recent development, but I
>> might be wrong.
>=20