Hi, Huajie,
Thank you very much for the clarification. This has well addressed the previous questions and will significantly facilitate the progress of subsequent work. If I’m understanding correctly, based on the current information, we’ve already aligned on the general plan: - The next version number will be 2.1.6 - The release tag will be created based on the already existing dev-2.1.6 branch - There is currently no pending work that needs to be waited on - During validation, apart from the usual checks, we only need to focus on the effectiveness and impact of the bug fixes > Regarding the release of version 2.1.6, I fully support it. It would be > excellent if you’re willing to serve as the Release Manager for this release! Thanks for your response. I'd like to volunteer as the release manager for this version 2.1.6, and I welcome other contributors to join and collaborate on the release process. Best regards, Yuepeng Pan At 2025-04-11 20:07:11, "Huajie Wang" <[email protected]> wrote: >Hi Yuepeng, > >Thank you for driving this forward. As you mentioned, it is indeed >necessary to release a formal version after the streampark project's >official graduation from Apache. Currently, the dev-2.1.6 branch is ready >for release, and I'd like to clarify the differences between the dev branch >and the dev-2.1.6 branch: > >The dev-2.1.x series is based on continuous iterations of version 2.1.0, >having progressed from 2.1.0 up to 2.1.5. This series will not involve >major architectural changes and primarily focuses on bug fixes and >stability improvements, making it a relatively stable release. > >The dev branch is our current main development branch, where the code has >diverged significantly from the 2.1.x series. We have added many new >features to this branch, such as support for PyFlink, Spark, etc., some of >which may include breaking changes. There is still substantial work >remaining for this version, and we tentatively plan to complete its release >within the next two months. > >I’ve now clarified the differences between these two branches. If you have >any further questions, feel free to reach out anytime. > >Regarding the release of version 2.1.6, I fully support it. It would be >excellent if you’re willing to serve as the Release Manager for this >release! > > >Best, >Huajie Wang > > > >Yuepeng Pan <[email protected]> 于2025年4月7日周一 16:44写道： > >> Hi, community, >> >> >> It has been about five months since the last release version >> (v2.1.5-incubating, Oct 18, 2024). >> During this period, the community has merged around 45 commits contributed >> by developers. >> These contributions have not only improved the usability and stability of >> StreamPark but also introduced new features. >> Perhaps now is a great time to start considering the release plan for the >> next version. >> I tried to find any discussion or proposal regarding the next release plan >> on the mailing list, >> but I can't locate anything relevant. If I missed anything, please feel >> free to correct me—many thanks in advance! >> >> >> What’s exciting is that this will be the first release plan since >> StreamPark graduated to a TLP. >> I’m looking forward to hearing everyone’s suggestions and input to help >> plan and organize the release process. >> Suggestions and input may include but are not limited to: >> - Choosing the version number: v2.1.6 or v2.2.0 >> - BTW, I noticed there are two branches with the dev prefix in the main >> repository: dev and dev-2.1.6. >> It would be helpful if we could confirm which one should serve as the >> base for the release branch. >> - Estimated completion time for ongoing development work (new features or >> bug fixes) & Expected release date >> - This will determine the concrete follow-up plan for what we’re going >> to release, making some trade-offs between the expected release date and >> the ongoing features and fixes. >> - After that, we'll collect the patches and features list to validate >> and release. >> - ... >> >> Any input it apprecated! >> >> Best regards, >> Yuepeng Pan
