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 Trino Gateway chart 1.13.0 #270

Merged
merged 2 commits into from
Dec 4, 2024

Conversation

mosabua
Copy link
Member

@mosabua mosabua commented Dec 2, 2024

For Trino Gateway 13

Also @willmostly

@nineinchnick
Copy link
Member

Trino Gateway's Docker image 13 is not available yet: https://hub.docker.com/r/trinodb/trino-gateway/tags

@mosabua
Copy link
Member Author

mosabua commented Dec 3, 2024

Trino Gateway's Docker image 13 is not available yet: https://hub.docker.com/r/trinodb/trino-gateway/tags

I know .. this is in preparation to get things ready..

@mosabua
Copy link
Member Author

mosabua commented Dec 3, 2024

I pushed a commit again so this build runs again since the docker container is released .. but there are failures.. what am I missing @nineinchnick and @willmostly ?

@mosabua
Copy link
Member Author

mosabua commented Dec 3, 2024

Nevermind .. I think I found it.

@nineinchnick
Copy link
Member

You need to commit the updated Readme. See the main repo readme on how to set up a precommit hook to do this automatically

@mosabua mosabua force-pushed the trino-gateway-13 branch 5 times, most recently from 9f8256a to 9d46ff9 Compare December 4, 2024 01:12
@mosabua
Copy link
Member Author

mosabua commented Dec 4, 2024

Finally.. it passed now.

Copy link
Member

@Chaho12 Chaho12 left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@@ -2,15 +2,15 @@ apiVersion: v2
name: trino-gateway
description: A Helm chart for Trino Gateway
type: application
version: "0.12.0"
appVersion: "12"
version: "1.13.0"
Copy link
Member

Choose a reason for hiding this comment

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

Why do we increment a major version?

Copy link
Member

Choose a reason for hiding this comment

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

Having 0 as the major version might be understood the chart is unstable, or not ready for production use, which is not accurate, and might confuse some users. We agreed with @mosabua to bump major versions for both Trino and Trino Gateway to 1. So there are no breaking changes here, we just want to mark a stable release from this point forward.

Copy link
Member Author

@mosabua mosabua Dec 4, 2024

Choose a reason for hiding this comment

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

Our chart used to have full major versions so 10.0.0, 11.0.0 .. and when we changed to the chart repo here it was changed to 0.x .. however we (Trino Gateway maintainers and @nineinchnick feel that this is misleading. The chart is totally usable for production so the version should be > 1.0 .. hence we are switching 1.x with x being the Trino Gateway version now .. and if we cut chart releases in between we go minor update..

We also plan to upgrade the trino chart to be >1 .. and the go client ..

Copy link
Contributor

@willmostly willmostly left a comment

Choose a reason for hiding this comment

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

This lgtm

@mosabua mosabua merged commit 4275fca into trinodb:main Dec 4, 2024
10 checks passed
@mosabua mosabua deleted the trino-gateway-13 branch December 4, 2024 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants