Release automation

[qinsoon]

We should have an automated process for release. I assume it should be manually triggered, by either a version bump PR, or a Github release.

The following is a checklist for doing a MMTk release.

MMTk core

• Make sure all related PRs are merged.
• Create a new PR to bump version in Cargo.toml. Update CHANGELOG.md. Follow the standard PR policy to merge it.
• Create a release for mmtk-core on Github, which will tag the revision. Use the new section of CHANGELOG as description.
• Cargo publish
• get mmtkgc bot's credential. Login to crates.io, get a token
• cargo login xxxxxx
• RUSTUP_TOOLCHAIN=nightly-2020-07-08 cargo publish --features semispace --dry-run
• If the above step works fine, do publish
• RUSTUP_TOOLCHAIN=nightly-2020-07-08 cargo publish --features semispace
• Check here: https://crates.io/crates/mmtk
• Check docs queue: https://docs.rs/releases/queue
• Eventually the docs will be built and showup here: https://docs.rs/releases/search?query=mmtk

Bindings

• For each binding:
• Update version in Cargo.toml
• Update mmtk rev to the latest in mmtk-core
• Create a new PR and get it merged.
• Create a release for the binding on Github, which will tag the revision.

[qinsoon]

With #325, when a new Github release is published, we will automatically do a cargo publish for the release. Thus the release procedure becomes:

MMTk core

• Make sure all related PRs are merged.
• Create a new PR to bump version in Cargo.toml. Update CHANGELOG.md. Follow the standard PR policy to merge it.
• Create a release for mmtk-core on Github, which will tag the revision. Use the new section of CHANGELOG as description.

Bindings

• For each binding:
  • Update version in Cargo.toml
  • Update mmtk rev to the latest in mmtk-core
  • Create a new PR and get it merged.
  • Create a release for the binding on Github, which will tag the revision.

If we think about more automation in the release procedure, we can automate bumping the version and publishing a github release.