[
https://issues.apache.org/jira/browse/CASSGO-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898678#comment-17898678
]
Eric Evans commented on CASSGO-34:
----------------------------------
My vote would be set the version in {{go.mod}} to the lowest version that will
actually work (1.19 in this instance). The project not wanting to support more
than the last two versions, shouldn't prohibit using an older version, if it
would otherwise be expected to work. Think: Principle of Least Hostility. :)
> Decide go version Bump for goclq
> ----------------------------------
>
> Key: CASSGO-34
> URL: https://issues.apache.org/jira/browse/CASSGO-34
> Project: Apache Cassandra Go driver
> Issue Type: Improvement
> Components: Core
> Reporter: Stanislav Bychkov
> Priority: Normal
> Fix For: 2.0.0
>
>
> The current {{go.mod}} file in gocql specifies go 1.13 as the minimum
> version, which is outdated. Recent updates, including support for {*}Native
> Protocol v5{*}, introduced dependencies such as {{{}atomic.Bool{}}}, which
> require go 1.19 or higher to build successfully.
> GoCQL officially supports the *latest two Go releases* (currently *Go 1.22*
> and {*}Go 1.23{*}) and uses these versions in its CI pipeline. However, we
> need to determine whether to bump the {{go.mod}} version to:
> # {*}Go 1.19{*}: The minimum version required to build with
> {{{}atomic.Bool{}}}.
> # {*}Go 1.22{*}: Align with GoCQL’s official policy of supporting the latest
> two Go releases.
> This decision impacts users, as a higher {{go.mod}} version requires them to
> upgrade their Go environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
