Moving to Java 7 post java 1.6 would be nice. Would be good to time the switch so that it is in lock step with hadoop. Not clear if there will be clear sign indicating that hadoop has switched. -roshan
On 2/12/15 1:50 PM, "Johny Rufus" <[email protected]> wrote: >Hi Hari, > >I am interested in doing the release management for 1.6. > > >Thanks, >Rufus > >On Thu, Feb 12, 2015 at 12:13 PM, Hari Shreedharan < >[email protected]> wrote: > >> Hi fellow devs, >> >> >> Hadoop just released 2.6 which is their last release on Java 6. Since >>Java >> 6 was EOL-ed a long time ago, we should think about doing that in Flume >>as >> well. To make sure we have all the recent features committed available >>for >> users of Java 6, we should do that only once 1.6 is released. So in this >> email, I want to propose two things: >> >> >> 1. Release 1.6 as soon as possible. Any one from the community who is >> interested in doing the release management for this release, please let >>me >> know. I will gladly mentor you :-) >> 2. Post 1.6, drop Java 6 support - so things like Java 7-only >> DirectoryWatcher API can be used for things like SpoolDir or a Tail >>Source. >> >> >> Let me know if anyone disagrees with blocking Java 6. >> >> >> >> Thanks, Hari
