This is an automated email from the ASF dual-hosted git repository. alexey pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/master by this push: new 9990d0193 Bump version to 1.18.0-SNAPSHOT 9990d0193 is described below commit 9990d0193a32d3f63783ed13636d92114c5da121 Author: Yingchun Lai <laiyingc...@apache.org> AuthorDate: Sat Feb 18 14:30:56 2023 +0800 Bump version to 1.18.0-SNAPSHOT Change-Id: I8122317c2fadf5b9f7b844be6c6ddec54aca91d6 Reviewed-on: http://gerrit.cloudera.org:8080/19513 Tested-by: Alexey Serbin <ale...@apache.org> Reviewed-by: Alexey Serbin <ale...@apache.org> --- docs/release_notes.adoc | 56 ++++++++++++++++++++++++------------------------- version.txt | 2 +- 2 files changed, 29 insertions(+), 29 deletions(-) diff --git a/docs/release_notes.adoc b/docs/release_notes.adoc index 14655fa21..5eca29a64 100644 --- a/docs/release_notes.adoc +++ b/docs/release_notes.adoc @@ -16,7 +16,7 @@ // under the License. [[release_notes]] -= Apache Kudu 1.17.0 Release Notes += Apache Kudu 1.18.0 Release Notes :author: Kudu Team :imagesdir: ./images @@ -28,80 +28,80 @@ :sectlinks: :experimental: -[[rn_1.17.0_upgrade_notes]] +[[rn_1.18.0_upgrade_notes]] == Upgrade Notes -[[rn_1.17.0_obsoletions]] +[[rn_1.18.0_obsoletions]] == Obsoletions -[[rn_1.17.0_deprecations]] +[[rn_1.18.0_deprecations]] == Deprecations Support for Python 2.x and Python 3.4 and earlier is deprecated and may be removed in the next minor release. -[[rn_1.17.0_new_features]] +[[rn_1.18.0_new_features]] == New features -[[rn_1.17.0_improvements]] +[[rn_1.18.0_improvements]] == Optimizations and improvements -[[rn_1.17.0_fixed_issues]] +[[rn_1.18.0_fixed_issues]] == Fixed Issues -[[rn_1.17.0_wire_compatibility]] +[[rn_1.18.0_wire_compatibility]] == Wire Protocol compatibility -Kudu 1.17.0 is wire-compatible with previous versions of Kudu: +Kudu 1.18.0 is wire-compatible with previous versions of Kudu: -* Kudu 1.17 clients may connect to servers running Kudu 1.0 or later. If the client uses +* Kudu 1.18 clients may connect to servers running Kudu 1.0 or later. If the client uses features that are not available on the target server, an error will be returned. -* Rolling upgrade between Kudu 1.16 and Kudu 1.17 servers is believed to be possible +* Rolling upgrade between Kudu 1.17 and Kudu 1.18 servers is believed to be possible though has not been sufficiently tested. Users are encouraged to shut down all nodes in the cluster, upgrade the software, and then restart the daemons on the new version. -* Kudu 1.0 clients may connect to servers running Kudu 1.17 with the exception of the +* Kudu 1.0 clients may connect to servers running Kudu 1.18 with the exception of the below-mentioned restrictions regarding secure clusters. The authentication features introduced in Kudu 1.3 place the following limitations -on wire compatibility between Kudu 1.17 and versions earlier than 1.3: +on wire compatibility between Kudu 1.18 and versions earlier than 1.3: -* If a Kudu 1.17 cluster is configured with authentication or encryption set to "required", +* If a Kudu 1.18 cluster is configured with authentication or encryption set to "required", clients older than Kudu 1.3 will be unable to connect. -* If a Kudu 1.17 cluster is configured with authentication and encryption set to "optional" +* If a Kudu 1.18 cluster is configured with authentication and encryption set to "optional" or "disabled", older clients will still be able to connect. -[[rn_1.17.0_incompatible_changes]] -== Incompatible Changes in Kudu 1.17.0 +[[rn_1.18.0_incompatible_changes]] +== Incompatible Changes in Kudu 1.18.0 -[[rn_1.17.0_client_compatibility]] +[[rn_1.18.0_client_compatibility]] === Client Library Compatibility -* The Kudu 1.17 Java client library is API- and ABI-compatible with Kudu 1.16. Applications - written against Kudu 1.16 will compile and run against the Kudu 1.17 client library and +* The Kudu 1.18 Java client library is API- and ABI-compatible with Kudu 1.17. Applications + written against Kudu 1.17 will compile and run against the Kudu 1.18 client library and vice-versa. -* The Kudu 1.17 {cpp} client is API- and ABI-forward-compatible with Kudu 1.16. - Applications written and compiled against the Kudu 1.16 client library will run without - modification against the Kudu 1.17 client library. Applications written and compiled - against the Kudu 1.17 client library will run without modification against the Kudu 1.16 +* The Kudu 1.18 {cpp} client is API- and ABI-forward-compatible with Kudu 1.17. + Applications written and compiled against the Kudu 1.17 client library will run without + modification against the Kudu 1.18 client library. Applications written and compiled + against the Kudu 1.18 client library will run without modification against the Kudu 1.17 client library. -* The Kudu 1.17 Python client is API-compatible with Kudu 1.16. Applications - written against Kudu 1.16 will continue to run against the Kudu 1.17 client +* The Kudu 1.18 Python client is API-compatible with Kudu 1.17. Applications + written against Kudu 1.17 will continue to run against the Kudu 1.18 client and vice-versa. -[[rn_1.17.0_known_issues]] +[[rn_1.18.0_known_issues]] == Known Issues and Limitations Please refer to the link:known_issues.html[Known Issues and Limitations] section of the documentation. -[[rn_1.17.0_contributors]] +[[rn_1.18.0_contributors]] == Contributors [[resources_and_next_steps]] diff --git a/version.txt b/version.txt index bd19712e6..18b1037a0 100644 --- a/version.txt +++ b/version.txt @@ -1 +1 @@ -1.17.0-SNAPSHOT +1.18.0-SNAPSHOT