raulcd commented on issue #43536: URL: https://github.com/apache/arrow/issues/43536#issuecomment-2290956956
At the moment all our merge (closes issues automatically) and release scripts (generation of release notes, cherry picking) expect one issue per PR. This was a requirement for JIRA but now that we are tracking issues on GH I think we can revisit that pattern, we could even avoid some issues and just use PRs for some things but this would require some time to adapt our current scripts. As per this particular issue, the biggest potential problems for the release: - As you have already seen the issue will keep getting closed every time we merge a subtask. - PRs merged pointing to this PR will probably not appear on the release notes (as far as I know release notes are generated from issues tagged with the correct milestone not PRs) - If we merge something after the feature freeze it won't get cherry-picked by our scripts To be honest not really breaking issues for the release but if this is a workflow we want to use (which I think we should) we should adapt our scripts. I am currently on vacation so might take some time responding. -- 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]
