[
https://issues.apache.org/jira/browse/CASSANDRA-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-13951:
----------------------------------------
Fix Version/s: (was: 4.0-rc)
(was: 4.0)
4.0-beta5
Source Control Link:
https://github.com/apache/cassandra/commit/1371883db3d8bf7d7c54e0baaca89c6c2d2a5abe
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks, committed to trunk in {{1371883db3d8bf7d7c54e0baaca89c6c2d2a5abe}}.
> 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-beta5
>
>
> 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]
