One addition to this: If the bug was *repeatable* before, and you can still
(because the UI hasn't changed too much) repeat the same steps but *not*
see it now, mark the bug as *FIXED*, not WORKSFORME/INVALID. Clearly, the
bug used to happen and isn't happening any more, so we FIXED it at some
point, even if we don't know when it was.
McQ.
From: John Arthorne/Ottawa/IBM@IBMCA
To: "Eclipse platform general developers list."
<[email protected]>
Date: 2014/06/26 10:23 AM
Subject: Re: [platform-dev] What to do with old issues?
Sent by: [email protected]
Absolutely, any bug that is no longer reproducible please feel free to
close as either WORKSFORME or INVALID. There is no need to set a target
milestone (that is only needed for FIXED bugs). That kind of triage is very
helpful since there are many thousand old bugs and only so many active
contributors to look at them.
John
From: Mickael Istria <[email protected]>
To: [email protected],
Date: 06/26/2014 10:15 AM
Subject: [platform-dev] What to do with old issues?
Sent by: [email protected]
Hi all,
I've spent some time on the history of Platform-UI component looking at
some old bugs (with id < 100000) that were reported against 3.0. Many of
those reports are not accurate any more, because the suggested improvements
or bugs were fixed later but not tracked in those old requests.
What should we do with such issues? Closing as WORKSFORME, INVALID? Should
we set a Target Milestone then? If yes, which one (next milestone) ? ...
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
platform-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/platform-dev
