-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Release] Vote email number of issues is querying JIRA and producing a wrong number #33782
Comments
GraphQL API is an option:
|
kou
pushed a commit
that referenced
this issue
Jan 24, 2023
…producing a wrong number (#33791) ### What changes are included in this PR? Release RC vote email now gets issue number and verify release PR's url from GitHub's GraphQL API. ### Are these changes tested? Changes were tested stand-alone from the rest of this script. ### Are there any user-facing changes? ARROW_GITHUB_API_TOKEN is now mandatory for generating the release vote email. * Closes: #33782 Authored-by: Rok Mihevc <rok@mihevc.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
vibhatha
pushed a commit
to vibhatha/arrow
that referenced
this issue
Jan 24, 2023
…A and producing a wrong number (apache#33791) ### What changes are included in this PR? Release RC vote email now gets issue number and verify release PR's url from GitHub's GraphQL API. ### Are these changes tested? Changes were tested stand-alone from the rest of this script. ### Are there any user-facing changes? ARROW_GITHUB_API_TOKEN is now mandatory for generating the release vote email. * Closes: apache#33782 Authored-by: Rok Mihevc <rok@mihevc.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
westonpace
pushed a commit
to westonpace/arrow
that referenced
this issue
Jan 25, 2023
…A and producing a wrong number (apache#33791) ### What changes are included in this PR? Release RC vote email now gets issue number and verify release PR's url from GitHub's GraphQL API. ### Are these changes tested? Changes were tested stand-alone from the rest of this script. ### Are there any user-facing changes? ARROW_GITHUB_API_TOKEN is now mandatory for generating the release vote email. * Closes: apache#33782 Authored-by: Rok Mihevc <rok@mihevc.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
sjperkins
pushed a commit
to sjperkins/arrow
that referenced
this issue
Feb 10, 2023
…A and producing a wrong number (apache#33791) ### What changes are included in this PR? Release RC vote email now gets issue number and verify release PR's url from GitHub's GraphQL API. ### Are these changes tested? Changes were tested stand-alone from the rest of this script. ### Are there any user-facing changes? ARROW_GITHUB_API_TOKEN is now mandatory for generating the release vote email. * Closes: apache#33782 Authored-by: Rok Mihevc <rok@mihevc.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
When generating the vote email for RC 0 on 11.0.0 I've realised that the vote email generated contains the following:
This number is extracted from:
This is wrong now, we should extract this from the GitHub milestone:
https://github.com/apache/arrow/milestone/1?closed=1
I've updated this manually for the current email vote but we should fix it on the
dev/release/02-source.sh
script.Component(s)
Release
The text was updated successfully, but these errors were encountered: