Replies: 2 comments 1 reply
-
|
I presented this idea at the first OpenDAL meetup. Here are the slides: https://docs.google.com/presentation/d/1nY8rQaRQqMwQUaUTDaP9_qpibsQ9MmmnRjtVs_ts3pA/edit?usp=sharing |
Beta Was this translation helpful? Give feedback.
0 replies
-
UpdatesWe have completed the first step: defining our VISION. We refined it to "One Layer, All Storage" and have created a new vision page: https://opendal.apache.org/docs/vision The next step will be |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Great job! <3 |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone, I'm thrilled yet nervous to kick off this discussion about OpenDAL Rust Core v1.0.
Releasing version 1.0 is a commitment—a commitment that we won't make any breaking changes until we upgrade to version 2.0. It’s a promise that we will take breaking changes seriously. At the same time, this is a declaration. We announce that OpenDAL is prepared for broader adoption. OpenDAL is ready to be integrated into more applications and used throughout the entire community.
That's why we're here. Thank you to everyone who has helped OpenDAL reach this position.
Following the pattern from hyper, I would like to divide this discussion into the following steps:
Define the VISION
First and foremost, we must define what OpenDAL actually represents. This will be an abstract vision that illustrates the goals and purpose of OpenDAL, tailored to the needs of our community.
Our current vision, "access data freely," occasionally confuses our users, as many associate the term "data" with databases, data lakes, and SQL in the broader context. We should refine it to better reflect OpenDAL's objectives.
Outline the roadmap
Shortly thereafter, we will outline the major changes necessary for OpenDAL to align with the objectives defined in the Vision.
Plan the work
We'll organize the necessary work into issues, labels, and milestones. Issues should be clearly articulated to allow newcomers to easily participate.
Do the development work
We will engage the entire community in the development of OpenDAL v1.0. We plan to release several minor versions to gradually introduce breaking changes, thus avoiding significant disruptions upon the release of OpenDAL v1.0. We anticipate that users will be able to upgrade to v1.0 from the latest version seamlessly.
Perfect the documentation
Some documents are missing or outdated, and others fail to meet user needs. It would be better to perfect them during the v1.0 release.
Gather feedback
OpenDAL v1.0 will not introduce sudden changes. I personally anticipate a gradual progression through versions v0.51, v0.52, etc. We will collect user feedback throughout these changes. Additionally, we will advance some key dependencies to release v1.0, such as reqsign.
Ship it
Click the button. Get ready for the next journey.
What are your thoughts? Do you believe it's an appropriate time for OpenDAL Rust Core to release its version 1.0? What are your expectations for OpenDAL Rust Core version 1.0?
Beta Was this translation helpful? Give feedback.
All reactions