alamb opened a new issue, #2327: URL: https://github.com/apache/arrow-datafusion/issues/2327
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** DataFusion's mission statement is to be "easy to embed" from https://arrow.apache.org/datafusion/user-guide/introduction.html#why-datafusion Within the rust ecosystem, publishing to crates.io is a key way to make something easy to embed (other projects can then use it with a single line of `toml`). However, we have been releasing about once every three months, which limits the speed at which we can publish new features to crates. io for use in downstream projects The most active projects of the users today of datafuson use a fork or work off the master branch directly (see presentation linked in #2323). **Describe the solution you'd like** It would be awesome to release DataFusion more frequently, perhaps in a semver compatible way, to encourage more community use. For example, as suggested by @martinitus https://github.com/apache/arrow-datafusion/issues/37#issuecomment-1106605474 when there is a new major version of arrow-rs: > I think general best practice (given you use semver) is that if you have a major increase in a dependency that appears in your public API, then you also need a major increase in your library version, as the stuff that appear in your public API may break backwards compatibility for the users of your API. **Describe alternatives you've considered** Keep with the current approximately quarterly release schedule, at least until the APIs have stabilized more. **Additional context** Managing regular releases is a substantial undertaking: 1. Managing the actual release process requires significant time 2. Managing what code changes can go where and still maintain semver is non trivial (e.g. backporting 'semver' compatible changes -- see discussion on https://github.com/apache/arrow-rs/issues/1120 for some flavor). We (I) abandoned doing this in arrow-rs due to lack of time. I don't personally have the bandwidth at this time to organize / manage this process; However, I wanted to get it on our collective radar, and I would be happy to help guide and support anyone who wants to invest the time making this happen for the community -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
