Skip to content

[website] update roadmap to account latest requirements#1214

Merged
polyzos merged 4 commits intoapache:mainfrom
MehulBatra:roadmap_update
Jul 10, 2025
Merged

[website] update roadmap to account latest requirements#1214
polyzos merged 4 commits intoapache:mainfrom
MehulBatra:roadmap_update

Conversation

@MehulBatra
Copy link
Copy Markdown
Contributor

Purpose

Linked issue: #1203

Update roadmap to reflect v0.8 features, timeline, and latest project additions.

Brief change log

  • Added "Fluss Server" section for HA, cluster operations, and optimizations
  • Added Streaming Lakehouse production-ready features and Lance support
  • Added Spark connector, Python client, and Helm charts sections
  • Updated Java version from 17 to 11
  • Reorganized Flink integration with system tables support
  • Added GitHub issue references and milestone board link

Tests

None

API and Format

None

Documentation

Yes. Enhanced roadmap with v0.8 features, timeline, and improved organization for better project visibility.

@MehulBatra
Copy link
Copy Markdown
Contributor Author

@wuchong @polyzos When you have some time, could you please take a look at this PR? Thank you!

@wuchong
Copy link
Copy Markdown
Member

wuchong commented Jun 26, 2025

In my opinion, the project roadmap should not serve as an issue tracker. Instead, it should provide a high-level overview that’s easy to understand — even for users who are not yet familiar with Fluss. That means we don’t need to list every detailed issue here (which may be hard to grasp at a glance). Interested users can refer to the corresponding milestone for full tracking details.

Also, there are currently too many bolded items, which dilutes the visual emphasis. I suggest using only H2 headings , and removing H3s and bold formatting for issue titles to improve readability and focus.

What do you think?

image

@MehulBatra
Copy link
Copy Markdown
Contributor Author

MehulBatra commented Jun 26, 2025

I completely agree, I had this same thought but I let it die. You're right that current roadmap is too granular and closely tied to version 0.8 specifics rather than presenting a clear, high-level vision. I'll rework it to be more concise and strategic, focusing on the big picture that newcomers can easily grasp. I'll also streamline the formatting as you suggested.
Thank you for the feedback!

@MehulBatra
Copy link
Copy Markdown
Contributor Author

@wuchong Please have a look, I have try to modify it as discussed above in a more condensed way.

@MehulBatra MehulBatra requested a review from polyzos July 8, 2025 18:38
@polyzos
Copy link
Copy Markdown
Contributor

polyzos commented Jul 10, 2025

LGTM

@polyzos polyzos merged commit 1fef980 into apache:main Jul 10, 2025
2 checks passed
@MehulBatra
Copy link
Copy Markdown
Contributor Author

MehulBatra commented Jul 10, 2025

Thanks @polyzos @wuchong for the review!

polyzos pushed a commit to polyzos/fluss that referenced this pull request Aug 30, 2025
* update roadmap to account latest requirements

* Address Jark comment

* minor fix

* address giannis comments
polyzos pushed a commit to Alibaba-HZY/fluss that referenced this pull request Aug 31, 2025
* update roadmap to account latest requirements

* Address Jark comment

* minor fix

* address giannis comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants