Thanks for the feedback! I agree that we should follow a structured approach.
Release 0.7.0 first — We can kick off the 0.7.0 release cycle immediately, incorporating the features and fixes that have accumulated since 0.6. This gives us a clear "final minor version" of the 0.x series. And then formally close the 0.x line — Once 0.7.0 is released, we can officially declare it the last minor version of 0.x, which sets a clean boundary. Open a dedicated discussion for 1.0.0 — After 0.7.0 ships, we start a separate thread to align on what "1.0.0 readiness" means for Celeborn — API stability guarantees, compatibility commitments, etc. I'm happy to volunteer as release manager for 0.7.0 first, and then continue the conversation about 1.0.0 with the community. On 2026/03/25 06:24:31 Nicholas Jiang wrote: > Hi Zaynt, > > Thanks for volunteering the new release. Generally speaking, it's necessary > to first discuss whether a new major version needs to be introduced. The next > version release should be 0.7.0, which version is the final minor version. > The 0.6.2 version is not officially announced as the final minor version of > version 0.x. Therefore, is it better to firstly release 0.7.0 and discuss the > major version 1.0.0? > > Regards, > Nicholas Jiang > > On 2026/03/20 10:10:52 Zhentao Shuai wrote: > > Hi, Celeborn community, > > > > It has been 10 months since we release the last major version , and there > > are some new features: > > > > More complete C++ native client support. > > > > More mature OSS/S3 support, performance optimizations such as S3 client > > caching to reduce redundant initialization, and unified Flink tiered > > storage integration. > > > > New observability metrics for flush volume/latency, eviction counts, and > > read buffer availability across all storage tiers. > > > > Better performance on pushing data etc. > > > > Looking at the remarkable progress the Celeborn community has made since > > its graduation: > > > > Rerun Spark stage, support for MapReduce and Flink, support for memory > > storage and remote storage, Flink hybrid shuffle, HARD_SPLIT in > > PushMergedData, optimize skew partition, CppClient etc. > > > > Considering the extensive real-world applications and valuable feedback > > from our users, I believe we are ready to take a significant step forward > > and it is the right time to prepare for the new release version. > > > > With our current release at 0.6.2, I propose that we kick off 2026 with > > version 1.0.0 as our first major release. This milestone not only > > represents the technical maturity and production-grade stability we've > > achieved together, but also signifies our community's commitment to > > delivering a robust, reliable, and enterprise-ready solution. The 1.0.0 > > release will mark an important chapter in Celeborn's journey, reflecting > > the collective dedication and innovation that have brought us to this point. > > > > WDYT? And I’m volunteering to be the release manager if no one has applied. > > > > Regards, > > Zaynt Shuai > > >
