From 9456a696aff99580d65ee183e3d0f36302c322e4 Mon Sep 17 00:00:00 2001 From: Lauri Nevala Date: Tue, 30 Jun 2020 15:22:20 +0300 Subject: [PATCH] Document release process (#532) Signed-off-by: Lauri Nevala --- RELEASE_GUIDE.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 RELEASE_GUIDE.md diff --git a/RELEASE_GUIDE.md b/RELEASE_GUIDE.md new file mode 100644 index 0000000000..da4bf01d94 --- /dev/null +++ b/RELEASE_GUIDE.md @@ -0,0 +1,11 @@ +# Release Process + +Lens releases are built by CICD automatically on git tags. The typical release process flow is the following: + +1. Create a release branch `release/v{version}` from `master` branch or from existing release branch (for example, `release/v3.5`) on patch releases. +2. Update changelog in `static/RELEASE_NOTES.md` and bump version in `package.json`. +3. Create PR and put change log in description field. +4. After the PR is accepted, create a tag from release branch. +5. Push tag to GitHub. +6. Publish automatically created GitHub release. +7. Merge the release PR after the release is published and delete the release branch from GitHub. \ No newline at end of file