raulcd opened a new issue, #14720: URL: https://github.com/apache/arrow/issues/14720
### Describe the feature requested. As we are migrating from JIRA issues to GitHub issues and now that no new users can be created on JIRA we should modify the `merge_pr` script to be able to handle issues on GitHub. I am happy to work on a PR but there are some things that might need to be decided first. 1. How do we link issues with PRs? Currently we add the JIRA ticket id to the title of the PRs `ARROW-XXXX:`. Do we want to do the same with GitHub issues: `GH-XXXXX:` or do we want to have a mandatory `Closes XXXX` on the PR description so once the PR is merged the issue gets automatically closed? We have to define a way for either the merge script or the PR being merge to close the GitHub issue. 2. We need to add Labels to GitHub to identify the different components. Currently the GitHub merge_pr shows the identified components when merging, we should keep that functionality. 3. We should create the initial milestones so the merge_pr script is able to add, prompt the correct milestone when merging the PR. 4. Do we want to add assignee to the issue as we do with JIRA? The `merge_pr` script should continue working with JIRA as the `parquet CPP` project is not going to be move to GitHub as far as I understand. ### Component Developer Tools -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
