By starting the release process I meant the steps to create a RC, but the wording was confusing.
On Tuesday, March 25th, 2025 at 12:09, Ferenc Csaky <ferenc.cs...@pm.me.INVALID> wrote: > > > Thank you all for the inputs! If no objections until then, > I will start the release process in Thursday (03-27). > > Thanks, > Ferenc > > > > On Monday, March 24th, 2025 at 16:59, Mate Czagany czmat...@gmail.com wrote: > > > Hi Ferenc, > > > > I think the current state is great to have the first release. Thank you for > > the effort you've put into this. > > > > Regards, > > Mate > > > > Attila Kreiner kreiner.att...@gmail.com ezt írta (időpont: 2025. márc. > > > > 21., P, 15:07): > > > > > +1 for the release and the release manager. > > > > > > Cheers, > > > Attila > > > > > > On Fri, 21 Mar 2025 at 14:46, Márton Balassi balassi.mar...@gmail.com > > > wrote: > > > > > > > Hi Ferenc, > > > > > > > > +1. It makes sense to move the Kudu connector under the Flink umbrella, > > > > I > > > > agree that it should support Flink 1.19 and 1.20 (maybe 2.0 soon) and > > > > thanks for volunteering as the release manager. > > > > > > > > Cheers, > > > > Marton > > > > > > > > On Fri, Mar 21, 2025 at 1:00 PM Ferenc Csaky <ferenc.cs...@pm.me.invalid > > > > > > > > wrote: > > > > > > > > > Hello devs, > > > > > > > > > > I would like to start a discussion to release the externalized Kudu > > > > > connector. To make anyone > > > > > up to date regarding what happened until now and why, let me summarize > > > > > the > > > > > story. > > > > > > > > > > Originally, the Kudu connector was part of the Bahir Flink [1] > > > > > repository, > > > > > but it was moved into > > > > > the attic in early 2024. Since there was demand to still maintain and > > > > > develop this connector, I > > > > > initiated FLIP-439 [2] to externalize this connector and adapt it to > > > > > the > > > > > externalized Flink > > > > > connector model. > > > > > > > > > > I think at this point the connector is in a good state, all the > > > > > original > > > > > deliverables are done, and > > > > > some new features and improvements were also developed that was not > > > > > part > > > > > of the scope of > > > > > the FLIP, feel free to check all the items [3]. All in all, I think > > > > > the > > > > > connector is ready for its first > > > > > release in the standalone externalized model, and according to the > > > > > current > > > > > Flink releases I > > > > > would suggest to release it for the currently supported 1.x minor > > > > > Flink > > > > > versions, which means > > > > > 1.19, and 1.20. > > > > > > > > > > If the community agrees, I also volunteer to be the release manager. > > > > > > > > > > WDYT? > > > > > > > > > > Thanks, > > > > > Ferenc > > > > > > > > > > [1] https://github.com/apache/bahir-flink > > > > > [2] > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-439%3A+Externalize+Kudu+Connector+from+Bahir > > > > > > > > [3] > > > > > > https://issues.apache.org/jira/browse/FLINK-37527?jql=project %3D FLINK > > > AND fixVersion %3D kudu-2.0.0 and resolution %3D Fixed
