I could help out with the docs and take care of updating the maven artifacts. Hopefully that will take some load off.
Bryan On Thu, Oct 19, 2017 at 11:22 AM, Wes McKinney <wesmck...@gmail.com> wrote: > I would be fine with splitting up the work. For example, for the 0.8.0 > release perhaps another PMC can do the source release (to make sure we > have fully documented the system requirements necessary for cutting > the release tarball) and I can take care of updating the website, and > others can handle the documentation and binary package updates. > > Per https://issues.apache.org/jira/browse/ARROW-1349 we also should > provide Linux packages on the ASF BinTray. We have not done this yet > but since Kou has been doing a bunch of work already on Linux > packaging, we need some more help getting this across the finish line. > > Thanks > > On Thu, Oct 19, 2017 at 2:04 PM, Bryan Cutler <cutl...@gmail.com> wrote: > > Wes, thanks for taking on so much of the release management so far! I'd > be > > glad to help out with the next release. From the document you wrote, are > > you wanting someone to fully do the next release or would it work if we > > divide up some of the tasks? > > > > Bryan > > > > On Wed, Oct 18, 2017 at 6:06 PM, Wes McKinney <wesmck...@gmail.com> > wrote: > > > >> hi folks, > >> > >> I wrote up a document describing the work involved with an Arrow > release: > >> > >> https://github.com/apache/arrow/blob/master/dev/release/ > >> RELEASE_MANAGEMENT.md > >> > >> I've managed the last 7 releases -- I think it would be good for > >> others committers or PMC members to be exposed to the work involved > >> with an Arrow release so we can build some tools to assist with > >> automating routine matters. > >> > >> Since the release vote already takes 3 days, it would be good to get > >> to a point where we have all of the post-release tasks handled within > >> 48 hours of a release vote closing. In practice this has meant that I > >> lose anywhere from 4 to 10 hours of productive hours (i.e. a whole > >> working day) to doing this work. It is important for the growth of the > >> Arrow community that we release frequently and do not delay with > >> updating binary packages after the source artifacts are finalized. > >> > >> There are also a number of tasks, like updating the Python conda > >> packages, which do not require PMC / committer karma to help update, > >> so there's opportunities for other members of the community to earn > >> karma through non-code contributions helping update these packages. I > >> want to point out that these packages have each had over 100,000 > >> downloads since the project started > >> (https://anaconda.org/conda-forge/pyarrow) -- increasingly the rapid > >> deployment of new versions of our software will be important for the > >> health of the ecosystem. By their nature, the Arrow libraries will be > >> used as dependencies of other projects. > >> > >> thanks! > >> Wes > >> >
