From 9d56569774aa23818065f262d4575fea7f59f06a Mon Sep 17 00:00:00 2001 From: Joris Van den Bossche Date: Fri, 13 Sep 2024 02:17:47 +0200 Subject: [PATCH] MINOR: [Docs] Remove mention of JIRA issues in the contributing PR checklist (#44091) ### Rationale for this change We no longer have any remaining JIRA issues, so this sentence can be removed. Authored-by: Joris Van den Bossche Signed-off-by: Sutou Kouhei --- docs/source/developers/overview.rst | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/source/developers/overview.rst b/docs/source/developers/overview.rst index 5a18b1e4eb8db..7e38dcb8ebc85 100644 --- a/docs/source/developers/overview.rst +++ b/docs/source/developers/overview.rst @@ -100,9 +100,6 @@ When contributing a patch, use this list as a checklist of Apache Arrow workflow * 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 `_). - Similarly **prefix your pull request name with the JIRA issue id** (ex: - `ARROW-767: [C++] Filesystem abstraction `_) - 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