flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denes Arvay <de...@cloudera.com>
Subject Re: [DISCUSS] Flume 1.8 release proposal
Date Wed, 13 Sep 2017 14:06:17 GMT
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’m not overly in favour of rushing a release out when we have many JIRAs
> > with patches submitted, especially when some of those are +1’d 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’t speak of a mature and active community process - I’d much
> > rather that we pause a little, have a big effort by the committers to get
> > 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 likely
> > to be a more active member of the community if I could see my patches
> > getting committed, rather than spending years in ‘patch available’.
> >
> > Would anyone be in favour of a concerted push to get some of these types
> 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’t even be suggesting this if you knew another release
> would be coming next month.
>
> Ralph
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message