-
Notifications
You must be signed in to change notification settings - Fork 2.7k
adding policies page to the docs #3057
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
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
Thanks @rjgoldsborough . Two quick questions:
|
|
Yeah, I just straight copied all that text so it might need some updating. But sure. Whatever works for you. Just excited to dive in. :) And honestly, I'm not sure why that got added heh. It came with the build so I left it. |
|
Sent! |
|
Also, /cc @rust-lang/core , given that this is no longer the literal text of the old post. I've mostly
|
tweak policies
| Many questions are specialized instances of a more general form: “Under what | ||
| circumstances can a package be removed from Crates.io?” | ||
|
|
||
| The short version is that packages are first-come, first-served, and we won’t |
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.
"served"
|
@steveklabnik looks good to me! |
|
LGTM |
|
@bors: r+ rollup thanks! Sorry for the latency here, it's been a busy month! |
|
📌 Commit a26732c has been approved by |
adding policies page to the docs Fixes #3056
|
Yeah for sure, and no problem! |
|
And thank y'all! |
|
💔 Test failed - cargo-win-msvc-64 |
|
@bors: retry On Tue, Sep 27, 2016 at 6:14 PM, bors [email protected] wrote:
|
|
⚡ Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-msvc-32 are reusable. Rebuilding only cargo-cross-linux, cargo-win-gnu-64, cargo-win-msvc-64... |
|
☀️ Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
Fixes #3056