stanislavkozlovski commented on code in PR #578:
URL: https://github.com/apache/kafka-site/pull/578#discussion_r1497321697
##########
blog.html:
##########
@@ -22,6 +22,125 @@
<!--#include virtual="includes/_nav.htm" -->
<div class="right">
<h1 class="content-title">Blog</h1>
+ <article>
+ <h2 class="bullet">
+ <a id="apache_kafka_370_release_announcement"></a>
+ <a href="#apache_kafka_370_release_announcement">Apache
Kafka 3.7.0 Release Announcement</a>
+ </h2>
+ February 2024 - Stanislav Kozlovski (<a
href="https://twitter.com/BdKozlovski";>@BdKozlovski</a>)
+ <p>We are proud to announce the release of Apache Kafka 3.7.0.
This release contains many new features and improvements. This blog post will
highlight some of the more prominent features. For a full list of changes, be
sure to check the <a
href="https://downloads.apache.org/kafka/3.7.0/RELEASE_NOTES.html";>release
notes</a>.</p>
+ <p>See the <a
href="https://kafka.apache.org/36/documentation.html#upgrade_3_7_0";>Upgrading
to 3.7.0 from any version 0.8.x through 3.6.x</a> section in the documentation
for the list of notable changes and detailed upgrade steps.</p>
+ <p>
+ In the last release, 3.6,
+ <a
href="https://kafka.apache.org/documentation/#kraft_zk_migration";>the ability
to migrate Kafka clusters from a ZooKeeper metadata system</a>
+ to a KRaft metadata system was ready for usage in
production environments with one caveat -- JBOD was not yet available for KRaft
clusters.
+ In this release, we are shipping an early access release
of JBOD in KRaft. (See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>
for details)
+ </p>
+ <p>
+ Additionally, client APIs released prior to Apache Kafka
2.1 are now marked deprecated in 3.7 and will be removed in Apache Kafka 4.0.
See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896</a>
for details and RPC versions that are now deprecated.
+ </p>
+ <p>
+ Java 11 support for the Kafka broker is also marked
deprecated in 3.7, and is planned to be removed in Kafka 4.0. See <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510";>KIP-1013</a>
for more details
Review Comment:
Not sure we should have this though. This is just deprecation. JDK 8 for
clients was deprecated a very long time ago, and will be removed with 4.0 too -
so they can't continue using JDK 8 after 4.0.
We should maybe say `Note that clients can continue to use JDK >= 11 to
connect to Kafka brokers.`? @ijuma can you chime in?
##########
blog.html:
##########
@@ -22,6 +22,125 @@
<!--#include virtual="includes/_nav.htm" -->
<div class="right">
<h1 class="content-title">Blog</h1>
+ <article>
+ <h2 class="bullet">
+ <a id="apache_kafka_370_release_announcement"></a>
+ <a href="#apache_kafka_370_release_announcement">Apache
Kafka 3.7.0 Release Announcement</a>
+ </h2>
+ February 2024 - Stanislav Kozlovski (<a
href="https://twitter.com/BdKozlovski";>@BdKozlovski</a>)
+ <p>We are proud to announce the release of Apache Kafka 3.7.0.
This release contains many new features and improvements. This blog post will
highlight some of the more prominent features. For a full list of changes, be
sure to check the <a
href="https://downloads.apache.org/kafka/3.7.0/RELEASE_NOTES.html";>release
notes</a>.</p>
+ <p>See the <a
href="https://kafka.apache.org/36/documentation.html#upgrade_3_7_0";>Upgrading
to 3.7.0 from any version 0.8.x through 3.6.x</a> section in the documentation
for the list of notable changes and detailed upgrade steps.</p>
+ <p>
+ In the last release, 3.6,
+ <a
href="https://kafka.apache.org/documentation/#kraft_zk_migration";>the ability
to migrate Kafka clusters from a ZooKeeper metadata system</a>
+ to a KRaft metadata system was ready for usage in
production environments with one caveat -- JBOD was not yet available for KRaft
clusters.
+ In this release, we are shipping an early access release
of JBOD in KRaft. (See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>
for details)
+ </p>
+ <p>
+ Additionally, client APIs released prior to Apache Kafka
2.1 are now marked deprecated in 3.7 and will be removed in Apache Kafka 4.0.
See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896</a>
for details and RPC versions that are now deprecated.
+ </p>
+ <p>
+ Java 11 support for the Kafka broker is also marked
deprecated in 3.7, and is planned to be removed in Kafka 4.0. See <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510";>KIP-1013</a>
for more details
Review Comment:
Not sure we should have this though. This is just deprecation. JDK 8 for
clients was deprecated a very long time ago, and will be removed with 4.0 too -
so they can't continue using JDK 8 after 4.0.
We should maybe say `Note that clients will continue to be able to use JDK
>= 11 to connect to Kafka brokers.`? @ijuma can you chime in?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
