IIUC the difference in the verification script is that we construct the
wheel file name, download it, and install the file, rather than have pip
query a repo and download the latest:
https://github.com/apache/arrow/blob/master/dev/release/verify-release-candidate-wheels.bat#L69-L72
Verification fa
Actually we are verifying the wheels after building them, the manylinux
wheels in fresh environments using docker.
We should first investigate why didn't the windows wheel issue surface
during its verification [1].
[1]:
https://github.com/apache/arrow/blob/master/dev/tasks/python-wheels/win-build
In terms of wheel verification, I added
https://issues.apache.org/jira/browse/ARROW-7853 to the 0.16.1 tag. It's
for CI using pip to install the wheels we build nightly. Obviously this is
not required for 0.16.1 but it would make the release verification simpler
because we would be running that log
It seems inevitable that a few annoying regressions will pop up as
0.16.0 becomes more widely deployed, e.g. ARROW-7841 was just reported
and patched. I created a 0.16.1 Fix Version in JIRA so that we can tag
issues that we may want to cherry pick into a maint-0.16.x branch. We
probably would want
