GitHub user alamb added a comment to the discussion: More thorough contribution guideline
We do have this guide for API stability (aka trying to reduce breaking changes) https://datafusion.apache.org/contributor-guide/api-health.html > Use 'cargo-semver-checks' to detect unintentional API breakages. Smallest > things can break APIs in ways we can not predict. > [Here](https://predr.ag/blog/semver-in-rust-tooling-breakage-and-edge-cases/) > is an article about this. This is a great idea. The other thing we have been trying to do more recently is test with downstream crates *before* we make a release, to catch regressions - https://github.com/apache/datafusion/issues/15072 - I agree that trying to do long lived feature branches is tough -- and something like https://github.com/apache/datafusion/issues/14444 will be especially tough as it it will generate many conflicts GitHub link: https://github.com/apache/datafusion/discussions/15365#discussioncomment-12607256 ---- This is an automatically sent email for github@datafusion.apache.org. To unsubscribe, please send an email to: github-unsubscr...@datafusion.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
