Hi Jark, Thanks for your input! Regarding the announcement blog post for the Fluss clients release, Keith Lee and Anton Borisov already have two PRs in progress to address this:
- Rust SDK introduction blog: https://github.com/apache/fluss/pull/2934 - Rust/Python/C++ client overview blog: https://github.com/apache/fluss/pull/2730 We'll work on getting these published to showcase the capabilities and use cases of the clients. Best, Yunhong (Swuferhong) On 2026/03/27 09:56:47 Jark Wu wrote: > +1 (binding) > > - Verified signatures and hashes: *OK* > - Build and compile the source code locally: *OK* > - Checked the LICENSE: *OK* > - Checked the DISCLAIMER: *OK* > - Checked ASF license header: *OK* > - Checked the NOTICE: should update to 2026 > > Additionally, the release of the first Fluss clients marks a > significant milestone for the project. We highly recommend publishing > an announcement blog post to showcase the capabilities of these > clients and highlight the specific use cases they enable. > > Best, > Jark > > On Thu, 26 Mar 2026 at 14:37, Jim Hu <[email protected]> wrote: > > > > Thanks Yunhong for driving this release. > > +1 > > > > - Signatures: OK > > - Checksum: OK > > - Build: OK > > - Dependencies license check: OK > > - Compatible licence of deps are documented: OK > > - DISCLAIMER exists: OK > > - ASF license headers: OK > > > > Sincerely, > > Yangyang > > > > yuxia <[email protected]> 于2026年3月26日周四 11:24写道： > > > > > Thanks Yunhong for driving this release. > > > +1 (binding) > > > > > > - Signatures: OK > > > - Checksum: OK > > > - Build: OK > > > - Dependencies license check: OK > > > - Compatible licence of deps are documented: OK > > > - DISCLAIMER exists: OK > > > - ASF license headers: OK > > > > > > > > > Best regards, > > > Yuxia > > > > > > ----- 原始邮件 ----- > > > 发件人: "Jean-Baptiste Onofré" <[email protected]> > > > 收件人: "dev" <[email protected]> > > > 发送时间: 星期四, 2026年 3 月 26日 上午 12:53:57 > > > 主题: [SPAM]Re: [VOTE] Release Apache Fluss clients (fluss-rust, > > > fluss-python, fluss-cpp) 0.1.0-incubating (RC1) > > > > > > +1 (binding) > > > > > > nit: for the vote, I would suggest to clarify we are voting on > > > fluss-rust, that includes the cpp/python bindings. Incubator PMC > > > members might misunderstand the "relation" between rust/cpp/python. > > > > > > I checked: > > > - source distribution (rust) > > > -- incubating is in the name/version > > > -- signature and checksum are good > > > -- DISCLAIMER is present > > > -- LICENSE is good, NOTICE should be updated to have copyright to 2026 > > > -- ASF header present in all expected files > > > -- No binary/compiled file found in the source distribution (the image > > > files are totally fine here) > > > > > > NB: I'm not able to verify binary distribution. For the next releases, > > > I suggest to include binary distribution on dist.apache.org for > > > review. > > > > > > Thanks ! > > > Regards > > > JB > > > > > > On Mon, Mar 23, 2026 at 2:13 PM yunhong Zheng <[email protected]> > > > wrote: > > > > > > > > Hi everyone, > > > > > > > > Please review and vote on release candidate #RC1 for Apache Fluss > > > > clients > > > > (fluss-rust, fluss-python, fluss-cpp) 0.1.0-incubating. > > > > > > > > [ ] +1 Approve the release > > > > [ ] +0 No opinion > > > > [ ] -1 Do not approve (please provide specific comments) > > > > > > > > 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 download, verify, and test. Verification steps are in > > > > https://clients.fluss.apache.org/release/verifying-a-release-candidate > > > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > > > approval with at least 3 PPMC affirmative votes (or as per project > > > policy). > > > > > > > > Thanks, > > > > Yunhong (Swuferhong) > > > >
