Actually the Java 7 thing is just so that we can finally use Java 7 API. So
moving to 8 and then targeting 7 would work fine I think.

So when I meant release volunteering is that the volunteer would do the
release, and I can push the bits out.

On Thursday, February 12, 2015, Ashish <[email protected]> wrote:

> Java 7 shall be EOLed in April 2015. Any issues in moving directly to
> 1.8 (perhaps generate target binary with 1.7 version if needed)? Just
> a wild thought :) Perhaps after migration we can move to 2.0 and do
> some breaking changes as well :)
>
> I am not sure but don't think anyone other than committer can do a
> release, else he won't be able to push generated stuff and website
>
> Johny would be able to release faster than me, believe he is co-located.
>
> thanks
> ashish
>
>
>
> On Fri, Feb 13, 2015 at 4:03 AM, Hari Shreedharan
> <[email protected] <javascript:;>> wrote:
> > Yep, to be clear - Flume 1.6 will still have to be Java 6, since we
> added a bunch of features which never got shipped for Java 6. So we will
> switch to Java 7 only after the 1.6 release
> >
> >
> >
> >
> > Thanks, Hari
> >
> > On Thu, Feb 12, 2015 at 1:53 PM, Johny Rufus <[email protected]
> <javascript:;>> 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] <javascript:;>> 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
>
>
>
> --
> thanks
> ashish
>
> Blog: http://www.ashishpaliwal.com/blog
> My Photo Galleries: http://www.pbase.com/ashishpaliwal
>

Reply via email to