Hi,

sorry for forgetting to import the new key, so I need to recall my previous
vote mail.

+1 (binding)

I checked the following items:

- [x] Download links are valid
- [x] All expected release artifacts are present (source release + .asc +
.sha512)
- [x] Checksums and PGP signatures are valid
- [x] LICENSE and NOTICE files are correct
- [x] No SNAPSHOT dependencies found
- [x] No unexpected binary files in source
- [x] All source files have ASF license headers (RAT check passed)
- [x] Version number in pom.xml is consistent (2.3.0)
- [x] Source code compiles successfully

Build:
- Source compilation: SUCCESS (6s)

Test environment:
- OS: macOS-26.4.1-arm64-arm-64bit
- JDK: openjdk version "21.0.2" 2024-01-16
- Maven: Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)

On Mon, Apr 20, 2026 at 8:47 PM Hongzhi Gao <[email protected]> wrote:

> Hi all,&nbsp;
>
>
> Apache TsFile 2.3.0 has been staged under [2] and it’s time to vote on
> accepting it for release. All Maven artifacts are available under [1].
> Voting will be open for 72hr. A minimum of 3 binding +1 votes and more
> binding +1 than binding -1 are required to pass.&nbsp;
>
>
> Release tag: v2.3.0&nbsp;
> Hash for the release tag: 7d4a4faf1cf4b634748daf1f4f5b39d4b23822df
>
> Before voting +1, PMC members are required to download the signed source
> code package, compile it as provided, and test the resulting executable on
> their own platform, along with also verifying that the package meets the
> requirements of the ASF policy on releases. [3]&nbsp;
>
>
> [ ] +1 accept (indicate what you validated)
> [ ] -1 reject (explanation required)&nbsp;
> &nbsp;
> [1]
> https://repository.apache.org/content/repositories/orgapachetsfile-1025/
> [2] https://dist.apache.org/repos/dist/dev/tsfile/2.3.0/rc1/
> [3] https://www.apache.org/dev/release.html#approving-a-release&nbsp;
> [4]
> https://dist.apache.org/repos/dist/dev/tsfile/2.3.0/rc1/RELEASE_NOTES.md&nbsp
> ;
> [5] https://dist.apache.org/repos/dist/dev/tsfile/KEYS
>
>
>  Best, Hongzhi Gao
>
>
>
>
> Hongzhi&nbsp;Gao
> [email protected]

Reply via email to