On Mon, May 20, 2019 at 8:44 AM Andrew Purtell <[email protected]> wrote:
> This is fine in my opinion, based on similar past action taken by myself > and others and the reaction to them, and we appreciate the help and > attention to detail. > > I agree with all of above. > There are no documented guidelines as such but we have a number of issues > with no activity for months if not years and these are pretty obvious cases > in my opinion. I like to close them with one of the following resolutions, > depending: > > - Fixed: if the described issue is known fixed, and refer to where the > work was done. > > - Not A Problem or Invalid: if the issue in its preset state is nor > actionable and does not describe a testable condition. > > - Cannot Reproduce: if the issue describes a testable condition but > current code does not exhibit the problem; for example, an old report of a > failing unit test that is no longer failing. > > - Later: if the issue is a nice idea or a brainstorming issue that didn’t > go anywhere but might be worth revisiting someday > To be explicit, I think 'stale' issues can be closed with this designation. As to what is a 'stale' issue, how about an issue that has seen no action in a year? > > - Incomplete: a catch all resolution if work on the issue was started and > then abandoned. > Above list would make for a nice start on a when-to-close a JIRA in the dev section of refguide. Filed HBASE-22446 to get this and any other nuggest that come of this thread up into the refguide. Thanks, S > > > On May 20, 2019, at 4:59 AM, Clay Baenziger (BLOOMBERG/ 731 LEX) < > [email protected]> wrote: > > > > Hi HBase Devs, > > > > Could anyone clarify if it's okay to close incomplete/stale HBase JIRAs > (and if there is a hard line of a stale ticket) or if the community has had > any guidance on their handling? I closed the following JIRA tickets[1] and > realized I may be stepping on toes or be out of process. (But the clean-up > sure feels nice when trawling JIRA looking for active issues.) > > > > -Clay > > > > [1]: I closed: > > * HBASE-2502 - HBase won't bind to designated interface when more than > one network interface is available (Resolved/Works For Me) > > * HBASE-16077 - Replication status doesnt show failed RS metrics in CLI > (Resolved/Incomplete) >
