We indeed set the July 25 deadline as a fixed deadline. We wanted to get back in the quicker cadence of releasing. Op di 31 mei 2022 om 09:03 schreef Robert Metzger <rmetz...@apache.org>:
> > > > Is the feature freeze deadline on July 25 fixed or will it be adjusted > > accordingly? > > > Ideally we try not to push the deadline too much into the future. So I > prefer to consider it fixed. > > On Mon, May 30, 2022 at 7:08 PM Jing Ge <j...@ververica.com> wrote: > > > Thanks Robert for the reminder. Thanks Martijn for sharing the link. > > > > Is the feature freeze deadline on July 25 fixed or will it be adjusted > > accordingly? > > > > Best regards, > > Jing > > > > On Mon, May 30, 2022 at 4:56 PM Martijn Visser <martijnvis...@apache.org > > > > wrote: > > > >> Yes, we will have the release meeting tomorrow. Looking forward to > >> everyone > >> who wants to participate. For those that are looking for the invite > link, > >> see https://cwiki.apache.org/confluence/display/FLINK/1.16+Release > >> > >> Best regards, > >> > >> Martijn > >> > >> Op ma 30 mei 2022 om 16:39 schreef Robert Metzger <rmetz...@apache.org > >: > >> > >> > I assume we'll have the next release planning meeting tomorrow? > >> > > >> > I'm also bringing this up also as a reminder for other folks who might > >> be > >> > interested in joining. > >> > > >> > On Wed, May 11, 2022 at 5:55 AM Xintong Song <tonysong...@gmail.com> > >> > wrote: > >> > > >> >> I'd like to kindly remind that, if someone adds / modifies release > >> notes > >> >> of > >> >> a JIRA ticket close to or after the release finalization, it would be > >> >> important to sync with the release managers and make sure that change > >> >> appears in the final release notes. > >> >> > >> >> We have recently discovered a breaking change in 1.14 that is > >> mentioned in > >> >> JIRA but not in the final release notes, because the JIRA change > >> happened > >> >> after the release managers assembled the final release notes from > JIRA > >> >> tickets. > >> >> > >> >> Thank you~ > >> >> > >> >> Xintong Song > >> >> > >> >> > >> >> [1] https://issues.apache.org/jira/browse/FLINK-23652 > >> >> > >> >> On Mon, May 9, 2022 at 7:34 PM Johannes Moser <johan...@moser.wtf> > >> wrote: > >> >> > >> >> > Thanks Chesnay, Godfrey, Xingbo and Martijn for volunteering as > >> release > >> >> > managers. > >> >> > > >> >> > I would also recommend to have an eye on the "Release Notes:" > fields > >> in > >> >> > JIRA > >> >> > for related issues early, as this is used to assemble the final > >> release > >> >> > notes. > >> >> > > >> >> > I'd also like to take the chance to ask contributors to fill the > >> >> "Release > >> >> > Notes" > >> >> > field such that users know what to do when they want to upgrade > from > >> a > >> >> > previous version. [1] for reference. > >> >> > Please keep in mind it is about enabling users. If no significant > >> >> changes > >> >> > facing the user have been done it should be left empty. > >> >> > > >> >> > > >> >> > [1] > >> >> > > >> >> > >> > https://cwiki.apache.org/confluence/display/FLINK/Flink+Jira+Process#FlinkJiraProcess-ReleaseNoteRedImportant > >> >> > > >> >> > > >> >> > > On 09.05.2022, at 12:27, Martijn Visser < > martijnvis...@apache.org> > >> >> > wrote: > >> >> > > > >> >> > > Hi everyone, > >> >> > > > >> >> > > With Flink 1.15 released last week, we're starting with the next > >> >> release > >> >> > > cycle for what will become Flink 1.16. As previously discussed > [1] > >> >> > Chesnay, > >> >> > > Godfrey, Xingbo and myself have volunteered as release managers. > >> We're > >> >> > > aiming to cut the release branch on the 25th of July. If needed, > we > >> >> can > >> >> > > delay this with a maximum of 2 weeks. We're aiming for a release > of > >> >> Flink > >> >> > > 1.16 mid September 2022. > >> >> > > > >> >> > > As we've done before, we would like to have a rough overview of > new > >> >> > > features or major improvements that are planned and will likely > be > >> >> > included > >> >> > > in this release. Please provide your FLIP, or (umbrella) Jira > >> ticket > >> >> in > >> >> > the > >> >> > > wiki page which you can find at > >> >> > > https://cwiki.apache.org/confluence/display/FLINK/1.16+Release. > >> >> > > > >> >> > > Starting Tuesday the 17th of May we will start again with > bi-weekly > >> >> > release > >> >> > > sync. This is scheduled for 9am CEST / 3pm China Standard Time / > >> 7am > >> >> UTC. > >> >> > > This meeting is to perform the following: > >> >> > > > >> >> > > * Have a look at the Flink 1.16 progress from the wiki page > (please > >> >> > update > >> >> > > this before the meeting). > >> >> > > * Discuss any blocker ticket that might occur who can help > resolve > >> >> this. > >> >> > > * Discuss build instability tickets that need to be followed-up. > >> >> > > * If there's a (new) contributor to get a PR reviewed or > >> committed, we > >> >> > can > >> >> > > see who can help out unblocking the contributor. > >> >> > > > >> >> > > One of the lessons learned during the Flink 1.15 release cycle > was > >> >> that > >> >> > > cross-team testing was done fairly late in the process, which > >> delayed > >> >> the > >> >> > > release. It would be good to make sure that these efforts are > done > >> as > >> >> > > quickly as possible. > >> >> > > This also applies to documentation: please make sure that your > >> >> feature is > >> >> > > documented (either in regular documentation, the JavaDocs, inside > >> the > >> >> > repo > >> >> > > in markdown or multiple). Don't start working on your next > >> >> contribution > >> >> > if > >> >> > > the documentation hasn't been made available yet. > >> >> > > > >> >> > > Please let us know what you think. > >> >> > > > >> >> > > Best regards, > >> >> > > > >> >> > > Chesnay, Godfrey, Xingbo and Martijn > >> >> > > > >> >> > > [1] > >> https://lists.apache.org/thread/ghfb5xdjy7tv0zqlrxvh3hcsc740w4ml > >> >> > > >> >> > > >> >> > >> > > >> > > >
