ijuma commented on a change in pull request #277:
URL: https://github.com/apache/kafka-site/pull/277#discussion_r465133944
##########
File path: 26/upgrade.html
##########
@@ -19,6 +19,48 @@
<script id="upgrade-template" type="text/x-handlebars-template">
+<h4><a id="upgrade_2_6_0" href="#upgrade_2_6_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x, 1.0.x, 1.1.x, 2.0.x or 2.1.x or 2.2.x,
2.3.x, 2.4.x, 2.5.x to 2.6.0</a></h4>
Review comment:
This got pretty unwieldy. Can we simplify it somehow?
##########
File path: 26/upgrade.html
##########
@@ -41,6 +83,48 @@ <h5><a id="upgrade_260_notable"
href="#upgrade_260_notable">Notable changes in 2
</li>
</ul>
+<h4><a id="upgrade_2_5_0" href="#upgrade_2_5_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x, 1.0.x, 1.1.x, 2.0.x or 2.1.x or 2.2.x,
2.3.x, 2.4.x to 2.5.0</a></h4>
Review comment:
Whatever we decide for 2.6.0, we could maybe apply here too.
##########
File path: downloads.html
##########
@@ -5,12 +5,55 @@
<div class="right">
<h1>Download</h1>
- <p>2.5.0 is the latest release. The current stable version is 2.5.0.</p>
+ <p>2.6.0 is the latest release. The current stable version is 2.6.0.</p>
<p>
You can verify your download by following these <a
href="https://www.apache.org/info/verification.html";>procedures</a> and using
these <a href="https://www.apache.org/dist/kafka/KEYS";>KEYS</a>.
</p>
+ <span id="2.6.0"></span>
+ <h3 class="download-version">2.6.0<a href="#2.6.0"><i class="fas fa-link "
style="color:#053ce2"></i></a></h3>
+ <ul>
+ <li>
+ Released Aug 3, 2020
+ </li>
+ <li>
+ <a
href="https://www.apache.org/dist/kafka/2.6.0/RELEASE_NOTES.html";>Release
Notes</a>
+ </li>
+ <li>
+ Source download: <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/2.6.0/kafka-2.6.0-src.tgz";>kafka-2.6.0-src.tgz</a>
(<a
href="https://www.apache.org/dist/kafka/2.6.0/kafka-2.6.0-src.tgz.asc";>asc</a>,
<a
href="https://www.apache.org/dist/kafka/2.6.0/kafka-2.6.0-src.tgz.sha512";>sha512</a>)
+ </li>
+ <li>
+ Binary downloads:
+ <ul>
+ <li>Scala 2.12 - <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/2.6.0/kafka_2.12-2.6.0.tgz";>kafka_2.12-2.6.0.tgz</a>
(<a
href="https://www.apache.org/dist/kafka/2.6.0/kafka_2.12-2.6.0.tgz.asc";>asc</a>,
<a
href="https://www.apache.org/dist/kafka/2.6.0/kafka_2.12-2.6.0.tgz.sha512";>sha512</a>)</li>
+ <li>Scala 2.13 - <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/2.6.0/kafka_2.13-2.6.0.tgz";>kafka_2.13-2.6.0.tgz</a>
(<a
href="https://www.apache.org/dist/kafka/2.6.0/kafka_2.13-2.6.0.tgz.asc";>asc</a>,
<a
href="https://www.apache.org/dist/kafka/2.6.0/kafka_2.13-2.6.0.tgz.sha512";>sha512</a>)</li>
+ </ul>
+ We build for multiple versions of Scala. This only matters if you
are using Scala and you want a version
+ built for the same Scala version you use. Otherwise any version
should work (2.13 is recommended).
+ </li>
+ </ul>
+
+ <p>
+ Kafka 2.6.0 includes a number of significant new features. Here is a
summary of some notable changes:
Review comment:
Let's add a line for the performance improvements please.
##########
File path: 26/upgrade.html
##########
@@ -19,6 +19,48 @@
<script id="upgrade-template" type="text/x-handlebars-template">
+<h4><a id="upgrade_2_6_0" href="#upgrade_2_6_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x, 1.0.x, 1.1.x, 2.0.x or 2.1.x or 2.2.x,
2.3.x, 2.4.x, 2.5.x to 2.6.0</a></h4>
+
+<p><b>If you are upgrading from a version prior to 2.1.x, please see the note
below about the change to the schema used to store consumer offsets.
+ Once you have changed the inter.broker.protocol.version to the latest
version, it will not be possible to downgrade to a version prior to 2.1.</b></p>
+
+<p><b>For a rolling upgrade:</b></p>
+
+<ol>
+ <li> Update server.properties on all brokers and add the following
properties. CURRENT_KAFKA_VERSION refers to the version you
+ are upgrading from. CURRENT_MESSAGE_FORMAT_VERSION refers to the
message format version currently in use. If you have previously
+ overridden the message format version, you should keep its current
value. Alternatively, if you are upgrading from a version prior
+ to 0.11.0.x, then CURRENT_MESSAGE_FORMAT_VERSION should be set to
match CURRENT_KAFKA_VERSION.
+ <ul>
+ <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g.
0.10.0, 0.11.0, 1.0, 2.0, 2.2).</li>
+ <li>log.message.format.version=CURRENT_MESSAGE_FORMAT_VERSION
(See <a href="#upgrade_10_performance_impact">potential performance impact
+ following the upgrade</a> for the details on what this
configuration does.)</li>
+ </ul>
+ If you are upgrading from version 0.11.0.x or above, and you have not
overridden the message format, then you only need to override
+ the inter-broker protocol version.
+ <ul>
+ <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (0.11.0,
1.0, 1.1, 2.0, 2.1, 2.2, 2.3).</li>
Review comment:
Maybe worth having `e.g.` here too since this list is not exhaustive
anymore. It was at some point before.
##########
File path: 26/upgrade.html
##########
@@ -41,6 +83,48 @@ <h5><a id="upgrade_260_notable"
href="#upgrade_260_notable">Notable changes in 2
</li>
</ul>
+<h4><a id="upgrade_2_5_0" href="#upgrade_2_5_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x, 1.0.x, 1.1.x, 2.0.x or 2.1.x or 2.2.x,
2.3.x, 2.4.x to 2.5.0</a></h4>
+
+<p><b>If you are upgrading from a version prior to 2.1.x, please see the note
below about the change to the schema used to store consumer offsets.
+ Once you have changed the inter.broker.protocol.version to the latest
version, it will not be possible to downgrade to a version prior to 2.1.</b></p>
+
+<p><b>For a rolling upgrade:</b></p>
+
+<ol>
+ <li> Update server.properties on all brokers and add the following
properties. CURRENT_KAFKA_VERSION refers to the version you
+ are upgrading from. CURRENT_MESSAGE_FORMAT_VERSION refers to the
message format version currently in use. If you have previously
+ overridden the message format version, you should keep its current
value. Alternatively, if you are upgrading from a version prior
+ to 0.11.0.x, then CURRENT_MESSAGE_FORMAT_VERSION should be set to
match CURRENT_KAFKA_VERSION.
+ <ul>
+ <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g.
0.10.0, 0.11.0, 1.0, 2.0, 2.2).</li>
+ <li>log.message.format.version=CURRENT_MESSAGE_FORMAT_VERSION
(See <a href="#upgrade_10_performance_impact">potential performance impact
+ following the upgrade</a> for the details on what this
configuration does.)</li>
+ </ul>
+ If you are upgrading from version 0.11.0.x or above, and you have not
overridden the message format, then you only need to override
+ the inter-broker protocol version.
+ <ul>
+ <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (0.11.0,
1.0, 1.1, 2.0, 2.1, 2.2, 2.3).</li>
Review comment:
Same as the comment for 2.6.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
