Thanks Danny for bring this. +1 (non-binding)
Best regards, Weijie Jing Ge <j...@ververica.com.invalid> 于2023年2月27日周一 20:23写道： > +1 (non-binding) > > BTW, should we follow the content style [1] to describe the new rule using > 1.2.x, 1.1.y, 1.1.z? > > [1] https://flink.apache.org/downloads/#update-policy-for-old-releases > > Best regards, > Jing > > On Mon, Feb 27, 2023 at 1:06 PM Matthias Pohl > <matthias.p...@aiven.io.invalid> wrote: > > > Thanks, Danny. Sounds good to me. > > > > +1 (non-binding) > > > > On Wed, Feb 22, 2023 at 10:11 AM Danny Cranmer <dannycran...@apache.org> > > wrote: > > > > > I am starting a vote to update the "Update Policy for old releases" [1] > > to > > > include additional bugfix support for end of life versions. > > > > > > As per the discussion thread [2], the change we are voting on is: > > > - Support policy: updated to include: "Upon release of a new Flink > minor > > > version, the community will perform one final bugfix release for > resolved > > > critical/blocker issues in the Flink minor version losing support." > > > - Release process: add a step to start the discussion thread for the > > final > > > patch version, if there are resolved critical/blocking issues to flush. > > > > > > Voting schema: since our bylaws [3] do not cover this particular > > scenario, > > > and releases require PMC involvement, we will use a consensus vote with > > PMC > > > binding votes. > > > > > > Thanks, > > > Danny > > > > > > [1] > > https://flink.apache.org/downloads.html#update-policy-for-old-releases > > > [2] https://lists.apache.org/thread/szq23kr3rlkm80rw7k9n95js5vqpsnbv > > > [3] https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws > > > > > >
