Mailing-List: contact dev-help@flume.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flume.apache.org
MIME-Version: 1.0
References: <CAGJT+6t07UTXt5XYK=B49kTa0Yp8TqoEjXdv5+wqLg5_w_1qDg@mail.gmail.com>
 <CAGJT+6t-MM9WmPOROCNqBy-mO+pwXv6pj0A9s1i32c-sZOZpaA@mail.gmail.com>
 <CADrPCehskK8BmU83g5H38=FWSxvJY3C8FcqjzKtCj+UbJDStUA@mail.gmail.com>
 <CAGJT+6tMkhJP93Qbb6YhPsAkAZ0bgJov=2SJLjvkOyyhhjudOw@mail.gmail.com>
 <CAJLbxRZrmc2yUN9g_oCRA0V4KkijqV83Syt3XsscQSsYVpz3yQ@mail.gmail.com>
 <CACGQnLVz1nj5HyGsXKZ_88Fyd=7p58A_bfAJM=A0w+r=DD-_yg@mail.gmail.com>
 <CAHNKprCidNg_Ca0=9-3aw-3b=EYTTMmMNrb-udQvUyD8pEtv8g@mail.gmail.com> <60D4EE56-B894-4FF6-8A12-D351F437FC5D@dslextreme.com>
In-Reply-To: <60D4EE56-B894-4FF6-8A12-D351F437FC5D@dslextreme.com>
From: Denes Arvay <denes@cloudera.com>
Date: Wed, 13 Sep 2017 14:06:17 +0000
Message-ID: <CAGJT+6s1NkeFT=TM1YG+uca44UxTzZB0CO1Dr5QLJNNAX-SPsA@mail.gmail.com>
Subject: Re: [DISCUSS] Flume 1.8 release proposal
To: dev@flume.apache.org
Content-Type: multipart/alternative; boundary="001a113ce2b67c65c3055912aa85"
archived-at: Wed, 13 Sep 2017 14:06:34 -0000

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

Thank you all for sharing your thoughts, and thanks Tristan for supporting
the release.
I'm about to branch, I'll let you know when it's done.

Regards,
Denes

On Wed, Sep 13, 2017 at 6:10 AM Ralph Goers <ralph.goers@dslextreme.com>
wrote:

>
> > On Sep 12, 2017, at 7:46 AM, Tristan Stevens <tristan@cloudera.com>
> wrote:
> >
> > FWIW:
> > I=E2=80=99m not overly in favour of rushing a release out when we have =
many JIRAs
> > with patches submitted, especially when some of those are +1=E2=80=99d =
by
> multiple
> > reviewers.
>
> Rushing a release? It has been a year since the last release. For most
> open source projects that is an eternity.
>
> >
> > This doesn=E2=80=99t speak of a mature and active community process - I=
=E2=80=99d much
> > rather that we pause a little, have a big effort by the committers to g=
et
> > these patches in - especially as this will improve buy-in for those who
> > have spent time developing patches. I, for one, would be much more like=
ly
> > to be a more active member of the community if I could see my patches
> > getting committed, rather than spending years in =E2=80=98patch availab=
le=E2=80=99.
> >
> > Would anyone be in favour of a concerted push to get some of these type=
s
> of
> > JIRAs committed?
>
> From my experience you will not gain anything. People have had a year to
> fix the things that interest them. Waiting a bit longer just means more
> things will come in that people think are important.
>
> The solution is the same as it always has been. Release early and release
> often.  You wouldn=E2=80=99t even be suggesting this if you knew another =
release
> would be coming next month.
>
> Ralph
>

--001a113ce2b67c65c3055912aa85--