flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bessenyei Balázs Donát <bes...@apache.org>
Subject Re: [DISCUSS] Flume 1.8 release proposal
Date Tue, 12 Sep 2017 09:18:17 GMT
Hi Denes,

It seems to me that 1.8.1 and 1.9.0 releases already exist in our JIRA.

Regarding the retargeting: I'd be happy to batch-edit the necessary
tickets in order to avoid spamming the mailing lists.
Once you have a list of actions you'd like to do, please let us know.

Thank you,


2017-09-11 19:39 GMT+02:00 Denes Arvay <denes@cloudera.com>:
> Hi All,
> I'd like to let you know that we are planning to cut the 1.8 branch
> tomorrow around 2am PDT.
> If you think that there any important tickets targeted to 1.8 still open
> which needs to be reviewed and committed to get into the release, please
> let us know as soon as possible and we'll do our best to push it through.
> The ones which couldn't get committed by the branching will be retargeted
> to 1.8.1 or 1.9, depending on their type (i.e. bug fixes will be retargeted
> to 1.8.1, new features will be scheduled for 1.9).
> For this I'd like to ask our PMC members to create these new releases in
> Jira, or if it's possible to grant the required Jira permissions to me, I'd
> be more than happy to do this.
> Thank you,
> Denes
> On Mon, Sep 4, 2017 at 10:21 AM Denes Arvay <denes@cloudera.com> wrote:
>> Hi Flume Community,
>> Almost a year passed since we've released Flume 1.7.
>> More than 50 commits were pushed since then, including documentation
>> fixes, many critical bug fixes and several important features, so I'd like
>> to propose to publish the next minor release of Flume.
>> I'd be happy to be the Release Manager with the help of Ferenc Szabo and
>> Marcell Hegedus who have been quite active recently, and Balazs Donat
>> Bessenyei who took the lion's share of the work during the previous release
>> - if both community and they are OK with it.
>> Among others the following major changes will be included in the next
>> release:
>> Fixed bugs:
>> - FLUME-2857. Make Kafka Source/Channel/Sink restore default values when
>> live updating config
>> - FLUME-2812. Fix semaphore leak causing java.lang.Error: Maximum permit
>> count exceeded in MemoryChannel
>> - FLUME-3020. Improve HDFS Sink escape sequence substitution
>> - FLUME-3027. Change Kafka Channel to clear offsets map after commit
>> - FLUME-3049. Make HDFS sink rotate more reliably in secure mode
>> - FLUME-3080. Close failure in HDFS Sink might cause data loss
>> - FLUME-3085. HDFS Sink can skip flushing some BucketWriters, might lead
>> to data loss
>> - FLUME-2752. Fix AvroSource startup resource leaks
>> - FLUME-2905. Fix NetcatSource file descriptor leak if startup fails
>> New features:
>> - FLUME-2171. Add Interceptor to remove headers from event
>> - FLUME-2993. Add support for environment variables in configuration files
>> - New component: HTTP Sink
>> - FLUME-3100. Support arbitrary header substitution for topic of Kafka Sink
>> - FLUME-2917. Provide netcat UDP source as alternative to TCP
>> There are 35 open tickets targeted for 1.8 in patch available state:
>> https://s.apache.org/flume-1.8-target-tickets
>> Plus we also have quite a lot (~65) open pull requests on GitHub:
>> https://github.com/apache/flume/pulls
>> Some of the above mentioned tickets/pull requests already have some review
>> comments, so at least part of this list can get into this release beside
>> the already pushed ones.
>> I'd like to propose to target the week of 11th of September with the first
>> release candidate. That'd mean that the branch date would be the 11th, any
>> significant code change should get in by that date.
>> If nobody has any concerns then I'm going to create an umbrella ticket to
>> track the release process.
>> Kind regards,
>> Denes

View raw message