Probably just an old habit from Lucene... I usually mark things as
resolved and then close them later if no issues come up. It allows
others to chime in if they want. Of course, there is zero cost for
reopening in Open Source so it's not a big deal. Especially for minor
issues, no big deal.
On Jun 17, 2009, at 6:03 AM, Robert Burrell Donkin wrote:
grant committed the patch in
https://issues.apache.org/jira/browse/MAHOUT-134 (thanks :-) and set
the issue to resolved but not closed
am i right in thinking that mahout is using the convention that the
reporter of the issue should check that the committed code works ok
then close the issue...?
(or is there some other convention at work here...)
- robert
