[
https://issues.apache.org/jira/browse/CASSANDRA-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303520#comment-17303520
]
Sam Tunnicliffe commented on CASSANDRA-13951:
---------------------------------------------
The python driver is still awaiting release, but really the java driver
dependency is the more critical one to upgrade, so I've pushed a patch and
started CI.
|Patch|
[here|https://github.com/apache/cassandra/compare/trunk...beobal:13951-trunk]|
|CircleCI|
[here|https://app.circleci.com/pipelines/github/beobal/cassandra?branch=13951-trunk]|
|Apache CI|
[here|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/493/]|
> Release Java and Python drivers and re-enable build.xml driver dep
> ------------------------------------------------------------------
>
> Key: CASSANDRA-13951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13951
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Urgent
> Fix For: 4.0, 4.0-rc
>
>
> During [CASSANDRA-10786], driver changes were introduced that required a
> snapshot release of both drivers.
> When the stable driver version is published, we have to update the driver
> dependencies in {{lib}} and un-comment {{build.xml}} sections with
> {{java-driver}} information for correct publish of 4.0. This manipulation was
> required in order to account for the chicken-or-egg problem between Cassandra
> itself and the drivers.
> This absolutely has to be done before 4.0 & there should be no release
> without making sure right drivers are in place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
