You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Hershel1995 (via GitHub)" <gi...@apache.org> on 2026/03/09 10:59:06 UTC
[I] Release plan of library next versions [cassandra-gocql-driver]
Hershel1995 opened a new issue, #1931:
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931
Hello community!
are you able to provide a release plan for the next versions of the library? Or at least provide the planned release frequency (e.g. 2 releases per year, 1 release for quarter, etc...).
And if already known, what is the planned release date of version 2.1.0?
Thanks!
--
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: commits-unsubscribe@cassandra.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
Re: [I] Release plan of library next versions [cassandra-gocql-driver]
Posted by "joao-r-reis (via GitHub)" <gi...@apache.org>.
joao-r-reis commented on issue #1931:
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931#issuecomment-4024897305
> Unfortunately, we cannot directly update the primary dependencies of your gocql library, unless you release a new version with updated dependencies. It could happen that a direct dependencies of gocql is impacted by a CVE, and we would need to have in a certain time interval (more or less long) a new gocql version that includes the new dependency version fixing the security finding.
You can't choose the dependencies that gocql brings into your application but you can override the version. If you install those dependencies directly on your application those versions "override" the ones coming in from gocql. It's possible that the security scan will still fail depending on what kind of tool you are using but in practice the application developer has the final say over which version of the dependency will be used in that application binary.
--
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: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
Re: [I] Release plan of library next versions [cassandra-gocql-driver]
Posted by "joao-r-reis (via GitHub)" <gi...@apache.org>.
joao-r-reis commented on issue #1931:
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931#issuecomment-4023545980
Updating library dependencies too often can also be an issue for certain users so we have to be mindful of that. Users can always update the dependencies on their own go.mod if they want to
--
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: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
Re: [I] Release plan of library next versions [cassandra-gocql-driver]
Posted by "joao-r-reis (via GitHub)" <gi...@apache.org>.
joao-r-reis commented on issue #1931:
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931#issuecomment-4022977239
Hi, the goal is to have at least 2 releases per year but we rely on a small group of contributors and committers at the moment so we can't really set specific dates in stone. At the moment we're mostly deciding when to release based on the amount of PRs that have been merged to `trunk` and how important they are. We're planning to release 2.1.0 soon (in the following weeks, maybe next month).
Is there a particular feature/fix you're interested in?
--
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: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
Re: [I] Release plan of library next versions [cassandra-gocql-driver]
Posted by "Hershel1995 (via GitHub)" <gi...@apache.org>.
Hershel1995 commented on issue #1931:
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931#issuecomment-4023678565
Yes, for sure in case of a major update of direct dependencies you need to analyze impacts and understand if they are disruptive (in that case evaluating if a patch release does not fit well).
Unfortunately, we cannot directly update the primary dependencies of your gocql library, unless you release a new version with updated dependencies. It could happen that a direct dependencies of gocql is impacted by a CVE, and we would need to have in a certain time interval (more or less long) a new gocql version that includes the new dependency version fixing the security finding.
I would like to suggest you to also consider updating direct dependencies before to proceed with an official release, in order to support also a periodic refreshment and avoid security impacts.
Anyhow, thanks for the positive discussion and information! I will close the issue.
--
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: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
Re: [I] Release plan of library next versions [cassandra-gocql-driver]
Posted by "Hershel1995 (via GitHub)" <gi...@apache.org>.
Hershel1995 commented on issue #1931:
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931#issuecomment-4023143911
Hi @joao-r-reis, thanks a lot for your prompt response!
Not interested in a specific feature/fix, we need only to know the frequency of your releases since we have a strict process in updating libraries due to security reasons.
In this scope, it could be useful (not only for us) to have more frequent versions only restricted to update library dependencies in the go.mod, in order to release a sort of security patches tagged with the patch number (for example 2.0.1).
--
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: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
Re: [I] Release plan of library next versions [cassandra-gocql-driver]
Posted by "Hershel1995 (via GitHub)" <gi...@apache.org>.
Hershel1995 closed issue #1931: Release plan of library next versions
URL: https://github.com/apache/cassandra-gocql-driver/issues/1931
--
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: commits-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org