Community
Participate
Working Groups
While http://www.eclipse.org/projects/dev_process/bugzilla-use.php gives a clue of the effect to which some projects use the WONTFIX status, https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#status, which provides an otherwise neat recapitulative table of bugs status, does not mention WONTFIX at all. This confuses some users (see comment #9 of bug 154984), the RESOLVED part of 'RESOLVED REMIND' making them believe that we don't want to investigate further (while we ask them to help us investigate further).
Frédéric points out to me that I mistakenly used WONTFIX instead of REMIND... Apologies to all, and thx to Fred. While http://www.eclipse.org/projects/dev_process/bugzilla-use.php gives a clue of the effect to which some projects use the 'RESOLVED REMIND' status, https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#status, which provides an otherwise neat recapitulative table of bugs status, does not mention REMIND at all. This confuses some users (see comment #9 of bug 154984), the RESOLVED part of 'RESOLVED REMIND' making them believe that we don't want to investigate further (while we ask them to help us investigate further).
Interesting. New bugzilla installations >= 3.0 (not yet released) won't have RESOLVED/LATER and RESOLVED/REMIND, as they are considered "bad": https://bugzilla.mozilla.org/show_bug.cgi?id=13534 Also, this implemented feature will allow us to customize the resolutions: https://bugzilla.mozilla.org/show_bug.cgi?id=94534 I think we'll eventually lose RESOLVE/REMIND and maybe RESOLVE/LATER.
Then we'll need to fix our processes. Copying Philippe to that effect.
(In reply to comment #3) > Then we'll need to fix our processes. Copying Philippe to that effect. > I suggest you wait before changing any processes. I believe that Bugzilla 3.0, when released, will allow us to customize the statuses and the resolutions. What I'd suggest we do, when the time comes, is that we revist the Bugzilla workflow and adjust our statuses/resolutions accordingly. I'm simply documenting the Mozilla bugs here for completeness. This bug is also related to bug 157642. In the interim, I agree that we can define REMIND on our pages... But that definition may vary from one project to the next. Any suggestions?
Reassigning to community/bugzilla
Personally, I have always believed the Target Milestone field was more appropriate for LATER than the Resolution field (like suggested in the mozilla.org bug).
I've added descriptions of those resolutions to https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#status
Denis, LATER and REMIND are deprecated for sure (after some debate, to say the least). But I thought that we as a community agreed that the teams had some time to adjust - more precisely, that we would not have to dig for bugs matching those until 3.3 is released. The description you posted is improved in the sense it is more exhaustive, citing the formerly missing status, but I do not quite see the benefit to the user, since it gives her no clue what the meaning of the status could be. Would it be possible to add more information, along the following lines: - Some projects/teams used to move peculiar bugs to RESOLVED REMIND instead of marking them with the needinfo keyword (which means asking more information from the reporter) or decreasing their priority (which means postponing work in favor of other bugs). Such bugs are not considered as resolved. - Some projects/teams used to move peculiar bugs to RESOLVED LATER instead of decreasing their priority. Such bugs are not considered as resolved.
I wasn't quite sure what teams were using them for, so thanks for the verbiage. I've updated the page.
Thanks a lot.
