I don't know, do you think it makes sense to do the next release before
2.6.0 is released?  Are they done tweaking the API?

Not sure we need a new tag for the RC, but if we do have one it should be
very clear in the tag name that it is not a release, and we shouldn't link
to it from the website or anything.


On Wed, Sep 3, 2014 at 7:49 AM, Sumit Mohanty <[email protected]>
wrote:

> Considering going forward it will be 2.6 only it might be OK.
>
> Should we tag the last release candidate as one for hadoop 2.4 for folks to
> sync to that tag if they need to?
>
>
> On Wed, Sep 3, 2014 at 5:39 AM, Steve Loughran <[email protected]>
> wrote:
>
> > I never got around to doing the final bit of the release: taking it to
> > incubator general.
> >
> > How about we skip that release as an official release and i do one of the
> > latest code
> >
> > The biggest argument against this is that it's hadoop 2.6 only, so the
> #of
> > users will be low
> >
> > -steve
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to