You didn't mention it specifically but one big thing I'd like to get into the next release is prepackaged flight tools for c++, java and python.
As far as 1.0, I think its time and would vote for naming the next release 1.0. Thanks for bringing this up! On Fri, Jun 7, 2019 at 8:43 AM Wes McKinney <wesmck...@gmail.com> wrote: > hi folks, > > Our last release 0.13.0 occurred at the end of March. I think it would > be good to plot a course for the next release (0.14.0?) as soon as > possible. There are still a number of issues (such as the shared > library duplication issue in the Python wheels) that I think might > discourage us from releasing right now. Do you think that pushing for > a release candidate by the end of June is reasonable? > > As a second matter (and this can be split off into a separate > discussion thread), the Arrow format and binary protocol has been > stable effectively since the 0.8.0 release which occurred in December > 2017. While we have some details yet to iron out in compatibility > testing between implementations (for example, the Union question, see > mailing list discussion [1]) and new features (e.g. 64-bit offset > binary/string/list types), in theory these should not prevent us > necessarily from making a declaration of protocol stability. I think > this would have a lot of benefits for project onlookers to remove > various warnings around the codebase around stability and cautions > against persistence of protocol data. It's fair to say that if we _do_ > make changes in the future, that there will be a transition path for > migrate persisted data, should it ever come to that. > > I would suggest a "1.0.0" release either as our next release (instead > of 0.14.0) or the release right after that (if we need more time to > get affairs in order), with the guidance for users of: > > PROTOCOL VERSION (1): Protocol version, so libraries bearing 1.x.y > will be forward and backwards compatible (though new metadata fields > introduced in newer versions will be dropped in older readers) > MAJOR VERSION (0): API changes possible (and indeed, likely) from > major release to major release > MINOR VERSION (0): No API changes, bug fix only release > > Thoughts on the above? > > Thanks > Wes > > [1]: > https://lists.apache.org/thread.html/e54e8ec096f665a8aef94155de3b6c567258c0d15209de4b966dd8da@%3Cdev.arrow.apache.org%3E >
