From 34d2c317115a5d00588401778382180ccc673c7c Mon Sep 17 00:00:00 2001 From: NibiruHeisenberg <101130700+NibiruHeisenberg@users.noreply.github.com> Date: Wed, 13 Jul 2022 12:47:26 -0700 Subject: [PATCH 1/3] Add release process --- CHANGELOG.md | 4 ++++ RELEASE_PROCESS.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 50 insertions(+) create mode 100644 RELEASE_PROCESS.md diff --git a/CHANGELOG.md b/CHANGELOG.md index a69c6911b..b62609d32 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -42,6 +42,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## Unreleased +### Documentation + +* Add release process guide + ## [v0.9.2](https://github.com/NibiruChain/nibiru/releases/tag/v0.9.2) - 2022-07-11 ### Improvements diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md new file mode 100644 index 000000000..cc1b87455 --- /dev/null +++ b/RELEASE_PROCESS.md @@ -0,0 +1,46 @@ +# Release Process + +This document outlines the process for releasing a new version of the Nibiru binary. + +## Step 1) Create a new release branch off master + +```sh +$ git checkout master +$ git branch releases/v0.x.y +$ git switch releases/v0.x.y +``` + +## Step 2) Update the changelog + +- Move the changelog notes from `Unreleased` to a new section titled `v0.x.y` +- Add the date to `v0.x.y` + +## Step 3) Create a tag + +```sh +$ git tag -a -s -m "Create new release v0.x.y" v0.x.y +$ git push origin v0.x.y +``` + +## Step 4) Go to the [GitHub Releases](https://github.com/NibiruChain/nibiru/releases) page + +- Create a new release from the tag v0.x.y you just pushed +- Make sure you save the release as a draft release +- Make sure you check the `This is a pre-release` checkbox + +## Step 5) Build the binaries locally + +```sh +$ cd nibiru/ +$ ignite chain build --release -t linux:amd64 -t darwin:amd64 -t darwin:arm64 +``` + + + +## Step 6) Upload the files in the release/ directory to GitHub + +Upload all the files under `releases/` to the [GitHub Release](https://github.com/NibiruChain/nibiru/releases) you just made + +## Step 7) Merge your release branch into master + +After merging the release branch `releases/v0.x.y` into master, uncheck the `This is a pre-release` checkbox for the release. \ No newline at end of file From 90580345318848dc2ec2269ad2b7423ac7f2a299 Mon Sep 17 00:00:00 2001 From: NibiruHeisenberg <101130700+NibiruHeisenberg@users.noreply.github.com> Date: Wed, 13 Jul 2022 12:48:01 -0700 Subject: [PATCH 2/3] Update CHANGELOG.md --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b62609d32..edd6bed7c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -44,7 +44,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Documentation -* Add release process guide +* [#701](https://github.com/NibiruChain/nibiru/pull/701) Add release process guide ## [v0.9.2](https://github.com/NibiruChain/nibiru/releases/tag/v0.9.2) - 2022-07-11 From 558af68982cfe785de2a55c1c027dc543c0e5646 Mon Sep 17 00:00:00 2001 From: NibiruHeisenberg <101130700+NibiruHeisenberg@users.noreply.github.com> Date: Mon, 18 Jul 2022 09:24:04 -0700 Subject: [PATCH 3/3] Add linux:arm64 --- RELEASE_PROCESS.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md index cc1b87455..0ba7a72a2 100644 --- a/RELEASE_PROCESS.md +++ b/RELEASE_PROCESS.md @@ -5,9 +5,9 @@ This document outlines the process for releasing a new version of the Nibiru bin ## Step 1) Create a new release branch off master ```sh -$ git checkout master -$ git branch releases/v0.x.y -$ git switch releases/v0.x.y +git checkout master +git branch releases/v0.x.y +git switch releases/v0.x.y ``` ## Step 2) Update the changelog @@ -18,8 +18,8 @@ $ git switch releases/v0.x.y ## Step 3) Create a tag ```sh -$ git tag -a -s -m "Create new release v0.x.y" v0.x.y -$ git push origin v0.x.y +git tag -a -s -m "Create new release v0.x.y" v0.x.y +git push origin v0.x.y ``` ## Step 4) Go to the [GitHub Releases](https://github.com/NibiruChain/nibiru/releases) page @@ -31,11 +31,10 @@ $ git push origin v0.x.y ## Step 5) Build the binaries locally ```sh -$ cd nibiru/ -$ ignite chain build --release -t linux:amd64 -t darwin:amd64 -t darwin:arm64 -``` - +cd nibiru/ +ignite chain build --release -t linux:amd64 -t linux:arm64 -t darwin:amd64 -t darwin:arm64 +``` ## Step 6) Upload the files in the release/ directory to GitHub @@ -43,4 +42,4 @@ Upload all the files under `releases/` to the [GitHub Release](https://github.co ## Step 7) Merge your release branch into master -After merging the release branch `releases/v0.x.y` into master, uncheck the `This is a pre-release` checkbox for the release. \ No newline at end of file +After merging the release branch `releases/v0.x.y` into master, uncheck the `This is a pre-release` checkbox for the release.