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

Is the cool-off time between go versions right? #2918

Closed
MadVikingGod opened this issue May 20, 2022 · 2 comments · Fixed by #3079
Closed

Is the cool-off time between go versions right? #2918

MadVikingGod opened this issue May 20, 2022 · 2 comments · Fixed by #3079
Milestone

Comments

@MadVikingGod
Copy link
Contributor

MadVikingGod commented May 20, 2022

I would like to do a review of our go version process. Go1.18 was added in #2679, published in v1.6.0 on 2022-03-23, and I have proposed to remove go1.16 in #2917.

As currently written we support the two latest versions, and a dropped version (1.16) for up to 3 months.

Is this an acceptable time period?
Is this too long?
Is this too short?
Was this time useful?

@dmathieu
Copy link
Member

I don't know if we should support a version if it's not support anymore on the language side.

@MadVikingGod
Copy link
Contributor Author

Notes from the SIG meeting:

The ask on the call is the first release after a new version of go, eg. go1.18, should add the new go version. The release after that will remove the oldest version, eg. go 1.16.

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