Yes, definitely. I'll create a packaging / arrow-dist automation umbrella JIRA and attach tasks to it
On Mon, Jul 24, 2017 at 4:17 PM, Jacques Nadeau <jacq...@apache.org> wrote: > Hey Wes, > > Does it make sense to create some jiras around this and then maybe some > people can pick them up? > > On Mon, Jul 24, 2017 at 7:55 AM, Wes McKinney <wesmck...@gmail.com> wrote: > >> We're accumulating more deployment targets and possible package >> artifacts from Arrow releases, such as: >> >> - Source tarball >> - Java JARs >> - Python wheels (for pip), 3 platforms >> - Python conda packages (for conda), 3 platforms >> - .deb/.rpm packages for C++, GLib C >> >> Doing all of this manually is a lot of work. Also, because many of the >> binary artifacts are being built post-release, they are not being >> voted on by the PMC and thus are "unofficial" packages. See >> http://arrow.apache.org/install/ >> >> Recently the apache/arrow-dist repo was created as a place where we >> can automate package builds, with uploads happening to a cloud bucket >> someplace: >> >> https://github.com/apache/arrow-dist >> >> Once we've set up the build scripts and various CI services, which >> should decide which packages we may want to include as part of a >> future release vote. >> >> Any help with packaging and distribution would be much appreciated. >> >> Thanks >> Wes >>
