Update releasing document.
@@ -22,13 +22,15 @@ Rusoto uses [semantic versioning 2.0.0](http://semver.org/).
### Publishing walkthrough:
-1. Make a pull request that bumps version numbers for `rusoto_core`, `rusoto_credential` and `rusoto_mock` if needed and each service that changed since previous release. Service versions are in the `services.json` file in the codegen project. Otherwise they are in the `Cargo.toml` files for each project. Make sure the root Rusoto README example gets updated with the new version. The `skeptical` package will also need to be set to use the new version of Rusoto - do this in a PR after the release and publish has been completed.
-2. Merge release PR.
-3. Publish new version of `rusoto_credential` if changes have been made to it.
-4. Publish new version of `rusoto_core` if changes have been made to it.
-5. Publish new version of `rusoto_mock` if it changes have been made to it.
-6. Run `publish-services.sh` in the `rusoto/services` dir. *Warning*: takes >4 hours on a low end Macbook. The script can be run again if an issue comes up without problems - crates.io prevents republishing.
-7. Tag master branch with the new version. Example: `git tag -a rusoto-v0.21.0 -m "Rusoto 0.21.0 release."` then `git push --tags origin`.
+1. Ensure all PRs included in the release are reflected in [the CHANGELOG](https://github.com/rusoto/rusoto/blob/master/CHANGELOG.md). If in doubt, add an entry so it's recorded. Can be a separate PR or part of the one below.
+2. Make a pull request that bumps version numbers for `rusoto_core`, `rusoto_credential`, `rusoto_signature` and `rusoto_mock` if needed and each service that changed since previous release. Service versions are in the `services.json` file in the codegen project. Otherwise they are in the `Cargo.toml` files for each project. Make sure the root Rusoto README example gets updated with the new version. The `skeptical` package will also need to be set to use the new version of Rusoto - do this in a PR after the release and publish has been completed.
+3. Merge release PR.
+4. Publish new version of `rusoto_credential`.
+5. Publish new version of `rusoto_signature`.
+6. Publish new version of `rusoto_core`.
+7. Publish new version of `rusoto_mock`.
+8. Run `publish-services.sh` in the `rusoto/services` dir. *Warning*: takes >4 hours on a low end Macbook. The script can be run again if an issue comes up without problems - crates.io prevents republishing.
+9. Tag master branch with the new version. Example: `git tag -a rusoto-v0.41.0 -m "Rusoto 0.41.0 release."` then `git push --tags origin`.
### Git tags
@@ -36,9 +38,10 @@ Due to multiple crates being in the repo, releases for each crate will be in the
Examples:
-* `rusoto-v0.41.0`
-* `credentials-v0.41.0`
-* `mock-v0.41.0`
+* `rusoto-v0.42.0`
+* `credentials-v0.42.0`
+* `signature-v0.42.0`
+* `mock-v0.42.0`
When bug fixes for a crate are published, all crates get a new release.
