ARROW-7708: [Developer][Release] Include PARQUET issues in release changelogs by scraping git history #6722
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wrote logic in dev/release/changelog.py that does the following:
git log
$PROJECT-$key
strings to select from parquet-cpp issues returned by the JIRA APII updated the changelogs back to 0.12.0 which was the first major release (I think) after the monorepo merge was completed. It might be nice to also update the changelogs on the website