-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Declare support level for each crate in our Charter / docs #14600
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
> This crate is maintained by the Cargo team, primarily for use by Cargo | ||
> and not intended for external use. This | ||
> crate may make major changes to its APIs or be deprecated without warning. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
> This crate is maintained by the Cargo team for use by the wider | ||
> ecosystem. This crate follows semver compatibility for its APIs. | ||
Comment on lines
+1
to
+2
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm on the fence here. My intention when I created it was to be more "internal". I was thinking that if others found it useful, we could expand that to a more "experimental" status. I didn't know if anyone would actually have a use for it, and it wasn't really something I wanted to put effort into. Also, as evident by the lack of a README, this isn't really up to my standards for an intentional artifact that we intend to support. It looks like it has a few dependents now, though: https://crates.io/crates/cargo-platform/reverse_dependencies. I'm fine with elevating this to be "intentional" if ya'll agree. It has required almost no maintenance effort, and I don't expect us to delete it, and we already have semver checks. I just wanted to make clear what I was originally thinking. (We probably should eventually add a real README, though 🤣) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the clarification! I think its reasonable for the Rust Project to provide an API for this micro-DSL. My main concern is what shape any of that should take and thats where I feel like the commitment of "Intentional" is strong. Granted, the definition of "Intentional" is strong enough I'm hesitant to mark anything intentional but anything else would also be too weak / scare people away. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,3 @@ | ||
WARNING: You might not want to use this outside of Cargo. | ||
|
||
* This is designed for testing Cargo itself. Use at your own risk. | ||
* No guarantee on any stability across versions. | ||
* No feature request would be accepted unless proved useful for testing Cargo. | ||
> This crate is maintained by the Cargo team, primarily for use by Cargo | ||
> and not intended for external use. This | ||
> crate may make major changes to its APIs or be deprecated without warning. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,3 @@ | ||
WARNING: You might not want to use this outside of Cargo. | ||
|
||
* This is designed for testing Cargo itself. Use at your own risk. | ||
* No guarantee on any stability across versions. | ||
* No feature request would be accepted unless proved useful for testing Cargo. | ||
> This crate is maintained by the Cargo team, primarily for use by Cargo | ||
> and not intended for external use. This | ||
> crate may make major changes to its APIs or be deprecated without warning. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
> This crate is maintained by the Cargo team for use by the wider | ||
> ecosystem. This crate follows semver compatibility for its APIs. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
> This crate is maintained by the Cargo team, primarily for use by Cargo | ||
> and not intended for external use (except as a transitive dependency). This | ||
> crate may make major changes to its APIs or be deprecated without warning. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
> This crate is maintained by the Cargo team for use by the wider | ||
> ecosystem. This crate follows semver compatibility for its APIs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is already mentioned in the "Installing Cargo" section.
Should we move "For all other uses of this crate..." to under "Compiling from Source"? Something like
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That section heavily implies "building the binary from source" and doesn't really cover the "depending on it as a library" case.
I feel like a lot of this should be re-worked, mostly by moving in to the contributor guide. I recommend we remove the install instructions and defer re-working the compilation instructions.