[Packaging] Tooling to make nightly wheels available for install

[asfimport]

Reporter: Wes McKinney / @wesm
Assignee: Krisztian Szucs / @kszucs

PRs and other links:

• GitHub Pull Request #6366

_{Note: This issue was originally created as ARROW-1581. Please see the migration documentation for further details.}

[asfimport]

Robert Nishihara / @robertnishihara:
Are you planning on putting these on PyPI? I'd like to do something similar with Ray, ideally people would be able to pip install the project from any commit. Sort of like https://pypi.python.org/pypi/tf-nightly except with every commit, not just the most recent.

[asfimport]

Wes McKinney / @wesm:
I don't see why not to put them on PyPI as long as the Apache project does not advertise them. It might be a little work to munge the package metadata to do this. I have already found having the conda nightlies to be incredibly useful

[asfimport]

Uwe Korn / @xhochy:
@wesm What would be the problems with package metadata here? setuptools_scm should take care of providing a continuous version number suitable for nightly builds.

[asfimport]

Krisztian Szucs / @kszucs:
After merging #2162 and setting this branch to master the nightlies will be uploaded to github releases.

[asfimport]

Wes McKinney / @wesm:
So I have to object a little bit to resolving this issue as there's no visibility into these builds. If someone wanted to start using them, how would they do that? I know that @robertnishihara @pcmoritz and others would make use of these for development

[asfimport]

Wes McKinney / @wesm:
Reopening until we figure out the developer workflow for using the nightly builds, and document it on https://cwiki.apache.org/confluence/display/ARROW

[asfimport]

Krisztian Szucs / @kszucs:
What is the desired user flow here? Listing nightly wheel artifacts on a web page? And having a latest link to download the most recent wheel?

[asfimport]

Krisztian Szucs / @kszucs:
Issue resolved by pull request 6366
#6366