ribaraka commented on PR #1812: URL: https://github.com/apache/cassandra-gocql-driver/pull/1812#issuecomment-2330844722
> Have you tried to bump it to 1.23 to see if it still works? I upgraded the project’s Go version to 1.23 and added a Go version matrix (1.20-1.23) to the CI pipeline. The pipeline ran successfully for all versions except Go 1.20. Currently, I'm encountering a compilation error when trying to build Go 1.23 code with Go 1.20. When updating the Go version to 1.23 **only** in the CI workflow for this PR (while the project's Go version remains at 1.21), both versions 1.20 and 1.23 work fine. The current PR's Go version seems to strike a good balance across all these versions. > OK so I think that we should code against 1.20 and having 1.23 supported which is the latest one. Basically, test the oldest version possible and the newest one makes sense to me. https://github.com/apache/cassandra-gocql-driver/issues/1686#issuecomment-2147426562 I assume maintainers of the gocql were focused on supporting the last magor go version due to support of security, vulnerability updates and optimization. From the [Go Release Policy](https://go.dev/doc/devel/release#policy) : > Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release. We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions (for example, Go 1.6.1, Go 1.6.2, and so on). @martin-sucha might have a good vision for the project’s go version. At least he suggested to bump the version up to 1.21. > Contributor guide is OK, just link that from the main readme or made it more visible so people do not need to look for that for too long. OK, I will do it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
