Skip to content

Latest commit

 

History

History
26 lines (18 loc) · 1.17 KB

MAINTAINER_GUIDELINES.md

File metadata and controls

26 lines (18 loc) · 1.17 KB
Raw

Maintainer Guidelines

General

  1. The master branch build should be green. If it's not, it should be a high priority to fix.
  2. Rusoto documentation should work and not be wrong or misleading. This includes https://rusoto.org and the crate docs on https://docs.rs. It doesn't have to be 100% up to date but it should work. Skeptic is used to help with this.
  3. Generally prefer fixing bugs over new features.

Pull request review

  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

Cutting a release

  1. Make a new branch for the release, following the RELEASING document. (Example release PR)
  2. Run all integration tests on the PR branch.
  3. After release PR is reviewed and merged, follow instructions in RELEASING.

Development direction

  • Rusoto should be able to be used and developed on Rust's stable channel
  • 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)