Hi Aparna,
Ok, sounds like "works for me" is indeed the right resolution for these
bugs. One thing for devs to keep in mind as they resolve bugs this way
-- if the person who logged the bug is new to the community, it might be
worth explaining that "works for me" does not mean that the bug is
forgotten or lost information.
Cheers,
Katie
Aparna Kadakia wrote:
Secondly regarding the 'works for me' resolution, the QA team does look
at each 'works for me' bug seriously and we do validate it before
closing it out. So as far as the end users are concerned they need not
worry about their bugs slipping thru the cracks. Even though it may be
resolved as 'worksforme', if we have even one instance where it fails we
will work with the developer and the user on providing exact steps for
reproducing the problem and resolving it.
...
On Dec 28, 2006, at 12:10 PM, Philippe Bossut wrote:
I think it's the right resolution. I know it can be frustrating but
the alternative (leaving the bug open and dangling with no clear
action) is no better. No one should take the resolution personally (we
*are* grateful for the report). The wording of the resolution doesn't
mean more than what it says ("works for the developer/tester"). At
least, it shows that a fair attempt at reproducing the bug has been
made and nothing prevents the discussion to continue between devs and
users (on the afore mentioned mailing list) and the bug to be reopen
if a new info shows up. It's also good to have a record so that the
bug and attempt to repro can be searched and consulted by others with
similar issues.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev