comphead commented on code in PR #14071:
URL: https://github.com/apache/datafusion/pull/14071#discussion_r1915282401


##########
README.md:
##########
@@ -146,3 +146,27 @@ stable API, we also improve the API over time. As a 
result, we typically
 deprecate methods before removing them, according to the [deprecation 
guidelines].
 
 [deprecation guidelines]: 
https://datafusion.apache.org/library-user-guide/api-health.html
+
+## Dependencies and a `Cargo.lock`
+
+`datafusion` is intended for use as a library and thus purposely does not have 
a
+`Cargo.lock` file checked in. You can read more about the distinction in the
+[Cargo book].
+
+CI tests always run against the latest compatible versions of all dependencies
+(the equivalent of doing `cargo update`), as suggested in the [Cargo CI guide]
+and we rely on Dependabot for other upgrades. This strategy has two problems
+that occasionally arise:
+
+2. CI failures when downstream libraries upgrade in some non compatible way
+3. Local development builds that fail when DataFusion inadvertently relies on

Review Comment:
   ```suggestion
   1. CI failures when downstream libraries upgrade in some non compatible way
   2. Local development builds that fail when DataFusion inadvertently relies on
   ```



-- 
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

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