amoeba commented on issue #5368: URL: https://github.com/apache/arrow-rs/issues/5368#issuecomment-2121525541
This has been a really interesting and productive discussion. I wanted to add a few notes/questions: 1. As some of the people on this thread are probably aware, Apache Arrow [is discussing](https://lists.apache.org/thread/tvqns9d9z45mtpsqrngjyg083jdv8f1t) component versioning and releases on its developer mailing list and, as a result of that discussion, ADBC has started versioning its components independently while releasing a single source tarball for voting. It seems that approach could work here and may be a small piece of the puzzle for independently versioning sub-crates if that's still of interest at some point in the future. 2. A recurring theme in this discussion has been considering the impact of any changes on maintainer bandwidth. It seems like adopting something like [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) could address a number of issues here and could be paired with automations that reduce maintainer burden. @wjones127 has been doing some [work](https://github.com/lancedb/lancedb/pull/1294/files) in this area recently for Lance(DB) and the notion has come up again for the Arrow monorepo too. Is there any interest in opening an issue to discuss this and related automations? 3. @mbrobbel brought up https://docs.rs/tokio/latest/tokio/#unstable-features which I see as a way to make it easier to reason about what types changes constitute breaking changes which could reduce maintainer burden. Is this worth pulling out into its own issue? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
