Update releasing doc.
@@ -13,10 +13,13 @@ Rusoto uses [semantic versioning 2.0.0](http://semver.org/).
### Publishing walkthrough:
-1. Make a pull request that bumps version numbers for `rusoto_core` if needed and each service that changed since previous release. Service versions are in the `services.json` file in the codegen project. Make sure the root Rusoto README example gets updated with the new version.
-2. After new release PR has been merged, publish `rusoto_core` if it had changes since last release.
-3. Run `publish-services.sh` in the `rusoto/services` dir. *Warning*: takes 1.5 hours on a low end Macbook.
-4. Tag master with the new version. Example: `git tag -a rusoto-v0.21.0 -m "Rusoto 0.21.0 release."` then `git push --tags origin`.
+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.
+2. Merge release PR.
+3. Publish new version of `rusoto_credential` if changes have been made to it.
+4. Publish new version of `rusoto_mock` if changes have been made to it.
+5. Publish new version of `rusoto_core` if it changes have been made to it.
+6. Run `publish-services.sh` in the `rusoto/services` dir. *Warning*: takes >2 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`.
### Git tags
@@ -26,6 +29,7 @@ Examples:
* `rusoto-v0.21.0`
* `credentials-v0.3.0`
+* `mock-v0.27.0`
### Release notes
