You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by Johannes Moser <jo...@data-artisans.com> on 2021/06/28 07:54:22 UTC

Flink 1.14. Bi-weekly 2021-06-22

Hello,

Last Tuesday was our second bi-weekly.

You can read up the outcome in the confluence wiki page [1].

*Feature freeze date*
As we didn't come to a clear agreement, we will keep the anticipated feature freeze date
as it is at early August.

*Build stability*
The good thing: we decreased the number of issues, the not so good thing: only by ten.
We as a community need to put further effort into this.

*Dependencies*
We'd like to ask all contributors to have a look at the components they are heavily 
Involved with to see if any dependencies require updating. There were some 
Issues recently to pass the security scans by some of the users. In future this should
somehow be a default at the beginning of every release cycle.

*Criteria for merging PRs*
We want to avoid merging PRs with unrelated CI failures. We are quite aware that we
need to raise the importance of the Docker caching issue.

What can you do to make the Flink 1.14. release a good one:
* Identify and update outdated dependencies
* Get rid of test instabilities
* Don't merge PRs including unrelated CI failures

Best,
Joe


[1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release

Re: Flink 1.14. Bi-weekly 2021-06-22

Posted by Yu Li <ca...@gmail.com>.

Thanks for taking care of this, Joe! The information is very helpful!

Best Regards,
Yu


On Mon, 28 Jun 2021 at 18:40, Till Rohrmann <tr...@apache.org> wrote:

> Thanks a lot for the update, Joe. This is very helpful!
>
> Cheers,
> Till
>
> On Mon, Jun 28, 2021 at 10:10 AM Xintong Song <to...@gmail.com>
> wrote:
>
> > Thanks for the update, Joe.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> > On Mon, Jun 28, 2021 at 3:54 PM Johannes Moser <jo...@data-artisans.com>
> > wrote:
> >
> > > Hello,
> > >
> > > Last Tuesday was our second bi-weekly.
> > >
> > > You can read up the outcome in the confluence wiki page [1].
> > >
> > > *Feature freeze date*
> > > As we didn't come to a clear agreement, we will keep the anticipated
> > > feature freeze date
> > > as it is at early August.
> > >
> > > *Build stability*
> > > The good thing: we decreased the number of issues, the not so good
> thing:
> > > only by ten.
> > > We as a community need to put further effort into this.
> > >
> > > *Dependencies*
> > > We'd like to ask all contributors to have a look at the components they
> > > are heavily
> > > Involved with to see if any dependencies require updating. There were
> > some
> > > Issues recently to pass the security scans by some of the users. In
> > future
> > > this should
> > > somehow be a default at the beginning of every release cycle.
> > >
> > > *Criteria for merging PRs*
> > > We want to avoid merging PRs with unrelated CI failures. We are quite
> > > aware that we
> > > need to raise the importance of the Docker caching issue.
> > >
> > > What can you do to make the Flink 1.14. release a good one:
> > > * Identify and update outdated dependencies
> > > * Get rid of test instabilities
> > > * Don't merge PRs including unrelated CI failures
> > >
> > > Best,
> > > Joe
> > >
> > >
> > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release
> >
>

Re: Flink 1.14. Bi-weekly 2021-06-22

Posted by Till Rohrmann <tr...@apache.org>.

Thanks a lot for the update, Joe. This is very helpful!

Cheers,
Till

On Mon, Jun 28, 2021 at 10:10 AM Xintong Song <to...@gmail.com> wrote:

> Thanks for the update, Joe.
>
> Thank you~
>
> Xintong Song
>
>
> On Mon, Jun 28, 2021 at 3:54 PM Johannes Moser <jo...@data-artisans.com>
> wrote:
>
> > Hello,
> >
> > Last Tuesday was our second bi-weekly.
> >
> > You can read up the outcome in the confluence wiki page [1].
> >
> > *Feature freeze date*
> > As we didn't come to a clear agreement, we will keep the anticipated
> > feature freeze date
> > as it is at early August.
> >
> > *Build stability*
> > The good thing: we decreased the number of issues, the not so good thing:
> > only by ten.
> > We as a community need to put further effort into this.
> >
> > *Dependencies*
> > We'd like to ask all contributors to have a look at the components they
> > are heavily
> > Involved with to see if any dependencies require updating. There were
> some
> > Issues recently to pass the security scans by some of the users. In
> future
> > this should
> > somehow be a default at the beginning of every release cycle.
> >
> > *Criteria for merging PRs*
> > We want to avoid merging PRs with unrelated CI failures. We are quite
> > aware that we
> > need to raise the importance of the Docker caching issue.
> >
> > What can you do to make the Flink 1.14. release a good one:
> > * Identify and update outdated dependencies
> > * Get rid of test instabilities
> > * Don't merge PRs including unrelated CI failures
> >
> > Best,
> > Joe
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release
>

Re: Flink 1.14. Bi-weekly 2021-06-22

Posted by Xintong Song <to...@gmail.com>.

Thanks for the update, Joe.

Thank you~

Xintong Song


On Mon, Jun 28, 2021 at 3:54 PM Johannes Moser <jo...@data-artisans.com>
wrote:

> Hello,
>
> Last Tuesday was our second bi-weekly.
>
> You can read up the outcome in the confluence wiki page [1].
>
> *Feature freeze date*
> As we didn't come to a clear agreement, we will keep the anticipated
> feature freeze date
> as it is at early August.
>
> *Build stability*
> The good thing: we decreased the number of issues, the not so good thing:
> only by ten.
> We as a community need to put further effort into this.
>
> *Dependencies*
> We'd like to ask all contributors to have a look at the components they
> are heavily
> Involved with to see if any dependencies require updating. There were some
> Issues recently to pass the security scans by some of the users. In future
> this should
> somehow be a default at the beginning of every release cycle.
>
> *Criteria for merging PRs*
> We want to avoid merging PRs with unrelated CI failures. We are quite
> aware that we
> need to raise the importance of the Docker caching issue.
>
> What can you do to make the Flink 1.14. release a good one:
> * Identify and update outdated dependencies
> * Get rid of test instabilities
> * Don't merge PRs including unrelated CI failures
>
> Best,
> Joe
>
>
> [1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release