Hi Denes, sounds like a plan, I am more than happy to help, thank you for the opportunity. I created the umbrella ticket for the release: https://issues.apache.org/jira/browse/FLUME-3162
Let me know if any help need. Best regards, Ferenc Szabo On Mon, Sep 4, 2017 at 10:21 AM, Denes Arvay <de...@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 >
