The timeline for the 0.13 release is drawing closer. I would say we should consider a release candidate either the week of March 18 or March 25, which gives us ~3 weeks to close out backlog items.
There are around 220 issues open or in-progress in https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.13.0+Release Please have a look. If issues are not assigned to someone as the next couple of weeks pass by I'll begin moving at least C++ and Python issues to 0.14 that don't seem like they're going to get done for 0.13. If development stakeholders for C#, Java, Rust, Ruby, and other components can review and curate the issues that would be helpful. You can help keep the JIRA issues tidy by making sure to add Fix Version to issues and to make sure to add a Component so that issues are properly categorized in the release notes. Thanks Wes On Sat, Feb 9, 2019 at 10:39 AM Wes McKinney <wesmck...@gmail.com> wrote: > > See https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide > > The source release step is one of the places where problems occur. > > On Sat, Feb 9, 2019, 10:33 AM <ane...@quiltdata.io wrote: >> >> >> > On Feb 8, 2019, at 9:19 AM, Uwe L. Korn <m...@uwekorn.com> wrote: >> > >> > We could dockerize some of the release steps to ensure that they run in >> > the same environment. >> >> I may be able to help with said Dockerization. If not for this release, then >> for the next. Are there docs on which systems we wish to target and/or any >> build steps beyond the current dev container >> (https://github.com/apache/arrow/tree/master/dev/container)?
