Re: [DISCUSS] Go version in go.mod (GoCQL)

I personally think we should strive to align the go version in go.mod to what we test against and officially support, it clearly describes what the project is built and tested against to other developers/users, but happy to be told that's overkill and 1.19 is fine. If there is a time to push to new

Re: [DISCUSS] GoCQL sub modules vs packages

I concur with the approach of having a single module for the driver, I don't think this project is complicated enough yet to require separate modules, the project is new to the Apache foundation and keeping things simple will make it easier for people to learn and contribute. I also agree that we

RE: [DISCUSS] GoCQL sub modules vs packages

I'm in favor of the packages approach as discussed. Reference to my earlier comment here: GitHub Issue #1770 .

RE: [DISCUSS] Go version in go.mod (GoCQL)

On the topic of updating the go version for gocql. As the recent maintainer, Martin Sucha, mentioned: > In our README, we state: >> In general, the Cassandra community will focus on supporting the current and previous versions of Go. > So it should be safe to bump to 1.22. However, it should be