You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Tzu-Li (Gordon) Tai" <tz...@apache.org> on 2020/12/21 10:17:07 UTC
[DISCUSS] Releasing StateFun hotfix version 2.2.2
Hi,
Now that Flink 1.11.3 is out, which includes a critical fix that StateFun
was waiting for [1], we would like to proceed with the next hotfix for the
StateFun 2.2.x series by upgrading the Flink version to 1.11.3 in StateFun.
2.2.2 would not include many new fixes by itself other than upgrading to
Flink 1.11.3, but [1] is already critical enough to justify a hotfix
release ASAP. Please see [2] for a recap of the severity of [1] and how it
affects StateFun.
I'd like to create a RC preferably tomorrow, and taking into account the
Christmas holidays where we would expect some downtime in the community,
see if we can gather enough votes for a release before the end of the year.
Cheers,
Gordon
[1] https://issues.apache.org/jira/browse/FLINK-19741
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Releasing-StateFun-hotfix-version-2-2-1-td46239.html
Re: [DISCUSS] Releasing StateFun hotfix version 2.2.2
Posted by "Tzu-Li (Gordon) Tai" <tz...@apache.org>.
Thanks Seth!
And yes, I'll reach out to some individual PMCs to make sure the RCs will
get enough attention and votes.
I'll proceed to create RC1 now.
On Tue, Dec 22, 2020 at 3:18 AM Seth Wiesman <sj...@gmail.com> wrote:
> +1
>
> This is an important fix, and I'm available this week for RC testing. Given
> the makeup of the normal statefun contributors, it might make sense to
> proactively reach out to some additional PMC members about testing.
>
> Seth
>
> On Mon, Dec 21, 2020 at 4:18 AM Tzu-Li (Gordon) Tai <tz...@apache.org>
> wrote:
>
> > Hi,
> >
> > Now that Flink 1.11.3 is out, which includes a critical fix that StateFun
> > was waiting for [1], we would like to proceed with the next hotfix for
> the
> > StateFun 2.2.x series by upgrading the Flink version to 1.11.3 in
> StateFun.
> >
> > 2.2.2 would not include many new fixes by itself other than upgrading to
> > Flink 1.11.3, but [1] is already critical enough to justify a hotfix
> > release ASAP. Please see [2] for a recap of the severity of [1] and how
> it
> > affects StateFun.
> >
> > I'd like to create a RC preferably tomorrow, and taking into account the
> > Christmas holidays where we would expect some downtime in the community,
> > see if we can gather enough votes for a release before the end of the
> year.
> >
> > Cheers,
> > Gordon
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-19741
> > [2]
> >
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Releasing-StateFun-hotfix-version-2-2-1-td46239.html
> >
>
Re: [DISCUSS] Releasing StateFun hotfix version 2.2.2
Posted by Seth Wiesman <sj...@gmail.com>.
+1
This is an important fix, and I'm available this week for RC testing. Given
the makeup of the normal statefun contributors, it might make sense to
proactively reach out to some additional PMC members about testing.
Seth
On Mon, Dec 21, 2020 at 4:18 AM Tzu-Li (Gordon) Tai <tz...@apache.org>
wrote:
> Hi,
>
> Now that Flink 1.11.3 is out, which includes a critical fix that StateFun
> was waiting for [1], we would like to proceed with the next hotfix for the
> StateFun 2.2.x series by upgrading the Flink version to 1.11.3 in StateFun.
>
> 2.2.2 would not include many new fixes by itself other than upgrading to
> Flink 1.11.3, but [1] is already critical enough to justify a hotfix
> release ASAP. Please see [2] for a recap of the severity of [1] and how it
> affects StateFun.
>
> I'd like to create a RC preferably tomorrow, and taking into account the
> Christmas holidays where we would expect some downtime in the community,
> see if we can gather enough votes for a release before the end of the year.
>
> Cheers,
> Gordon
>
> [1] https://issues.apache.org/jira/browse/FLINK-19741
> [2]
>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Releasing-StateFun-hotfix-version-2-2-1-td46239.html
>