Github user ijuma commented on a diff in the pull request:
https://github.com/apache/kafka-site/pull/107#discussion_r148303944
--- Diff: downloads.html ---
@@ -9,48 +9,75 @@
<p>
You can verify your download by following these <a
href="http://www.apache.org/info/verification.html";>procedures</a> and using
these <a href="http://kafka.apache.org/KEYS";>KEYS</a>.
</p>
+ <h3>1.0.0</h3>
- <h3>1.0.0</h3>
- <ul>
- <li>
- Released November 1,
2017
- </li>
- <li>
- <a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/RELEASE_NOTES.html";>Release
Notes</a>
- </li>
- <li>
- Source download: <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/1.0.0/kafka-1.0.0-src.tgz";>kafka-1.0.0-src.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka-1.0.0-src.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka-1.0.0-src.tgz.sha512";>sha512</a>)
- </li>
- <li>
- Binary downloads:
- <ul>
-
<li>Scala 2.11 - <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/1.0.0/kafka_2.11-1.0.0.tgz";>kafka_2.11-1.0.0.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.11-1.0.0.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.11-1.0.0.tgz.sha512";>sha512</a>)</li>
-
<li>Scala 2.12 - <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/1.0.0/kafka_2.12-1.0.0.tgz";>kafka_2.12-1.0.0.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.12-1.0.0.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.12-1.0.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.11 is recommended).
- </li>
- </ul>
+ <ul>
+ <li>
+ Released November 1, 2017
+ </li>
+ <li>
+ Source download: <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/1.0.0/kafka-1.0.0-src.tgz";>kafka-1.0.0-src.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka-1.0.0-src.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka-1.0.0-src.tgz.md5";>md5</a>)
+ </li>
+ <li>
+ Binary downloads:
+ <ul>
+ <li>Scala 2.11 - <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/1.0.0/kafka_2.11-1.0.0.tgz";>kafka_2.11-1.0.0.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.11-1.0.0.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.11-1.0.0.tgz.md5";>md5</a>)</li>
+ <li>Scala 2.12 - <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/1.0.0/kafka_2.12-1.0.0.tgz";>kafka_2.12-1.0.0.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.12-1.0.0.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/kafka_2.12-1.0.0.tgz.md5";>md5</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.11 is recommended).
+ </li>
+ </ul>
+
+ <p>
+ Kafka 1.0.0 is no mere bump of the version number. The Apache
Kafka Project Management Committee has packed a number of valuable enhancements
into the release. Here is a summary of a few of them:
+ </p>
+
+ <ul>
+ <li>
+ Since its introduction in version 0.10, the Streams API
has become hugely popular among Kafka users, including the likes of Pinterest,
Rabobank, Zalando, and The New York Times. In 1.0, the the API continues to
evolve at a healthy pace. To begin with, the builder API has been improved
(KIP-120). A new API has been added to expose the state of active tasks at
runtime (KIP-130). The new cogroup API makes it much easier to deal with
partitioned aggregates with fewer StateStores and fewer moving parts in your
code (KIP-150). Debuggability gets easier with enhancements to the print() and
writeAsText() methods (KIP-160). And if thatâs not enough, check out KIP-138
and KIP-161 too. For more on streams, check out the <a
href="https://kafka.apache.org/documentation/streams/";>Apache Kafka Streams</a>
documentation, including some helpful new tutorial videos.
+ </li>
+ <li>
+ Operating Kafka at scale requires that the system remain
observable, and to make that easier, weâve made a number of improvements to
metrics. These are too many to summarize without becoming tedious, but Connect
metrics have been significantly improved (KIP-196), a litany of new health
check metrics are now exposed (KIP-188), and we now have a global topic and
partition count (KIP-168). Check out KIP-164 and KIP-187 for even more.
+ </li>
+ <li>
+ We now support Java 9, leading, among other things, to
significantly faster TLS and CRC32C implementations. Over-the-wire encryption
will be faster now, which will keep Kafka fast and compute costs low when
encryption is enabled.
+ </li>
+ <li>
+ In keeping with the security theme, KIP-152 cleans up the
error handling on Simple Authentication Security Layer (SASL) authentication
attempts. Previously, some authentication error conditions were
indistinguishable from broker failures and were not logged in a clear way. This
is cleaner now.
+ </li>
+ <li>
+ Kafka can now tolerate disk failures better. Historically,
JBOD storage configurations have not been recommended, but the architecture has
nevertheless been tempting: after all, why not rely on Kafkaâs own
replication mechanism to protect against storage failure rather than using
RAID? With KIP-112, Kafka now handles disk failure more gracefully. A single
disk failure in a JBOD broker will not bring the entire broker down; rather,
the broker will continue serving any log files that remain on functioning disks.
+ </li>
+ <li>
+ Since release 0.11.0, the idempotent producer (which is
the producer used in the presence of a transaction, which of course is the
producer we use for exactly-once processing) required
max.in.flight.requests.per.connection to be equal to one. As anyone who has
written or tested a wire protocol can attest, this put an upper bound on
throughput. Thanks to KAFKA-5949, this can now be as large as five, relaxing
the throughput constraint quite a bit.
+ </li>
+ </ul>
+
+ <p>
+ For more information, please read the detailed <a
href="https://dist.apache.org/repos/dist/release/kafka/1.0.0/RELEASE_NOTES.html";>Release
Notes</a>.
+ </p>
+
+ <h3>0.11.0.1</h3>
+ <ul>
+ <li>
+ Released September 13, 2017
+ </li>
+ <li>
+ <a
href="https://archive.apache.org/dist/kafka/0.11.0.1/RELEASE_NOTES.html";>Release
Notes</a>
+ </li>
+ <li>
+ Source download: <a
href="https://www.apache.org/dyn/closer.cgi?path=/kafka/0.11.0.1/kafka-0.11.0.1-src.tgz";>kafka-0.11.0.1-src.tgz</a>
(<a
href="https://dist.apache.org/repos/dist/release/kafka/0.11.0.1/kafka-0.11.0.1-src.tgz.asc";>asc</a>,
<a
href="https://dist.apache.org/repos/dist/release/kafka/0.11.0.0/kafka-0.11.0.0-src.tgz.md5";>md5</a>)
--- End diff --
There's a bug where 0.11.0.0 is used in one case.
---
