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

Release sbo 1.2.0 #7

Merged
merged 1 commit into from
Sep 16, 2022

Conversation

Kartikey-star
Copy link
Collaborator

This PR updates service binding operator repository with app version 1.2.0
Signed-off-by: Kartikey Mamgain mamgainkartikey@gmail.com

Signed-off-by: Kartikey Mamgain <mamgainkartikey@gmail.com>
Copy link

@dperaza4dustbit dperaza4dustbit left a comment

Choose a reason for hiding this comment

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

lgtm, one question

name: service-binding-operator
type: application
urls:
- service-binding-operator-1.1.0.tgz
Copy link

Choose a reason for hiding this comment

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

I think it is good, but just for me to understand, what is the criteria to move this version to patch , minor or major

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think since we have changed the template/test and added a param to values.yaml this should be a minor changes , so 1.1.0. Previously there was no major change on the chart, only the image hash in the deployment image changed.
When sbo moves to 2.x.x. we should move as well considering that will be a major change.
Going forward for the sake of consistency i would say we should keep the app version and chart version same.

@Kartikey-star Kartikey-star merged commit 248406f into redhat-developer:gh-pages Sep 16, 2022
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

2 participants