[ https://issues.apache.org/jira/browse/CASSANDRA-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305206#comment-17305206 ]
Adam Holmberg commented on CASSANDRA-13951: ------------------------------------------- Python driver 3.25.0 [released|https://groups.google.com/a/lists.datastax.com/g/python-driver-user/c/XrZ1cBBHNyU/m/HC7sM9giBQAJ]. If you want to bump that here too, I updated your branch and kicked off another CI run: https://app.circleci.com/pipelines/github/aholmberg/cassandra?branch=13951-trunk > 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: Sam Tunnicliffe > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org