[website] update roadmap to account latest requirements (#1214)

* update roadmap to account latest requirements

* Address Jark comment

* minor fix

* address giannis comments

Author: MehulBatra

website/src/pages/roadmap.md

@@ -17,56 +17,36 @@
 -->
 
 # Fluss Roadmap
-
-This roadmap means to provide users and contributors with a high-level summary of ongoing efforts in the Fluss community.
-The roadmap contains both efforts working in process as well as completed efforts, so that users may get a better impression of the overall status and direction of those developments.
-
+This roadmap means to provide users and contributors with a high-level summary of ongoing efforts in the Fluss community. The roadmap contains both efforts working in process as well as completed efforts, so that users may get a better impression of the overall status and direction of those developments.
 ## Kafka Protocol Compatibility
-
 Fluss will support the Kafka network protocol to enable users to use Fluss as a drop-in replacement for Kafka. This will allow users to leverage Fluss's real-time storage capabilities while maintaining compatibility with existing Kafka applications.
-
 ## Flink Integration
-
-Fluss will provide deep integration with Apache Flink, enabling users a single engine experience for building real-time analytics applications.
-The integration will include:
-- Support for Flink **DataStream API** to read/write data from/to Fluss.
-- Support new [Delta Join](https://cwiki.apache.org/confluence/display/FLINK/FLIP-486%3A+Introduce+A+New+DeltaJoin) to address the pain-points of Stream-Stream Join.
-- More pushdown optimizations: Filter Pushdown ([#197](https://github.com/alibaba/fluss/issues/197)), Partition Pruning ([#196](https://github.com/alibaba/fluss/issues/196)), Aggregation Pushdown, etc.
+Fluss will provide deep integration with Apache Flink, enabling users a single engine experience for building real-time analytics applications. The integration will include:
+- Upgrade Flink version to 2.x
+- Support new Delta Join to address the pain-points of Stream-Stream Join.
+- More pushdown optimizations: Filter Pushdown ([#197](https://github.com/alibaba/fluss/issues/197)), Aggregation Pushdown, etc.
 - Upgrade the Rule-Based Optimization into Cost-Based Optimization in Flink SQL streaming planner with leveraging statistics in Fluss tables.
-
-
 ## Streaming Lakehouse
-
-- Support for Iceberg ([#102](https://github.com/alibaba/fluss/issues/102)) as Lakehouse Storage. And DeltaLake, Hudi as well.
+- Support for Iceberg ([#452](https://github.com/alibaba/fluss/issues/452)) as Lakehouse Storage. And DeltaLake, Hudi as well.
 - Support Union Read for Spark, Trino, StarRocks.
-- Avoid data shuffle in compaction service to directly compact Arrow files of Fluss into Parquet files of data lakes ([#107](https://github.com/alibaba/fluss/issues/107)).
-
-## ZooKeeper Removal
-
-Fluss currently utilizes **ZooKeeper** for cluster coordination, metadata storage, and cluster configuration management.
-In upcoming releases, **ZooKeeper will be replaced** by **KvStore** for metadata storage and **Raft** for cluster coordination and ensuring consistency.
-This transition aims to streamline operations and enhance system reliability.
-
+- Support for Lance ([#1155](https://github.com/alibaba/fluss/issues/1155)) as Lakehouse Storage to enable integration with AI/ML workflows for multi-modal data processing.
+## Spark Integration
+- Support for Spark connector ([#155](https://github.com/alibaba/fluss/issues/155)) to enable seamless data processing and analytics workflows.
+## Python Client
+- Support Python SDK to connect with Python ecosystems, including PyArrow, Pandas, Lance, and DuckDB.
 ## Storage Engine
-
 - Support for complex data types: Array ([#168](https://github.com/alibaba/fluss/issues/168)), Map ([#169](https://github.com/alibaba/fluss/issues/169)), Struct ([#170](https://github.com/alibaba/fluss/issues/170)), Variant/JSON.
 - Support for schema evolution.
-- Support for secondary index for Delta Join with Flink (~~[#65](https://github.com/alibaba/fluss/issues/65)~~).
-- Support for buckets rescale.
+## ZooKeeper Removal
+Fluss currently utilizes ZooKeeper for cluster coordination, metadata storage, and cluster configuration management. In upcoming releases, ZooKeeper will be replaced by KvStore for metadata storage and Raft for cluster coordination and ensuring consistency. This transition aims to streamline operations and enhance system reliability.
 
 ## Zero Disks
-
-Fluss currently utilizes a tiered storage architecture to significantly reduce storage costs and operational complexities.
-However, the Fluss community is actively investing in the Zero Disk architecture,
-which aims to completely replace local disks with S3 storage. This transition will enable Fluss to achieve a
-serverless, stateless, and elastic design, significantly minimizing operational overhead while eliminating inter-zone networking costs.
-
+Fluss currently utilizes a tiered storage architecture to significantly reduce storage costs and operational complexities. However, the Fluss community is actively investing in the Zero Disk architecture, which aims to completely replace local disks with S3 storage. This transition will enable Fluss to achieve a serverless, stateless, and elastic design, significantly minimizing operational overhead while eliminating inter-zone networking costs.
 ## Maintenance
-
-- Re-balance Cluster
-- Gray Upgrade
-
+- Re-balance Cluster: Automatic cluster rebalancing capabilities for optimal resource distribution.
+- Gray Upgrade: Rolling upgrade support enabling zero-downtime system updates.
 ## Miscellaneous
+- Upgrade programming language to Java 11.
+- Support for more connectors: Trino, DuckDB, etc.
 
-- Upgrade programing language to Java 17 ([#203](https://github.com/alibaba/fluss/issues/203)).
-- Support for more connectors: Spark ([#155](https://github.com/alibaba/fluss/issues/155)), Presto, DuckDB, etc.
+*This roadmap is subject to change based on community feedback, technical discoveries, and evolving requirements. For the most up-to-date information, please refer to the GitHub milestone boards and project issues.*