Hi, for the sake of the ZK project I hope they don’t go down that route (I’ve already exposed my concern on the ZK mailing list) since there are many application in the wild that will be stuck on an older version of ZK.
From my own company point of view we already support Java11 in all our applications so we are not directly impacted (and we have upgrade path for older versions to provide to our customers). Since BK is a much younger project I don’t expect that the move to Java11 will be a problem. I think that Pulsar still supports Java8. Even in the case that the ZK team will decide to not go down that route (and still maintain Java8 support) I think that we should plan that move for BK to prevent a similar situation in the future (naturally, as soon as Pulsar will drop support for Java8). Alessandro Luccaroni Platform Manager @ Diennea - MagNews Tel.: (+39) 0546 066100 Int. 924 - Mob.: (+39) 393 7273519 Viale G.Marconi 30/14 - 48018 Faenza (RA) - Italy Da: Enrico Olivelli <eolive...@gmail.com> Inviato: mercoledì 21 ottobre 2020 11:24 A: Bookkeeper-Dev <dev@bookkeeper.apache.org>; user <u...@bookkeeper.apache.org> Oggetto: Moving BooKeeper to JDK11 Hello guys, (crossposting to user and dev) In the ZooKeeper project there is an open discussion about moving ZooKeeper 3.7 to JDK11 and basically dropping support for JDK8 in the client. If they go that route we will probably need to move in the same direction. How do you feel about this? Is JDK8 still required for your applications ? Best regards Enrico ________________________________ CONFIDENTIALITY & PRIVACY NOTICE This e-mail (including any attachments) is strictly confidential and may also contain privileged information. If you are not the intended recipient you are not authorised to read, print, save, process or disclose this message. If you have received this message by mistake, please inform the sender immediately and destroy this e-mail, its attachments and any copies. Any use, distribution, reproduction or disclosure by any person other than the intended recipient is strictly prohibited and the person responsible may incur in penalties. The use of this e-mail is only for professional purposes; there is no guarantee that the correspondence towards this e-mail will be read only by the recipient, because, under certain circumstances, there may be a need to access this email by third subjects belonging to the Company.
