Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: <HE1PR03MB130533148A8A9D7EB8366FE0F37D0@HE1PR03MB1305.eurprd03.prod.outlook.com>
References: <CANC1h_tS4oaoQxWb2Guv3ttZYZ3VKumRwGriPESNPt-pHXLRQA@mail.gmail.com>
 <CAAdrtT1eHQBTc4KrYoUcfvBwzTEstcbBportWAcz0mFdS1FG_Q@mail.gmail.com>
 <20FDA2ED-A04B-4FE4-A901-009F6878F0BC@kth.se> <etPan.587cbe63.6405c290.b89d@apache.org>
 <CANMrRJZEwCNca2P9gcn9j9-p64quRavGHqeHytrhEyO5Y=7h-g@mail.gmail.com> <HE1PR03MB130533148A8A9D7EB8366FE0F37D0@HE1PR03MB1305.eurprd03.prod.outlook.com>
From: Stephan Ewen <sewen@apache.org>
Date: Fri, 20 Jan 2017 16:42:04 +0100
Message-ID: <CANC1h_tGW9UytJaPwcmpizC_nfMZgfdCzs+zERMt0Bv9qHmuAA@mail.gmail.com>
Subject: Re: [DISCUSS] (Not) tagging reviewers
To: "dev@flink.apache.org" <dev@flink.apache.org>
Content-Type: multipart/alternative; boundary=001a1143e4cedf76a00546887d08
archived-at: Fri, 20 Jan 2017 15:42:07 -0000

--001a1143e4cedf76a00546887d08
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

@Alexey - Pull Requests backlog is going pretty crazy, I agree.

That is not because the committers are not working on pull requests, there
is simply so many of them.
We are looking for new committers (and discussing in the PMC).

Tagging is not going to make this better, I believe. It may make it worse,
because it discourages non-tagged community members from picking up a pull
request.


On Mon, Jan 16, 2017 at 4:54 PM, Anton Solovev <Anton_Solovev@epam.com>
wrote:

> Hi, Alexey
>
> I will check abandoned PRs to reduce obviously outdated ones and add them
> to a cleanup list https://issues.apache.org/jira/browse/FLINK-5384
>
>
> -----Original Message-----
> From: Alexey Demin [mailto:diominay@gmail.com]
> Sent: Monday, January 16, 2017 5:05 PM
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] (Not) tagging reviewers
>
> Hi all
>
> View from my prospective:
> in middle of summer - 150 PR
> in middle of autumn - 180
> now 206.
>
> This is mix of bugfixes and improvements.
> I understand that work on new features important, but when small and
> trivial fixes stay in states of PR more then 2-3 month, then all users
> think about changing engine on other product.
>
> Only way push people to merge this fixes in master it's tags.
>
> I don't speak about big changes, only about small and trivial with review
> less then 5 min.
>
> Features important, but if this features work incorrect, then user can
> select more stability product without any hesitation.
>
> Thanks
> Alexey Diomin
>
>
>
> 2017-01-16 16:36 GMT+04:00 Ufuk Celebi <uce@apache.org>:
>
> > On 16 January 2017 at 12:59:04, Paris Carbone (parisc@kth.se) wrote:
> > > > Though, when someone has started reviewing a PR and shows interest
> > > it probably makes sense to finish doing so. Wouldn=E2=80=99t tagging =
be
> > > acceptable there?
> > > In those case tagging triggers direct notifications, so that people
> > > already involved in a conversation get reminded and answer pending
> > > questions.
> >
> > I think that's totally fine Paris since it is more of a reminder in
> > that case.
> >
> > Stephan is referring to PRs that have a last line in the description
> > like "@XZY for review please".
> >
> > =E2=80=93 Ufuk
> >
> >
> >
>

--001a1143e4cedf76a00546887d08--