+1 (non-binding)

Best,
Jark Wu

On Mon, 30 Mar 2026 at 17:17, yuxia <[email protected]> wrote:
>
> +1 (non-binding)
>
> Best regards,
> Yuxia
>
> ----- 原始邮件 -----
> 发件人: "Jean-Baptiste Onofré" <[email protected]>
> 收件人: "general" <[email protected]>
> 发送时间: 星期一, 2026年 3 月 30日 下午 5:12:55
> 主题: [SPAM]Re: [VOTE] Release Apache Fluss (fluss-rust) 0.1.0-incubating
>
> +1 (binding)
>
> Casting my vote from the podling.
>
> Regards
> JB
>
> On Mon, Mar 30, 2026 at 3:52 AM yunhong Zheng <[email protected]>
> wrote:
>
> > Hi IPMC,
> >
> > The Fluss community has voted to release Apache Fluss (fluss-rust)
> > 0.1.0-incubating. This release includes the Rust implementation along with
> > its C++ and Python bindings. The community vote thread and results are
> > available at:
> > * https://lists.apache.org/thread/s6syqh16ly61rj9fn71zq76jzrkgrjzs
> >
> > The release candidate (source distribution) is available at:
> > *
> >
> > https://dist.apache.org/repos/dist/dev/incubator/fluss/fluss-rust-0.1.0-incubating-rc1/
> >
> > KEYS for signature verification:
> > * https://downloads.apache.org/incubator/fluss/KEYS
> >
> > Git tag:
> > * https://github.com/apache/fluss-rust/releases/tag/v0.1.0-incubating-rc1
> >
> > PyPI (release) / TestPyPI (RC):
> > * https://pypi.org/project/pyfluss/
> > * https://test.pypi.org/project/pyfluss/
> >
> > Please review and vote on this release. Verification steps are in:
> > https://clients.fluss.apache.org/release/verifying-a-release-candidate
> >
> > [ ] +1 Approve the release
> > [ ] +0 No opinion
> > [ ] -1 Do not approve (please provide specific comments)
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval with at least 3 IPMC affirmative votes.
> >
> > Thanks,
> > Yunhong (Swuferhong)
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

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

Reply via email to