Thanks for the heads-up. One follow-up: now that `fluss-rust` is part of the main repo, should we also standardize the issue/PR conventions for Rust-related work? For example: - Issues: use a `[rust]` title prefix and a `component: rust` label? - PRs: use `[rust]` as the title prefix, e.g. `[rust] Fix client build against updated proto`
Best regards, Yuxia ----- 原始邮件 ----- 发件人: "Nicholas" <[email protected]> 收件人: "dev" <[email protected]> 发送时间: 星期日, 2026年 7 月 05日 上午 9:48:29 主题: Re:[ANNOUNCE] The Rust, Python, C++ and Elixir clients are now part of Apache Fluss(Incubating) Thanks Anton for driving this. Great work! Regards, Nicholas Jiang ----- Original Message ----- From: "Anton Borisov" <[email protected]> To: [email protected] Sent: Sat, 4 Jul 2026 13:58:36 +0100 Subject: [ANNOUNCE] The Rust, Python, C++ and Elixir clients are now part of Apache Fluss(Incubating) The fluss-rust repo (and its Rust/Python/C++/Elixir clients) now lives in the main repo under fluss-rust, landed via a history-preserving merge: every original commit and author is intact, and git log/blame work on fluss-rust files. A few things worth knowing: - Your next git pull brings in fluss-rust/ plus ~320 imported commits, a larger-than-usual one-time fetch. - The Rust CI is path-gated (fluss-rust/** + proto), so Java-only PRs are unaffected. - fluss-rust now builds against fluss-rpc/.../FlussApi.proto, so a proto change can trip the Rust build, the rust CI lane will tell you. - apache/fluss-rust will be archived, please move any open PRs there over to apache/fluss under fluss-rust. Thanks to everyone who reviewed, and to the fluss-rust contributors whose history came along with it. -- Anton
