Thanks for flagging this, Mick!
No concern from me as all EOL dates for these distributions have long passed
and agreed that a NEWS entry is a good way to surface to users.
From: Mick Semb Wever
Sent: Friday, November 13, 2020 12:09 PM
To: dev@cassandra.
Sounds ok to be, but one small question; if a user is still running older
> versions, can they downgrade JNA or would this break? Basically, do our
> defaults/testing no longer support or would our source no longer be
> compatible?
>
The patch for CASSANDRA-16212 does not change the use of JNA,
Sounds ok to be, but one small question; if a user is still running older
versions, can they downgrade JNA or would this break? Basically, do our
defaults/testing no longer support or would our source no longer be
compatible?
On Fri, Nov 13, 2020 at 12:11 AM Mick Semb Wever wrote:
> CASSANDRA-1
CASSANDRA-16212 is about to be committed to trunk, upgrading JNA from 4.2.2
to 5.6.0.
This will mean that Cassandra 4.0 requires a glibc-2.7 or greater system.
Consequences of this will be the following distributions will no longer be
supported
- Centos 5 (and earlier), (EOL was 2017-03-31),
-
