[kafka] branch 3.1 updated: MINOR: bump version in kraft readme (#11596)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dajac pushed a commit to branch 3.1
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/3.1 by this push:
     new 5a99bef  MINOR: bump version in kraft readme (#11596)
5a99bef is described below

commit 5a99befccedd1956661ae599916264150c9792e5
Author: Luke Chen <sh...@gmail.com>
AuthorDate: Mon Dec 20 17:32:23 2021 +0800

    MINOR: bump version in kraft readme (#11596)
    
    Reviewers: Colin P. McCabe <cm...@apache.org>, David Jacot <dj...@confluent.io>
---
 config/kraft/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/kraft/README.md b/config/kraft/README.md
index 88de718..80bc8ca 100644
--- a/config/kraft/README.md
+++ b/config/kraft/README.md
@@ -4,7 +4,7 @@ KRaft (aka KIP-500) mode Preview Release
 # Introduction
 It is now possible to run Apache Kafka without Apache ZooKeeper!  We call this the [Kafka Raft metadata mode](https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum), typically shortened to `KRaft mode`.
 `KRaft` is intended to be pronounced like `craft` (as in `craftsmanship`). It is currently *PREVIEW AND SHOULD NOT BE USED IN PRODUCTION*, but it
-is available for testing in the Kafka 3.0 release.
+is available for testing in the Kafka 3.1 release.
 
 When the Kafka cluster is in KRaft mode, it does not store its metadata in ZooKeeper.  In fact, you do not have to run ZooKeeper at all, because it stores its metadata in a KRaft quorum of controller nodes.
 
@@ -14,8 +14,8 @@ Most important of all, KRaft mode is more scalable.  We expect to be able to [su
 # Quickstart
 
 ## Warning
-KRaft mode in Kafka 3.0 is provided for testing only, *NOT* for production.  We do not yet support upgrading existing ZooKeeper-based Kafka clusters into this mode.  In fact, when Kafka 3.1 is released,
-it may not be possible to upgrade your KRaft clusters from 3.0 to 3.1.  There may be bugs, including serious ones.  You should *assume that your data could be lost at any time* if you try the preview release of KRaft mode.
+KRaft mode in Kafka 3.1 is provided for testing only, *NOT* for production.  We do not yet support upgrading existing ZooKeeper-based Kafka clusters into this mode.  
+There may be bugs, including serious ones.  You should *assume that your data could be lost at any time* if you try the preview release of KRaft mode.
 
 ## Generate a cluster ID
 The first step is to generate an ID for your new cluster, using the kafka-storage tool: