Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release steps #202

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

varshaprasad96
Copy link
Member

Add release steps.

@varshaprasad96
Copy link
Member Author

cc: @jmrodri @everettraven

@coveralls
Copy link

coveralls commented Oct 16, 2022

Pull Request Test Coverage Report for Build 3261135424

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.223%

Totals Coverage Status
Change from base Build 3253085864: 0.0%
Covered Lines: 1631
Relevant Lines: 1828

💛 - Coveralls

@@ -0,0 +1,40 @@
This document walks through the release process for helm-operator-plugins.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This document walks through the release process for helm-operator-plugins.
# Release process for `helm-operator-plugins`

**Note**
The release PR with the above mentioned change will **fail** the `sanity` test and needs to be merged forcefully. This step is done because the packages which are to be imported in the scaffolded project and the plugin code reside in the same repository. This will ensure that after the release, the plugin will also import the updated version of library helpers.

2. Create a release branch with the name vX.Y.x. Example: `git checkout -b v0.0.10`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Create a release branch with the name vX.Y.x. Example: `git checkout -b v0.0.10`.
2. Create a release branch with the name vX.Y.Z. Example: `git checkout -b v0.0.10`.

3. Tag the release commit and verify the generated tag.

```
export VER=v0.0.10
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export VER=v0.0.10
VER=v0.0.10

No need to pollute the environment by exporting a variable that is only interpreted by the current shell.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, if you provided this variable setting as "step 0" it would be straightforward to reference it also in the commands in following steps rather than the ugly <release-branch> placeholder which is not copy-pasteable.


```
export VER=v0.0.10
git tag --sign --message "helm-operator-plugin $VER" "$VER"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to require some prior GPG setup. Might be useful to mention this as a prerequisite.

Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall looks good to me. I agree with @porridge's review suggestions/comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants