logan-keede opened a new issue, #15408:
URL: https://github.com/apache/datafusion/issues/15408

   ### Is your feature request related to a problem or challenge?
   
   DataFusion is a rapidly evolving codebase. With many minor and major changes 
every week, through this all we try to minimise unnecessary API changes/breaks 
as much as possible but every change has the possibility of causing API changes 
in ways we can not predict. 
[Here](https://predr.ag/blog/semver-in-rust-tooling-breakage-and-edge-cases/) 
is a nice article about this.
   
   ### Describe the solution you'd like
   
   `cargo-semver-checks` is a cargo tool made for specific purpose of 
automatically identifying API changes (and avoid breaking Semantic Versioning, 
not that relevant for us as we have pretty much only major release every 
month.).
   Its general usage is explained in above mentioned article.
   We can use this tool in a CI to check if a particular PR/merge has broken 
any API or not.
   Note: (IMO)This CI check is not supposed to be a blocker but a way to avoid 
uninformed API changes.
   
   ### Describe alternatives you've considered
   
   Search for other similar tools or continue to predict API changes without 
any tool.
   
   ### Additional context
   
   Discussion: _[More thorough contribution 
guideline.](https://github.com/apache/datafusion/discussions/15365)_
   Article: _[SemVer in Rust: Tooling, Breakage, and Edge 
Cases](https://predr.ag/blog/semver-in-rust-tooling-breakage-and-edge-cases/)_


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

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org

Reply via email to