Hi everyone, Thanks, Attila, for taking care of the release management.
+1 I performed the following verification steps on RHEL 8.8 (x86_64) and RHEL 8.10 (x86_64): - Built C++ and Java code from source (RELEASE and DEBUG mode). - Ran C++ tests and all tests passed (Apart from environmental failures). - Verified that all tests passed successfully. Thanks, Abhishek On Mon, Nov 9, 2026 at 3:18 PM Alexey Serbin via dev <[email protected]> wrote: > > Thanks a lot for taking care of the release management for Kudu 1.18.2, > Attila! > > +1 > > I performed the following verification steps: > * Checked out the source code from the https://github.com/apache/kudu > mirror for the 1.18.2-RC1 tag > * Built the C++ (DEBUG, RELEASE) and Java source code at RHEL9.6 (Plow) > x86_64 > * Built the C++ (DEBUG, RELEASE) and Java source code at RHEL8.8 (Ootpa) > aarch64 Graviton 3 > * Built the C++ source code (DEBUG) at macOS 26.7.2 using XCode 26.6 > toolchain > * Ran C++ tests on RHEL9.6 (Plow) x86_64: all tests pass > * Ran C++ tests on RHEL8.8 (Ootpa) aarch64 Graviton 3: all tests pass > except for some scenarios in log_block_manager-test.txt (see > https://issues.apache.org/jira/browse/KUDU-3825 for details). > > In this context, I think we can ignore the test failures on aarch64 > described in KUDU-3825 > and address them separately: btw, those also manifest themselves in the > master branch > of the repo. IIUC, that's about rounding errors due to incorrect > assumptions on the FS/log > block size and alignment. We had addressed issues like that already (e.g., > see 976e9fc11), > but then there were updates related to the encryption-at-rest project, etc. > > > Kind regards, > > Alexey > > > > On Mon, Nov 9, 2026 at 6:19 AM Zoltan Chovan via dev <[email protected]> > wrote: > > > Hi everyone, > > > > Thanks Attila for putting this RC together. > > > > My steps on validating this RC: > > > > - I downloaded the source, and built the C++ and Java bits on a Ubuntu > > 22.04 machine in RELEASE mode > > - Ran C++, Java, Python tests > > - Confirmed that all tests passed, except one (curl_util-test - > > CurlUtilTest.TestTimeout) but that was due to a local DNS setup issue, I > > confirmed manually on dist-test that it passed for the gerrit build > > > > > > Based on this my vote is +1 > > > > Best regards, > > Zoltan > > > > > > On Sun, Nov 8, 2026 at 4:31 PM Attila Bukor via dev <[email protected]> > > wrote: > > > > > Hi everyone, > > > > > > The Apache Kudu team is happy to announce the first release candidate for > > > Apache > > > Kudu 1.18.2. > > > > > > This is a maintenance release on the latest 1.18 line that offers several > > > bug > > > fixes, including stability and security fixes since Apache Kudu 1.18.1. > > > > > > This is a source-only release. The artifacts have been staged here: > > > https://dist.apache.org/repos/dist/dev/kudu/1.18.2-RC1/ > > > > > > Java convenience binaries in the form of a Maven repository are staged > > > here: > > > https://repository.apache.org/content/repositories/orgapachekudu-1136 > > > > > > Linux (x86_64 built on CentOS 7) and macOS (aarch64 built on Tahoe > > 26.7.2) > > > test-only Kudu binary JAR artifacts are staged here: > > > https://repository.apache.org/content/repositories/orgapachekudu-1134 > > > > > > It is tagged in Git as 1.18.2-RC1: > > > https://github.com/apache/kudu/tree/1.18.2-RC1 > > > > > > The release notes can be found here: > > > https://github.com/apache/kudu/blob/1.18.2-RC1/docs/release_notes.adoc > > > > > > The KEYS file to verify the artifact signatures can be found here: > > > https://dist.apache.org/repos/dist/release/kudu/KEYS > > > > > > 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 > > > 17:00:00 > > > CET on Wednesday, 11/11/2026. > > > > > > Thank You, > > > Attila > > > > >
