To me, RESOLVED/LATER is more like the reviewer of the bug saying IGNORE/FORGET. If someone wishes to update a bug to reflect that - yes, this should be fixed, but there's no urgency in doing so - then you can simply lower the importance to P4/P5 and add relevant keywords (Vision) or custom tags (later). Anything is preferable to closing if the intent is to later do work on it.
RESOLVED/REMIND has a similar sort of iffiness to it.
To me, RESOLVED/LATER is more like the reviewer of the bug saying IGNORE/FORGET. If someone wishes to update a bug to reflect that - yes, this should be fixed, but there's no urgency in doing so - then you can simply lower the importance to P4/P5 and add relevant keywords (
Vision) or custom tags (later). Anything is preferable to closing if the intent is to later do work on it.RESOLVED/REMIND has a similar sort of iffiness to it.
Existing bugs under these status/resolution codes, I've looked at a couple, but didn't see any justified use of LATER or REMIND. https://issues.dlang.org/buglist.cgi?list_id=228816&bug_status=RESOLVED&resolution=REMIND https://issues.dlang.org/buglist.cgi?list_id=228817&bug_status=RESOLVED&resolution=LATER
As of writing, there are zero bugs with these status/resolution codes. https://issues.dlang.org/buglist.cgi?list_id=228819&bug_status=VERIFIED&resolution=LATER https://issues.dlang.org/buglist.cgi?list_id=228820&bug_status=VERIFIED&resolution=REMIND https://issues.dlang.org/buglist.cgi?list_id=228821&bug_status=CLOSED&resolution=LATER https://issues.dlang.org/buglist.cgi?list_id=228822&bug_status=CLOSED&resolution=REMIND