+1(non-binding)

Best,
Shuxin Pan

On Thu, Feb 26, 2026 at 11:30 AM yuxia <[email protected]> wrote:
>
> Hi everyone,
>
> The Apache Fluss community has voted and approved the release of
> Apache Fluss 0.9.0-incubating (RC2). We now kindly request the IPMC
> members to review and vote for this release.
>
> Apache Fluss (Incubating) - A streaming storage built for real-time analytics 
> & AI which can serve as the real-time data layer for Lakehouse architectures.
>
> Fluss community vote thread:
> * https://lists.apache.org/thread/3c8w6ofrssjxrpvz85pkm2n2kx1gyzxd
>
> Vote result thread:
> * https://lists.apache.org/thread/ghlr851qc9mh3vly28904j8k6yp90tw4
>
> The release candidate:
> * 
> https://dist.apache.org/repos/dist/dev/incubator/fluss/fluss-0.9.0-incubating-rc2/
>
> The helm chart release package:
> * 
> https://dist.apache.org/repos/dist/dev/incubator/fluss/helm-chart/0.9.0-incubating-rc2/
>
> Git tag for the release:
> * https://github.com/apache/fluss/releases/tag/v0.9.0-incubating-rc2
>
> Git commit for the release:
> * 
> https://github.com/apache/fluss/commit/29dae4717f3dddd7fd89473450803ea50e0cadaf
>
> Maven staging repository:
> * https://repository.apache.org/content/repositories/orgapachefluss-1005/
>
> The artifacts signed with PGP key [56A9F259A4C18F9C], corresponding to
> [[email protected]], that can be found in keys file:
> https://downloads.apache.org/incubator/fluss/KEYS
>
> Please download, verify and test.
>
> Please vote in the next 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Fluss, please see https://fluss.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
>
> Best regards,
> Yuxia

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to