GH-44934: [Dev] Remove JIRA remnants

[raulcd]

Rationale for this change

We are not using JIRA anymore in the project

What changes are included in this PR?

Remove JIRA from:

• documentation
• pr and issue templates
• comment bot
• merge script

Are these changes tested?

Via CI

Are there any user-facing changes?

No

• GitHub Issue: [Dev] Remove JIRA remnants #44934

[github-actions]

⚠️ GitHub issue #44934 has been automatically assigned in GitHub to PR creator.

[raulcd]

@kou @pitrou this only contains the developer tools updates (merge script, bot comments, pr templates and some minor docs). It does not contain the archery required changes but it's already slightly big. I think it would be better to split the archery changes on a different PR. If you are ok with that I'll create a new issue and would update descriptions accordingly.

[pitrou]

Did you forget to update https://github.com/apache/arrow/blob/main/dev/requirements_merge_arrow_pr.txt ?

[raulcd]

Did you forget to update https://github.com/apache/arrow/blob/main/dev/requirements_merge_arrow_pr.txt ?

yes, I forgot :)

[kou]

+1

Let's work on Archery as a separated task.

[raulcd]

I've created this issue to work on the archery changes:

• [Dev][Archery] Remove JIRA remnants from archery #44948

[assignUser]

@amoeba can you remove the mentions of jira in the release guide when you update it?

[amoeba]

Yep, I'll plan to get that release guide update in for the 19.0.0 release.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit fe32a7d.

There were 132 benchmark results with an error:

• Commit Run on arm64-t4g-2xlarge-linux at 2024-12-06 00:47:57Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-07, scale_factor=1
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-09, scale_factor=1
• and 130 more (see the report linked below)

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 20 possible false positives for unstable benchmarks that are known to sometimes produce them.