Thanks Konstantin and Chesnay for starting the discussion. And thanks Konstantin, Chesnay, Godfrey, Martijn for volunteering.
The 1.16 release at the end of July means that there are currently only 3 months to fully commit to 1.16 development, and I'm a little concerned that this is too short a time frame, which may result in some features only reaching a halfway decent state. Best, Jingsong On Wed, Apr 27, 2022 at 7:10 PM David Morávek <d...@apache.org> wrote: > > Thanks Konstantin and Chesnay for starting the discussion and volunteering. > The timeline proposal sounds reasonable :+1: > > Best, > D. > > On Tue, Apr 26, 2022 at 1:37 PM Martijn Visser <martijnvis...@apache.org> > wrote: > > > Hi everyone, > > > > Thanks for starting this discussion. I would also volunteer to help out as > > a release manager for the 1.16 release. > > > > Best regards, > > > > Martijn Visser > > https://twitter.com/MartijnVisser82 > > https://github.com/MartijnVisser > > > > > > On Tue, 26 Apr 2022 at 13:19, godfrey he <godfre...@gmail.com> wrote: > > > > > Hi Konstantin & Chesnay, > > > > > > Thanks for driving this discussion, I am willing to volunteer as the > > > release manager for 1.16. > > > > > > > > > Best, > > > Godfrey > > > > > > Konstantin Knauf <kna...@apache.org> 于2022年4月26日周二 18:23写道： > > > > > > > > Hi everyone, > > > > > > > > With Flink 1.15 about to be released, the community has started > > planning > > > & > > > > developing features for the next release, Flink 1.16. As such, I would > > > like > > > > to start a discussion around managing this release. > > > > > > > > Specifically, Chesnay & myself would like to volunteer as release > > > managers. > > > > Our focus as release managers would be > > > > * to propose a release timeline > > > > * to provide an overview of all ongoing development threads and ideally > > > > their current status to the community > > > > * to keep an eye on build stability > > > > * facilitate release testing > > > > * to do the actual release incl. communication (blog post, etc.) > > > > > > > > Is anyone else interested in acting as a release manager for Flink > > 1.16? > > > If > > > > so, we are happy to make this a joint effort. > > > > > > > > Besides the question of who will act as a release manager, I think, we > > > can > > > > already use this thread to align on a timeline. For collecting features > > > and > > > > everything else, we would start a dedicated threads shortly. > > > > > > > > Given Flink 1.15 will be released in the next days, and aiming for a 4 > > > > months release cycle including stabilization, this would mean *feature > > > > freeze at the end of July*. The exact date could be determined later. > > Any > > > > thoughts on the timeline.? > > > > > > > > Looking forward to your thoughts! > > > > > > > > Thanks, > > > > > > > > Chesnay & Konstantin > > > > >
