You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by we...@apache.org on 2019/06/13 18:40:22 UTC

[arrow] branch master updated: ARROW-5526: [GitHub] Add more prominent notice to ISSUE_TEMPLATE.md to direct bug reports to JIRA

This is an automated email from the ASF dual-hosted git repository.

wesm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow.git


The following commit(s) were added to refs/heads/master by this push:
     new 740e729  ARROW-5526: [GitHub] Add more prominent notice to ISSUE_TEMPLATE.md to direct bug reports to JIRA
740e729 is described below

commit 740e7293c885a96d4a79637d0e984422f2b3fe64
Author: Wes McKinney <we...@apache.org>
AuthorDate: Thu Jun 13 13:40:14 2019 -0500

    ARROW-5526: [GitHub] Add more prominent notice to ISSUE_TEMPLATE.md to direct bug reports to JIRA
    
    This will hopefully help grab the attention of issue reporters to direct them to JIRA better than the current text.
    
    Author: Wes McKinney <we...@apache.org>
    
    Closes #4536 from wesm/ARROW-5526 and squashes the following commits:
    
    378e15990 <Wes McKinney> Respond to feedback, rewrite second part a bit to be more clear about expectation to use mailing lists for non-issue reports
    a397cd392 <Wes McKinney> Add more prominent notice to ISSUE_TEMPLATE.md to direct bug reports to JIRA
---
 .github/ISSUE_TEMPLATE.md | 31 ++++++++++++++++++-------------
 1 file changed, 18 insertions(+), 13 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index b7962a1..b42784b 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -1,16 +1,21 @@
-## GitHub Issues for Apache Arrow
+STOP! Are you reporting a bug, a possible bug, or requesting a
+feature? If so, please report under the ARROW project on the ASF JIRA
+server https://issues.apache.org/jira/browse/ARROW. This JIRA server
+is free to use and open to the public, but you must create an account
+if it is your first time.
 
-We support GitHub issues as a lightweight way to ask questions and engage with
-the Arrow developer community. We use the Apache Software Foundation's JIRA
-instance for maintaining a queue of development work and as the public record
-for work on the project. So, feel free to delete this text and open an issue
-here if you have a question or aren't sure whether something is a bug or
-feature request. Any bugs, suggestions, or feature requests will eventually
-need to end up in JIRA (https://issues.apache.org/jira/browse/ARROW),
-either before or after completing a pull request.
+See our contribution guidelines for more information:
+http://arrow.apache.org/docs/developers/contributing.html
 
-See our contribution guidelines for more information: http://arrow.apache.org/docs/developers/contributing.html
+We have GitHub issues available as a way for new contributors and
+passers-by who are unfamiliar with Apache Software Foundation projects
+to ask questions and interact with the project. Do not be surprised if
+the first response is to open a JIRA issue or to write an e-mail to
+one of the public mailing lists:
 
-For more in-depth development discussions, please use the public mailing list
-dev@arrow.apache.org (first subscribe by sending an e-mail to
-dev-subscribe@arrow.apache.org).
+* Development discussions: dev@arrow.apache.org (first subscribe by
+  sending an e-mail to dev-subscribe@arrow.apache.org).
+* User discussions: user@arrow.apache.org (first subscribe by
+  sending an e-mail to user-subscribe@arrow.apache.org).
+
+Thank you!
\ No newline at end of file