+1

1. Verified the GPG signature, MD5 checksum, and SHA512 checksum for both
source and binary tarballs
- 2. Built successfully from the source tarball.
- 3. Compared the source tarball with the repository at tag ozone-2.1.2-RC1
and confirmed that they are identical.
- 4. Verified the version with `bin/ozone version`. It reports 2.1.2 as
expected, and corresponds to the same commit as 2.1.2-RC1.
-

Wei-Chiu Chuang <[email protected]> 于2026年8月30日周日 06:01写道:

> Hi all,
>
> I would like to call a vote on releasing Apache Ozone 2.1.2 RC1.
>
> Please use a separate [DISCUSS] thread for anything but votes.
>
> This maintenance release is based on commit:
>   8a1ae0edbb6a797b9f1d83ad5fc87de4234c1f37
>
> Tag:
>   https://github.com/apache/ozone/releases/tag/ozone-2.1.2-RC1
>
> Resolved issues (fixVersion = 2.1.2):
>
> https://issues.apache.org/jira/issues/?jql=project%3DHDDS+AND+fixVersion%3D2.1.2
>
> Release notes (pending merge after vote):
>   https://github.com/apache/ozone-site/pull/543
>
> Note that we are voting upon the source (tag); binaries are provided for
> convenience.
>
> Source and binary files:
>   https://dist.apache.org/repos/dist/dev/ozone/2.1.2-rc1/
>
> Maven staging repository:
>   https://repository.apache.org/content/repositories/orgapacheozone-1084/
>
> Release artifacts are signed with the following key:
>   https://dist.apache.org/repos/dist/release/ozone/KEYS
>
> Signing key fingerprint:
>   A6C449A59A2551FA7B6C7CF33ED23305D7631918
>
> Known test issue (no runtime impact):
>   CI may intermittently fail
> TestOzoneRpcClient#testOverWriteKeyWithAndWithOutVersioning
>   due to a known test timing issue (HDDS-13861, fixed on master). This
> does not affect
>   Ozone runtime behavior.
>
> Please download, test, and vote by September 5, 2026.
>
> [ ] +1 Release
> [ ] +0
> [ ] -1 Do not release (reason: )
>
> Thanks,
> Wei-Chiu Chuang
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to