Bump Go/C* versions #1813
Bump Go/C* versions #1813
Conversation
|
we are contemplating about doing this in #1812 Would you mind to take it there? |
|
@smiklosovic I actually think this should be handled independently. We should upgrade the Go versions for 1.7.0 and I'd rather not bring any additional changes along with that if we can avoid it. Ideally 1.7.0 would basically be what was in 1.6.0 along with a few changes related to the release/ASF conversion. |
| go: [ '1.19', '1.20' ] | ||
| cassandra_version: [ '4.0.8', '4.1.1' ] | ||
| go: [ '1.22', '1.23' ] | ||
| cassandra_version: [ '4.0.13', '4.1.6' ] |
There was a problem hiding this comment.
4.1.6 and 4.0.13 are the latest 4.1.x and 4.0.x as of this writing. But now I'm wondering if we shouldn't be aiming for 4.1.x & 5.0.0 instead.
Trouble is stock ccm has issues with 5.0.0... and supporting a new major version of Cassandra probably needs a ticket (or perhaps even tickets) all to itself.
|
Closing in favor of #1825 |
4 participants
In prep for 1.7.0 release.
Ambition here is to match the "Sunsetting Model" that was in place with gocql.
Test run shows this passes all existing tests.