-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta: Release and launch Ibis streaming data backends #8033
Comments
Weekly Update: After the sync with Claypot on 01/16/24 these are the PRs that need review for the 8.0.0 release. Flink (Chloe mentioned that Mehmet's PR should be reviewed first so this is the order):
Draft PR: conversation ongoing in the comments on whether it's worth it keep this one open
This is the blog: Risingwave At the moment CI is stuck because it has conflicts, maybe we should give it a nudge. (copying over last week's update on behalf of Naty) |
Weekly Update 2024/01/24Flink
Merged or closed 🎉
Blog PR:
Tutorial PR: Risingwave
|
Weekly Update2024/01/31 NOTE: 8.0 Ibis release with streaming support will happen early next week Flink
Still open but not required for release
Blog PR:
Tutorial PR:
Risingwave PR was merged 🎉 |
Weekly update2024/02/07 Flink Blog and Tutorial PRs are ready to be merged, waiting for coordinated advertisement push:
RisingWave
|
@lostmygithubaccount In the main epic comment we have these as requirements. For release and launch.
Can we revisit these requirements? I think having API docs for RisingWave (added here #8286) and the roadmap blog announcement that will have information about streaming should probably be enough for release announcement. Thoughts? |
Weekly update2024/02/14
|
Weekly update2024/02/22
We have pending a RisingWave blog/tutorial on Ibis site. |
Acceptance criteria: Ibis releases and launches its first two streaming backends, Apache Flink and RisingWave, in collaboration with Claypot AI and RisingWave respectively.
Stretch goal: Apache Sedona backend for streaming + geospatial.
TODOs:
separately we will track:
The text was updated successfully, but these errors were encountered: