From 043f50487a331678f1faf56d76fe023425f9c89b Mon Sep 17 00:00:00 2001 From: Michael Vines Date: Sat, 17 Nov 2018 16:29:19 -0800 Subject: [PATCH] Document patch version updates after a release is made --- RELEASE.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 995bfad07..c108c7d24 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -12,8 +12,8 @@ When cutting a new channel branch these pre-steps are required: 1. Pick your branch point for release on master. 2. Create the branch. The name should be "v" + the first 2 "version" fields from Cargo.toml. For example, a Cargo.toml with version = "0.9.0" implies the next branch name is "v0.9". -3. Update Cargo.toml to the next semantic version (e.g. 0.9.0 -> 0.10.0) by running `./scripts/increment-cargo-version.sh`. -4. Push your new branch to solana.git +4. Push the new branch to the solana repository +3. Update Cargo.toml on master to the next semantic version (e.g. 0.9.0 -> 0.10.0) by running `./scripts/increment-cargo-version.sh`. 5. Land your Cargo.toml change as a master PR. At this point, ci/channel-info.sh should show your freshly cut release branch as "BETA_CHANNEL" and the previous release branch as "STABLE_CHANNEL". @@ -23,10 +23,12 @@ At this point, ci/channel-info.sh should show your freshly cut release branch as We use [github's Releases UI](https://github.com/solana-labs/solana/releases) for tagging a release. 1. Go [there ;)](https://github.com/solana-labs/solana/releases). -2. Click "Draft new release". +2. Click "Draft new release". The release tag must exactly match the `version` field in `/Cargo.toml` prefixed by `v` (ie, `.X`). 3. If the first major release on the branch (e.g. v0.8.0), paste in [this template](https://raw.githubusercontent.com/solana-labs/solana/master/.github/RELEASE_TEMPLATE.md) and fill it in. -4. Test the release by generating a tag using semver's rules. First try at a release should be .X-rc.0. +4. Test the release by generating a tag using semver's rules. First try at a release should be `.X-rc.0`. 5. Verify release automation: 1. [Crates.io](https://crates.io/crates/solana) should have an updated Solana version. 2. ... 6. After testnet deployment, verify that testnets are running correct software. http://metrics.solana.com should show testnet running on a hash from your newly created branch. +7. Once the release has been made, update Cargo.toml on release to the next semantic version (e.g. 0.9.0 -> 0.9.1) by running `./scripts/increment-cargo-version.sh patch`. +