-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
WIP: [Release] Verify release-11.0.0-rc0 #33751
Conversation
@github-actions crossbow submit --group verify-rc-source --param release=11.0.0 --param rc=0 |
Revision: f10f5cf Submitted crossbow builds: ursacomputing/crossbow @ actions-7adb62faa2 |
Revision: f10f5cf Submitted crossbow builds: ursacomputing/crossbow @ release-11.0.0-rc0-0 |
I re-ran the failed source verification jobs on macOS arm64. |
Passed. |
@github-actions crossbow submit --group verify-rc-binaries --group verify-rc-wheels --param release=11.0.0 --param rc=0 |
Revision: f10f5cf Submitted crossbow builds: ursacomputing/crossbow @ actions-1f979c18ed |
The pytest seg fault is also happening in verification https://github.com/ursacomputing/crossbow/actions/runs/3954649758/jobs/6772203240#step:5:2810 |
@raulcd In general, we merge a RC branch to Because a RC may be rejected when a blocker is found. |
Hi @kou thanks for the clarification. I also found it strange but that's what appears on the release management guide in the instructions for sending the vote. https://arrow.apache.org/docs/dev/developers/release.html#verify-the-release I'll update the notes to remove the merge instructions before sending the vote. |
PR to verify Release Candidate