[ 
https://issues.apache.org/jira/browse/CASSGO-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899109#comment-17899109
 ] 

Stanislav Bychkov commented on CASSGO-34:
-----------------------------------------

[~urandom], thank you for sharing your perspective, especially about 
Wikimedia's use of gocql in critical production services. It's very helpful to 
understand the real-world implications of changes like these.

Given your input, I agree that a more conservative approach is warranted for 
now. It seems reasonable to fix the decision to set a minimum requirement of go 
version 1.19, ensuring compatibility for the broadest range of users, including 
those in production environments like yours.

At the same time, we can continue monitoring the ecosystem to understand when 
moving to a higher go version becomes feasible. As we approach potential 
milestones like a gocql 2.0 release, it could be an opportunity to reassess and 
communicate such changes well in advance, ensuring minimal disruption for users.

If there are specific concerns about upgrade challenges, perhaps we could 
explore ways to mitigate those or document best practices to ease transitions. 
Let me know if there's anything specific that would help Wikimedia or other 
projects in this regard.

Thanks again for sharing this—it’s exactly the kind of input that helps make 
right decisions that balance progress with stability.

> 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]

Reply via email to