hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12794) Guidelines for filing JIRA issues
Date Thu, 01 Jan 2015 18:12:13 GMT

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

Andrew Purtell commented on HBASE-12794:

I think it may be useful to start with general guidelines and then also differentiate a bit
on issue type. We should be pretty strict about Bugs and Test issues being actionable with
a resource behind them, for example, yet encourage creative and aspirational thinking for
New Feature, Improvement, and Wish types. The former would describe our current work, the
latter would be a public backlog. 

> Guidelines for filing JIRA issues
> ---------------------------------
>                 Key: HBASE-12794
>                 URL: https://issues.apache.org/jira/browse/HBASE-12794
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>            Reporter: stack
>            Assignee: stack
> 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

View raw message