[
https://issues.apache.org/jira/browse/ARROW-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-8335.
---------------------------------
Fix Version/s: (was: 1.0.0)
0.17.0
Resolution: Fixed
Issue resolved by pull request 6836
[https://github.com/apache/arrow/pull/6836]
> [Release] Add crossbow jobs to run release verification
> -------------------------------------------------------
>
> Key: ARROW-8335
> URL: https://issues.apache.org/jira/browse/ARROW-8335
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Developer Tools
> Reporter: Neal Richardson
> Assignee: Neal Richardson
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.17.0
>
> Time Spent: 9h 50m
> Remaining Estimate: 0h
>
> Workflow: edit version number and rc number in template in
> {{dev/release/github.verify.yml}}, make PR, and do
> * {{@github-actions crossbow submit -g verify-rc}} to run everything
> * {{@github-actions crossbow submit -g verify-rc-wheel|source|binary}} to run
> those groups
> * Other groups at {{verify-rc-wheel|source-macos|ubuntu|windows}},
> {{verify-rc-source-cpp|csharp|java|etc.}}
> * Individual workflows at e.g. {{verify-rc-wheel-windows}},
> {{verify-rc-source-macos-csharp}}. We could break out the wheel verification
> by python version (maybe we should), but that requires changes to the
> verification scripts themselves.
> Running the main {{verify-rc}} group will put a ton of workflow svg badges on
> the PR so we can see at a glance what is passing and failing. If things fail
> when running all, can push fixes to the verification script to the branch and
> retry just those that failed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
