mirror of
https://github.com/lensapp/lens.git
synced 2025-05-20 05:10:56 +00:00
Document release process (#532)
Signed-off-by: Lauri Nevala <lauri.nevala@gmail.com>
This commit is contained in:
parent
b7974827d2
commit
9456a696af
11
RELEASE_GUIDE.md
Normal file
11
RELEASE_GUIDE.md
Normal file
@ -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.
|
||||||
Loading…
Reference in New Issue
Block a user