[GitHub] [arrow-rs] tustvold edited a comment on issue #1120: More frequent major releases for arrow-rs

[GitBox <gi...@apache.org>]

tustvold edited a comment on issue #1120:
URL: https://github.com/apache/arrow-rs/issues/1120#issuecomment-1005421434


   I wonder if we might further simplify matters by releasing weekly and incrementing the version based on if there are any new breaking changes on master since the last release. The major benefit would be this could be completely automated, potentially using existing tooling.
   
   In the past I've used this approach for binaries, in particular using goreleaser, but I see no obvious reason something similar couldn't be done here...
   
   Edit: a somewhat related question is must all the crates in this repo advance their version numbers in lockstep? Should a breaking release to parquet mandate a breaking semver bump to arrow?


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org