[
https://issues.apache.org/jira/browse/CASSANDRA-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846941#comment-17846941
]
Stefan Miklosovic commented on CASSANDRA-18712:
-----------------------------------------------
What I would personally do is that I would wait with this ticket until 5.1 is
imminent. The reason for doing so is that while we release 5.1, we will most
likely want to update these dependencies again because they are being actively
developed. I do not see any critical reason why should be this merged _right
now_ - only if we want to enable people to test trunk on s390x as mentioned in
the description that this is a blocker for them, but we do not officially
support that architecture anyway ...
> Update Chronicle bytes
> ----------------------
>
> Key: CASSANDRA-18712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18712
> Project: Cassandra
> Issue Type: Task
> Components: Dependencies
> Reporter: Nayana Thorat
> Assignee: Nayana Thorat
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [https://github.com/OpenHFT/Chronicle-Bytes/pull/485] fixes test failures of
> cassandra on s390x.
> This patch is merged and available in chronicle-bytes-2.24ea7 and later
> releases.
> possible to update Chronicle bytes and related pkg versions in Cassandra
> (https://github.com/apache/cassandra/blob/trunk/.build/parent-pom-template.xml)?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
