maemo.org Bugzilla – Bug 2365
resolution REMIND not documented
Last modified: 2008-08-11 14:09:06 UTC
You need to
before you can comment on or make changes to this bug.
There's a resolution REMIND in this bugzilla. It is not documented in
Without knowing what REMIND means, it's hard to tell if e.g. bug 737 is
actually going somewhere...
another option is to do away with that resolution, considering it's essentially
unused (4 bugs) https://bugs.maemo.org/buglist.cgi?resolution=REMIND
Jake, if you send me the updated fields.html.tmpl, I will move it to the
any news here? anybody having a patched fields.html.tmpl?
i would also like to see this resolution die.
("LATER" is also not clearly enough defined in my opinion, but that's a
Some thoughts to share:
- RESOLVED LATER can easily become a synonym for RESOLVED NEVER = WONTFIX.
- RESOLVED REMIND was thought for having a bug partially fixed. To me this
means that the bug has to remain open and the target milestone has to be
Both resolutions give wrong impressions to users. In fact the bugs are not
resolved; ergo they should not be in RESOLVED state. (One can also argue about
WONTFIX not being a resolved bug either, anyway.)
Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=178923#c75 for some
investigation by the Eclipse community on why to consider usage of LATER and
REMIND as deprecated and obsolete.
I would just dump LATER and REMIND.
Alternatively, I would resolve this bug as "REMIND LATER" ;)
Created an attachment (id=851) [details]
add descriptions for LATER and REMIND to fields.html
Just adding those lines:
<i>Usage is deprecated and obsolete</i>. Either keep the bug in its
open state or use WONTFIX instead.
<i>Usage is deprecated and obsolete</i>. Keep the bug in its state
and adjust the Target Milestone instead.
Fixed in SVN. Will be pushed to the live Bugzilla soon.