rust/PUBLISH.md

Steps to publish a new Clippy version

- Bump `package.version` in `./Cargo.toml` (no need to manually bump `dependencies.clippy_lints.version`).
- Write a changelog entry.
- Run `./pre_publish.sh`
- Review and commit all changed files
- `git push`
- Wait for Travis's approval.
- Merge.
- `cargo publish` in `./clippy_lints`.
- `cargo publish` in the root directory.
- `git pull`.
- `git tag -s v0.0.X -m "v0.0.X"`.
- `git push --tags`.
Consistently call it "Clippy", not clippy or rust-clippy As per discussion on the Clippy 1.0 RFC 2018-07-05 05:37:50 -05:00			`Steps to publish a new Clippy version`
Create PUBLISH.md 2016-11-08 04:52:38 -06:00
			- Bump `package.version` in `./Cargo.toml` (no need to manually bump `dependencies.clippy_lints.version`).
			`- Write a changelog entry.`
Fix order of publishing steps 2017-02-27 02:49:18 -06:00			- Run `./pre_publish.sh`
only require rustfmt and update_lints for version bumps 2017-02-14 04:22:21 -06:00			`- Review and commit all changed files`
Create PUBLISH.md 2016-11-08 04:52:38 -06:00			- `git push`
			`- Wait for Travis's approval.`
			`- Merge.`
fix docs 2017-09-23 15:36:40 -05:00			- `cargo publish` in `./clippy_lints`.
Create PUBLISH.md 2016-11-08 04:52:38 -06:00			- `cargo publish` in the root directory.
			- `git pull`.
only require rustfmt and update_lints for version bumps 2017-02-14 04:22:21 -06:00			- `git tag -s v0.0.X -m "v0.0.X"`.
Create PUBLISH.md 2016-11-08 04:52:38 -06:00			- `git push --tags`.