Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # dev >> RESOLVED vs CLOSED


Copy link to this message
-
Re: RESOLVED vs CLOSED
I'd say we should probably close any issue that has stayed resolved for
1+ months.

On 04/04/2013 12:45 PM, Israel Ekpo wrote:
> Team,
>
> I have noticed some issues are in RESOLVED state and others are in CLOSED
> state.
>
> I wanted to find out when we can use RESOLVED and when we can used CLOSED
> for the status of an issue.
>
> For instance, some issues have been marked as resolved for 12 months or
> longer.
>
> https://issues.apache.org/jira/browse/FLUME-1015
> https://issues.apache.org/jira/browse/FLUME-215
> https://issues.apache.org/jira/browse/FLUME-694
>
> A quick lookup on these JIRA statuses suggest that:
>
> *RESOLVED*
> Implies that a resolution has been taken, and it is awaiting verification
> by reporter. From here issues are either reopened, or are closed.
>
> *CLOSED*
> Implies that the issue is considered finished, the resolution is correct.
> Issues which are closed can be reopened.
>
> I think we should go over some of the issues that are marked as RESOLVED to
> see if thier status should be set to CLOSED.
>
> Here are some 800+ issues in RESOLVED state
>
> http://bit.ly/XYZ3Vz
>
> It looks like RESOLVED is not the final state these issue should be. If the
> reporter believes that the issue has been addressed satisfactorily, it
> should be marked as CLOSED.
>
> Any thoughts?
>