Hi everyone, thank you for the feedback so far. I've checked the length of the previous last release cycles. Up until Flink 1.14, we've actually been incredibly good at maintaining a 5 months release cycle (see below). Interestingly, the community is officially targeting a 4 months release cycle [1].
- 1.15.0 2022-05-01? (7 months, 2 days?) - 1.14.0: 2021-09-29 (4 months, 26 days) - 1.13.0: 2021-05-03 (4 months, 23 days) - 1.12.0: 2020-12-10 (5 months, 3 days) - 1.11.0: 2020-07-07 (4 months, 26 days) - 1.10.0: 2020-02-11 The 1.15 release cycle has took significantly longer. In my opinion we should try to get back into the 5 months cadence with the next release. Since empirically we always often end up moving the the feature freeze by a week or two, and that we often need about a month for release testing & stabilization and releasing, I don't think, we should move the planned feature freeze to later than *mid August. * What do you think: 1. Should we continue to strive for a 5 months release cycle (and update [1] accordingly)? 2. Does it sound reasonable to target a feature freeze date, which is 1.5 months before to the desired release date? Cheers, Konstantin [1] https://cwiki.apache.org/confluence/display/FLINK/Time-based+releases Am Do., 28. Apr. 2022 um 05:20 Uhr schrieb Jingsong Li < jingsongl...@gmail.com>: > 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 > > > > > > > >
