Hello dev! My team and I started working on the TLS implementation. We split the work into 9 contributions: https://github.com/apache/fluss/issues/3786. We have the first PR out: https://github.com/apache/fluss/pull/3813.
We will follow up with the other 8 contributions. We want to avoid impacting the 1.0 release, and I see 2 paths forward: 1. merge the partial feature with @Experimental on the user-exposed configs 2. Create a base branch feat-tls from main now so that we can merge all PRs there, when the time comes (post feature freeze and release-1.0 is live), we open a big PR from feat-tls to main to merge all the contributions without squashing commits to respect attributions. Hopefully the rebase on top of latest main won't be painful. I personally lean towards the second choice to avoid exposing the partial feature in 1.0. Additionally, with this email, we want to raise awareness and find a committer/PMC that is willing to review our work :) Thank you! -- Lorenzo Affetti Team Leader of Stream Storage [email protected] www.ververica.com ------------------------------ <https://www.stream-forward.org/> <https://www.ververica.com/> Ververica GmbH | Herzogspitalstrasse 24 | 80331 München | Germany Follow us: <https://www.linkedin.com/company/ververica/posts/?feedView=all> <https://www.youtube.com/@ververica> <https://open.spotify.com/show/2XME9h8iBOyr6YupqM99ir?si=87b064644add42a1> Available on: <https://aws.amazon.com/marketplace/pp/prodview-luvmqd6leha4i> <https://marketplace.microsoft.com/en-us/product/saas/ververica.vvc_managed?tab=Overview> Pflichtangaben/Mandatory Information <https://www.ververica.com/mandatory-information>
