apacheGH-14918: [Docs] Make changes to developers section of the docs…

… (Jira -> GitHub) (apache#14919)

This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
apache#14822
* Closes: apache#14918

Lead-authored-by: Alenka Frim <frim.alenka@gmail.com>
Co-authored-by: Alenka Frim <AlenkaF@users.noreply.github.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

docs/source/developers/bug_reports.rst

@@ -27,26 +27,13 @@ and feature requests or commenting on existing issues. Even if you cannot
 contribute solutions to the issues yourself, your feedback helps us understand
 problems and prioritize work to improve the libraries.
 
-.. _apache-arrow-jira:
+.. _github_issues:
 
-Apache Arrow Jira
-=================
+GitHub issues
+=============
 
-The Arrow project uses `Jira <https://issues.apache.org/jira/projects/ARROW/issues>`_
-to track issues - both bug reports and feature requests. No account or
-permissions are required to view or search Jira issues. The Jira server
-hosts issue tracking for multiple Apache projects. The Jira project name for
-Arrow is "ARROW".
-
-.. _required-permissions:
-
-Required permissions
-++++++++++++++++++++
-
-Any registered Apache Software Foundation (ASF) Jira account may create or
-assign Jira issues in the Apache Arrow project without additional permissions.
-Individuals may
-`create an ASF Jira account here <https://issues.apache.org/jira/secure/Signup!default.jspa>`_.
+The Arrow project uses `GitHub issues <https://github.com/apache/arrow/issues>`_
+to track issues - both bug reports and feature requests.
 
 .. _creating-issues:
 
@@ -65,7 +52,7 @@ Check existing issues
 +++++++++++++++++++++
 
 Before you create a new issue, we recommend you first
-`search <https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved>`_
+`search <https://github.com/apache/arrow/issues>`_
 for unresolved existing issues identifying the same problem or feature request.
 
 .. _describe-issue:
@@ -186,9 +173,10 @@ Arrow is an expansive project supporting many languages and organized into a
 number of components. Identifying the affected component(s) helps new issues
 get attention from appropriate contributors.
 
-* Use the **Component** field to indicate the area of the project that your
-  issue pertains to (for example "Python" or "C++").
-* Also prefix the issue title with the component name in brackets, for example
+* **Component label**, which can be added by a committer of the Apache Arrow
+  project, is used to indicate the area of the project that your issue pertains
+  to (for example "Component: Python" or "Component: C++").
+* Prefix the issue title with the component name in brackets, for example
   ``[Python] issue summary`` ; this helps when navigating lists of open issues,
   and it also makes our changelogs more readable. Most prefixes are exactly the
   same as the **Component** name, with the following exceptions:
@@ -197,77 +185,32 @@ get attention from appropriate contributors.
   * **Component:** Developer Tools — **Summary prefix:** [Dev]
   * **Component:** Documentation — **Summary prefix:** [Docs]
 
-.. _affected-version:
-
-Identify affected version
-+++++++++++++++++++++++++
-
-If you're reporting something that used to work in a previous version
-but doesn't work in the current release, you can add the **Affects version**
-field to identify the earliest known version where the bug is observed.
-For feature requests and other proposals, leave **Affects version** empty as
-it is not applicable.
-
 .. _issue-lifecycle:
 
 Issue lifecycle
 ===============
 
-Both bug reports and feature requests follow a defined lifecycle. The issue
-**Status** field is used to document the current state of the issue, while the
-**Resolution** field indicates the outcome of issues that have reached
-terminal status. 
-
-
-.. _issue-status:
-
-Issue Status
-++++++++++++
-
-The Arrow project uses the following statuses in Jira to indicate what has -
-and will be - done on an issue:
-
-* **Open** - This is the initial issue state, prior to a contributor assigning
-  the issue and starting progress. Issues in this state should be unassigned.
-* **In progress** - At the time a contributor self-assigns an issue, the status
-  should be set to In progress by clicking the **Start progress** button. All
-  issues in this status should have an assignee - unassigned issues will be
-  set back to a status of Open. Issues remain "in progress" until resolved or
-  closed, including during review of pull requests.
-* **Resolved** - This is a terminal status indicating action has been taken
-  on the issue, which is now considered completed. Issues in a resolved status
-  should have a resolution code set to **Fixed**.
-* **Closed** - Another terminal status, Closed indicates the issue is complete,
-  but *without* action being taken. The following resolution codes apply to
-  issues in Closed status:
-
-  * Won't Fix
-  * Duplicate
-  * Invalid
-  * Incomplete
-  * Cannot Reproduce
-  * Not a Problem
-  * Not a Bug
-  * Workaround
-  * Information Provided
-  * Works for Me
-  * Won't Do
-  * Abandoned
-
-* **Reopened** - When an issue has been closed or resolved, but additional
-  attention is needed, it may be reopened.
+Both bug reports and feature requests follow a defined lifecycle. If an issue
+is currently worked on, it should have a developer assigned. When an issue has
+reached a terminal status, it is closed with one of two outcomes:
+
+* **Closed as completed** - indicates the issue is complete; the PR that
+  resolved the issue should have been automatically linked by GitHub
+  (assuming the PR correctly mentioned the issue number).
 
+  If you are merging a PR it is good practice to add a comment
+  to the linked issue about which PR is resolving it. This way
+  GitHub crates a notification for anybody that collaborated on
+  the issue.
+
+* **closed as not planned** - indicates the issue is closed and should
+  not receive any further updates, but *without* action being taken.
 
 .. _issue-assignment:
 
 Issue assignment
 ++++++++++++++++
 
 Assignment signals commitment to work on an issue, and contributors should
-self-assign issues when that work starts. At the same time the issue is
-assigned, the status field should be updated to **In Progress**.
-
-The Arrow project relies upon community contributors to resolve issues. We
-recognize that priorities and plans may change, resulting in an issue assigned
-to an individual who cannot attend to it. Assigned issues without updates in
-the past 90 days will be unassigned and set to **Open** status.
+self-assign issues when that work starts. Anyone can now self-assign issues
+by commenting ``take``.

docs/source/developers/continuous_integration/overview.rst

@@ -56,7 +56,7 @@ The ``.yml`` files in ``.github/worflows`` are workflows which are run on GitHub
   - ``@github-actions autotune`` - runs a number of stylers/formatters, builds some of the docs, and commits the results
   - ``@github-actions rebase`` - rebases the PR onto the master branch
 - ``dev.yml`` - runs any time there is activity on a PR, or a PR is merged; it runs the linter and tests that the PR can be merged
-- ``dev_pr.yml`` - runs any time a PR is opened or updated; checks the formatting of the PR title, adds links to the appropriate JIRA ticket if included in the title (or adds a comment requesting the user fix this if not), and adds any relevant GitHub labels
+- ``dev_pr.yml`` - runs any time a PR is opened or updated; checks the formatting of the PR title, adds assignee to the appropriate GitHub issue if needed (or adds a comment requesting the user to include the issue id in the title), and adds any relevant GitHub labels
 
 There are two other files which define action-triggered builds:
 

docs/source/developers/overview.rst

@@ -33,8 +33,8 @@ checklist for using ``git``:
   "upstream".
 * Keep your fork's **master branch synced** with ``upstream/master``.
 * **Develop on branches**, rather than your own "master" branch.
-* It does not matter what you call your branch. Some people like to use the JIRA
-  number as branch name, others use descriptive names.
+* It does not matter what you call your branch. Some people like to use the GitHub
+  issue number as branch name, others use descriptive names.
 * **Sync your branch** with ``upstream/master`` **regularly**, as many commits are
   merged to master every day.
 * It is recommended to use ``git rebase`` rather than ``git merge``.
@@ -97,9 +97,12 @@ Pull request and review
 When contributing a patch, use this list as a checklist of Apache Arrow workflow:
 
 * Submit the patch as a **GitHub pull request** against the **master branch**.
-* So that your pull request syncs with the JIRA issue, **prefix your pull request
-  name with the JIRA issue id** (ex:
-  `ARROW-767: [C++] Filesystem abstraction <https://github.com/apache/arrow/pull/4225>`_).
+* So that your pull request syncs with the GitHub issue, **prefix your pull request
+  title with the GitHub issue id** (ex:
+  `GH-14866: [C++] Remove internal GroupBy implementation <https://github.com/apache/arrow/pull/14867>`_).
+  Similarly **prefix your pull request name with the JIRA issue id** (ex:
+  `ARROW-767: [C++] Filesystem abstraction <https://github.com/apache/arrow/pull/4225>`_)
+  in case the issue is still located in Jira.
 * Give the pull request a **clear, brief description**: when the pull request is
   merged, this will be retained in the extended commit message.
 * Make sure that your code **passes the unit tests**. You can find instructions how
@@ -137,7 +140,7 @@ will merge the pull request. This is done with a
 
   A pull request is merged with a squash merge so that all of your commits will be
   registered as a single commit to the master branch; this simplifies the
-  connection between JIRA issues and commits, makes it easier to bisect
+  connection between GitHub issues and commits, makes it easier to bisect
   history to identify where changes were introduced, and helps us be able to
   cherry-pick individual patches onto a maintenance branch.
 

docs/source/python/getting_involved.rst

@@ -30,7 +30,7 @@ integrations in other projects, we'd be happy to have you involved:
   `dev-subscribe@arrow.apache.org <mailto:dev-subscribe@arrow.apache.org>`_.
   Share your ideas and use cases for the project or read through the
   `Archive <http://mail-archives.apache.org/mod_mbox/arrow-dev/>`_.
-* Follow our activity on `JIRA <https://issues.apache.org/jira/browse/ARROW>`_
+* Follow our activity on `GitHub <https://github.com/apache/arrow/issues>`_
 * Learn the `Format / Specification
   <https://github.com/apache/arrow/tree/master/format>`_