- 
                Notifications
    You must be signed in to change notification settings 
- Fork 23
Prepare 0.2.0 release #52
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
Prepare 0.2.0 release #52
Conversation
this change updates the target of the email for releasing new versions.
this change updates the readmes, documentation, and helm chart for the 0.2.0 release.
| [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elmiko The full list of commands accepted by this bot can be found here. The pull request process is described here 
Needs approval from an approver in each of these files:
 
 Approvers can indicate their approval by writing  | 
| /hold i would like to get #51 merged before we make this release. | 
| provider | ||
|  | ||
|    | ||
|    | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just trying to understand how we are versioning this project, are we doing chart releases separate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm not a helm expert, but i thought we needed to update the app version when doing a new relaese.
as to the larger question, i would like to get automated image builds working when we do releases.
| /lgtm | 
| /unhold | 
this change updates the documentation and helm chart files for the upcoming 0.2.0 release.
fixes: #45