Thanks a lot for taking care of release management, Yingchun!

+1 for releasing Kudu 1.17.0 from the 1.17.0-RC2 tag in the git repository.

I did the following to verify the functionality of the RC2 candidate on
CentOS 7.9:
  * built C++ (DEBUG and RELEASE configurations) and Java parts of the
project: success
  * ran the C++ tests: see below for details
  * ran a smoke test scenario using the 'kudu perf loadgen' CLI tool against
    a small POC cluster (RELEASE binaries): success

The only failed test scenarios were in the test suites listed below, and
all that
seems to be test-only issues so far (long startup times for the Ranger
process, etc.):
  161:master_authz-itest.4
  162:master_authz-itest.5
  163:master_authz-itest.6
  164:master_authz-itest.7
  194:security-itest

I did the following to verify the functionality of the RC2 candidate on
RHEL 8.8:
  * built C++ (DEBUG and RELEASE configurations) and Java parts of the
project: success
  * ran the C++ tests (DEBUG): see below for details
  * ran a smoke test scenario using the 'kudu perf loadgen' CLI tool against
    a small POC cluster (RELEASE binaries): success

The only failed test scenarios were in the test suites listed below, and
all that
seems to be test-only issues so far (long startup times for the Ranger
process, etc.):
  161:master_authz-itest.4
  162:master_authz-itest.5
  163:master_authz-itest.6
  164:master_authz-itest.7
  173:master-stress-test.0
  194:security-itest
  286:subprocess_server-test
  453:threadpool-test

I did the following to verify the functionality of the RC2 candidate on
Ubuntu 20.04.6 LTS (focal):
  * built C++ (DEBUG and RELEASE configurations) and Java parts of the
project: success
  * ran the C++ tests: see below for details
  * ran a smoke test scenario using the 'kudu perf loadgen' CLI tool against
    a small POC cluster (RELEASE binaries): success

The only failed test scenarios were in the test suites listed below, and
all that
seems to be test-only issues so far (Ranger KMS-related issues):
  194:security-itest

For the test scenarios that failed on all the platforms I tested: that are
the recently
introduced ones involving Ranger KMS.  That seems to be a test-only issue
as well,
and I filed https://issues.apache.org/jira/browse/KUDU-3507 to track that.
I'll try
to report and probably also fix the other test-only issues reported above
when I have a chance.


Kind regards,

Alexey

On Sun, Aug 27, 2023 at 8:00 AM Yingchun Lai <laiyingc...@apache.org> wrote:

> Hello Kudu devs!
>
> The Apache Kudu team is happy to announce the second release candidate
> for Apache
> Kudu 1.17.0.
>
> Apache Kudu 1.17.0 is a minor release that offers many improvements and
> fixes
> since Apache Kudu 1.16.0.
>
> This is a source-only release. The artifacts have been staged here:
> https://dist.apache.org/repos/dist/dev/kudu/1.17.0-RC2
>
> Java convenience binaries in the form of a Maven repository are staged
> here:
> https://repository.apache.org/content/repositories/orgapachekudu-1113
>
> Linux (built on CentOS 7) and macOS (built on Ventura) test-only Kudu
> binary
> JAR artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapachekudu-1112
> https://repository.apache.org/content/repositories/orgapachekudu-1114
>
> It is tagged in Git as 1.17.0-RC2 and signed with my key (found in the
> KEYS file
> below). Its commit hash is 4a7700bdcff2bf2afe4e46efdb8874484fd66b86 you can
> check it out from ASF Gitbox or the official GitHub mirror:
>
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=4a7700bdcff2bf2afe4e46efdb8874484fd66b86
> https://github.com/apache/kudu/releases/tag/1.17.0-RC2
>
> The KEYS file to verify the artifact and tag signatures can be found here:
> https://dist.apache.org/repos/dist/release/kudu/KEYS
>
> The release notes can be found here:
> https://github.com/apache/kudu/blob/1.17.0-RC2/docs/release_notes.adoc
>
> I'd suggest going through the release notes, building Kudu, and running
> the unit
> tests. Testing out the Maven repo would also be appreciated. Also, it's
> worth
> running Kudu Java tests against kudu-binary JAR artifact as described in
> the
> commit message here:
>
> https://github.com/apache/kudu/commit/8a6faaa93f3e206ac75e8087731daccaf7ab646a
>
> The vote will run until a majority[1] is achieved, but at least until
> Wednesday
> Aug 30th 20:00:00 UTC 2023.
>
> Thank You,
> Yingchun Lai
>
> [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
>

Reply via email to