Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 24 Jun 2017 06:53:00 +0000 (UTC)
From: "Chia-Ping Tsai (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12764398.1420043426000.97331.1498287180894@Atlassian.JIRA>
In-Reply-To: <JIRA.12764398.1420043426000@Atlassian.JIRA>
References: <JIRA.12764398.1420043426000@Atlassian.JIRA> <JIRA.12764398.1420043426080@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-12794) Guidelines for filing JIRA issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 24 Jun 2017 06:53:07 -0000


    [ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061833#comment-16061833 ] 

Chia-Ping Tsai commented on HBASE-12794:
----------------------------------------

{quote}
+** What happens or doesn't happen
+** How does it impact you
+** How can someone else reproduce it
+** What would "fixed" look like?
{quote}
Consider adding the question mark for each line.

> Guidelines for filing JIRA issues
> ---------------------------------
>
>                 Key: HBASE-12794
>                 URL: https://issues.apache.org/jira/browse/HBASE-12794
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.0.0-alpha-1
>            Reporter: stack
>            Assignee: Misty Stanley-Jones
>             Fix For: 2.0.0
>
>         Attachments: HBASE-12794.patch
>
>
> Following on from Andrew's JIRA year-end cleaning spree, lets get some guidelines on filing issues e.g. fill out all pertinent fields, add context and provenance, add value (i.e. triage), don't file issues that are nought but repeat of info available elsewhere (build box or mailing list), be reluctant filing issues that don't have a resource behind them, don't file issues on behalf of others, don't split fixes across multiple issues (because there are poor folks coming behind us trying to backport our mess and piecemeal makes their jobs harder), and so on.
> The guidelines are not meant to put a chill on the opening of issues when problems are found, especially not for new contributors. They are more meant for quoting to veteran contributors who continue to file issues in violation of what was thought a common understanding; rather than explain each time why an issue has been marked invalid, it would be better if we can quote chapter and verse from the refguide.
> Dump any suggestion in here and I'll wind them up as a patch that I'll run by dev mailing list to get consensus before committing.
> Here is a running google doc if you'd like to add comment: https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)