Skip to content
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

Add CI badges to Cargo.toml #953

Closed
Tracked by #950
kbknapp opened this issue May 9, 2017 · 2 comments
Closed
Tracked by #950

Add CI badges to Cargo.toml #953

kbknapp opened this issue May 9, 2017 · 2 comments
Labels
A-meta Area: administrative question or tracking issue E-medium Call for participation: Experience needed to fix: Medium / intermediate

Comments

@kbknapp
Copy link
Member

kbknapp commented May 9, 2017

Cargo.toml publishes CI badges for tier 1 platforms (C-CI)

The Rust compiler regards tier 1 platforms as "guaranteed to work."
Specifically they will each satisfy the following requirements:

Official binary releases are provided for the platform.
Automated testing is set up to run tests for the platform.
Landing changes to the rust-lang/rust repository's master branch is gated on
tests passing.
Documentation for how to use and how to build the platform is available.

Stable, high-profile crates should meet the same level of rigor when it comes to
tier 1. To prove it, Cargo.toml should publish CI badges.

[badges]
travis-ci = { repository = "..." }
appveyor = { repository = "..." }
@kbknapp kbknapp added A-meta Area: administrative question or tracking issue D: easy E-medium Call for participation: Experience needed to fix: Medium / intermediate labels May 9, 2017
@kbknapp kbknapp added this to the Lib Blitz Overhaul milestone May 9, 2017
@mgeisler
Copy link
Contributor

Fixed by 78498bd.

@kbknapp
Copy link
Member Author

kbknapp commented Jul 29, 2017

Thanks, forgot to close this 😉

@kbknapp kbknapp closed this as completed Jul 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: administrative question or tracking issue E-medium Call for participation: Experience needed to fix: Medium / intermediate
Projects
None yet
Development

No branches or pull requests

2 participants