diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2020-07-20 05:27:41 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-20 05:27:41 +0900 |
| commit | e38ca715f0f6699e726086ae838a01c231f2438d (patch) | |
| tree | cffc37112904b5e0be3e9400b8b6b9b448fa694d | |
| parent | b17047fc2d01675e435495be857014aa007b4857 (diff) | |
| parent | 11e03e8ea2b23bd025f767d4c602ad7c66908a8a (diff) | |
| download | rust-libc-e38ca715f0f6699e726086ae838a01c231f2438d.tar.gz | |
Merge pull request #1826 from shepmaster/release-instructions
Remove unneeded release step
| -rw-r--r-- | CONTRIBUTING.md | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 052777f416..510d760ef8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -53,14 +53,11 @@ platform in this crate, the next step is to get that sweet, sweet usage from crates.io! The only next step is to bump the version of libc and then publish it. If you'd like to get a release out ASAP you can follow these steps: -1. Update the version number in `Cargo.toml`, you'll just be bumping the patch - version number. -2. Run `cargo update` to regenerate the lockfile to encode your version bump in - the lock file. You may pull in some other updated dependencies, that's ok. -3. Send a PR to this repository. It should [look like this][example], but it'd +1. Increment the patch version number in `Cargo.toml`. +1. Send a PR to this repository. It should [look like this][example], but it'd also be nice to fill out the description with a small rationale for the release (any rationale is ok though!) -4. Once merged the release will be tagged and published by one of the libc crate +1. Once merged, the release will be tagged and published by one of the libc crate maintainers. [example]: https://github.com/rust-lang/libc/pull/583 |