You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Karan Malhi <ka...@gmail.com> on 2008/08/03 03:03:24 UTC
jira issues
Was browsing through our JIRA issues. Some of them are pretty old and I dont
even think they are relevant any more. Whats the best way of closing an
issue. I was thinking maybe just commenting on an issue like "Should be
closed" and then waiting for a week or so (or whatever time) and let anybody
jump in and comment on the issue. If we hear no comments, we can safely
close it.
Please suggest better ways
--
Karan Singh Malhi
Re: jira issues
Posted by Mohammad Nour El-Din <no...@gmail.com>.
I think committers have the privileges to close issues. So all what
one need to do is to send a mail on the dev-list telling he is going
to close issue(s) and give a 72 hours - I think this is a common
Apache rule now - if no comments then close the issue(s).
On Sun, Aug 3, 2008 at 4:03 AM, Karan Malhi <ka...@gmail.com> wrote:
> Was browsing through our JIRA issues. Some of them are pretty old and I dont
> even think they are relevant any more. Whats the best way of closing an
> issue. I was thinking maybe just commenting on an issue like "Should be
> closed" and then waiting for a week or so (or whatever time) and let anybody
> jump in and comment on the issue. If we hear no comments, we can safely
> close it.
>
> Please suggest better ways
>
> --
> Karan Singh Malhi
>
--
Thanks
- Mohammad Nour