[ https://issues.apache.org/jira/browse/CASSANDRA-16509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Widman updated CASSANDRA-16509: ------------------------------------ Description: For the Cassandra 4.x release series, please should bump the cqlsh version... This way users can report which version of cqlsh they're using, along with the protocol/server version. It's been 5.0.1 for the cassandra 3.x series, so 6.0.0 probably makes sense because there are possible breaking changes depending on how CASSANDRA-16508 is resolved. Right now, if a user says they're using `cqlsh` 5.0.1, we have no idea which release they're actually using because that version number hasn't been incremented for several releases, even though the code is changing. I maintain a standalone version of `cqlsh` on PyPI for lighter-weight installs, and it'd be very helpful if the version was bumped. I opened a PR here to fix it: https://github.com/apache/cassandra/pull/923 Although I wasn't sure if this should be set to 6.0.0 because 6.0.0-beta5 might be more appropriate if there's another beta release planned before GA. was: For the Cassandra 4.x release series, please should bump the cqlsh version... This way users can report which version of cqlsh they're using, along with the protocol/server version. It's been 5.0.1 for the cassandra 3.x series, so 6.0.0 probably makes sense because there are possible breaking changes depending on how CASSANDRA-16508 is resolved. Right now, if a user says they're using `cqlsh` 5.0.1, we have no idea which release they're actually using because that version number hasn't been incremented for several releases, even though the code is changing. I maintain a standalone version of `cqlsh` on PyPI for lighter-weight installs, and it'd be very helpful if the version was bumped. > Bump cqlsh version to 6.0.0 > --------------------------- > > Key: CASSANDRA-16509 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16509 > Project: Cassandra > Issue Type: Task > Reporter: Jeff Widman > Priority: Normal > Time Spent: 20m > Remaining Estimate: 0h > > For the Cassandra 4.x release series, please should bump the cqlsh version... > This way users can report which version of cqlsh they're using, along with > the protocol/server version. > It's been 5.0.1 for the cassandra 3.x series, so 6.0.0 probably makes sense > because there are possible breaking changes depending on how CASSANDRA-16508 > is resolved. > Right now, if a user says they're using `cqlsh` 5.0.1, we have no idea which > release they're actually using because that version number hasn't been > incremented for several releases, even though the code is changing. > I maintain a standalone version of `cqlsh` on PyPI for lighter-weight > installs, and it'd be very helpful if the version was bumped. > I opened a PR here to fix it: https://github.com/apache/cassandra/pull/923 > Although I wasn't sure if this should be set to 6.0.0 because 6.0.0-beta5 > might be more appropriate if there's another beta release planned before GA. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org