Skip to content

Commit 4efba52

Browse files
committed
update links in reviewer checklist
1 parent 3931fb4 commit 4efba52

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

.travis.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ cache:
88
- book/linkcheck/
99
before_install:
1010
- shopt -s globstar
11-
- MAX_LINE_LENGTH=100 bash ci/check_line_lengths.sh src/**/*.md
1211
install:
1312
- source ~/.cargo/env || true
1413
- cargo install mdbook --version '^0.4.5'

src/code-considerations/reviewer-checklist.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,8 @@ r? @user
1212

1313
## Before you review
1414

15-
- [ ] Are there any `#[stable]` attributes involved?
15+
- [ ] Is this a [stabilization](../feature-lifecycle/stabilization.md) or [deprecation](../feature-lifecycle/deprecation.md)?
16+
- [ ] Make sure there's a completed FCP somewhere for it.
1617
- [ ] Ping `@rust-lang/libs` for input.
1718

1819
## As you review
@@ -29,8 +30,8 @@ Look out for code considerations:
2930

3031
- [ ] Is the commit log tidy? Avoid merge commits, these can be squashed down.
3132
- [ ] Can this change be rolled up?
32-
- [ ] Is this a new unstable feature?
33-
- [ ] Create a tracking issue.
33+
- [ ] Is this a [new unstable feature](../feature-lifecycle/landing-new-features.md)?
34+
- [ ] Create a [tracking issue](../feature-lifecycle/tracking-issues.md).
3435
- [ ] Update the `#[unstable]` attributes to point to it.
3536

3637
## When you're ready

src/getting-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
> Everything I wish I knew before somebody gave me `r+`
66
7-
This guide is an effort to capture some of the context needed to develop and maintain the Rust standard library. It’s goal is to help members of the Libs team share the process and experience they bring to working on the standard library so other members can benefit. It’ll probably accumulate a lot of trivia that might also be interesting to members of the wider Rust community.
7+
This guide is an effort to capture some of the context needed to develop and maintain the Rust standard library. Its goal is to help members of the Libs team share the process and experience they bring to working on the standard library so other members can benefit. It’ll probably accumulate a lot of trivia that might also be interesting to members of the wider Rust community.
88

99
## If you’re ever unsure…
1010

0 commit comments

Comments
 (0)