Update maintainer guidelines.
## Maintainer Guidelines
-### Releasing working code
+### Pull request review
-* run a full suite of actual integration tests before accepting a PR
-* releases should have a full integration test run before releasing to catch stragglers
+1. New service has integration test(s)
+2. All integration tests pass
+3. Code looks sound
+4. Travis/Appveyor builds pass
+5. Rustfmt has been run
-### Development
+### Cutting a release
+
+1. Make a new branch for the release, following the [RELEASING](RELEASING.md) document. ([Example release PR](https://github.com/rusoto/rusoto/pull/883))
+2. Run all integration tests on the PR branch.
+3. After release PR is reviewed and merged, follow instructions in [RELEASING](RELEASING.md).
+
+### Development direction
* Rusoto should be able to be used and developed on Rust's stable channel
-* to hit Rusoto's 1.0 release we should have all known AWS related bugs fixed (Ceph and minio are not required for 1.0) and all services covered
+* Rusoto's 1.0 release should have all known AWS related bugs fixed (Ceph and Minio are not required for 1.0) and all services implemented and covered with integration tests (if possible)
