hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@cloudera.com.INVALID>
Subject Re: [DISCUSS] Making 2.10 the last minor 2.x release
Date Fri, 22 Nov 2019 12:29:33 GMT
On Thu, Nov 21, 2019 at 11:49 PM Jonathan Hung <jyhung2357@gmail.com> wrote:

> Thanks for the detailed thoughts, everyone.
>
> Eric (Badger), my understanding is the same as yours re. minor vs patch
> releases. As for putting features into minor/patch releases, if we keep the
> convention of putting new features only into minor releases, my assumption
> is still that it's unlikely people will want to get them into branch-2
> (based on the 2.10.0 release process). For the java 11 issue, we haven't
> even really removed support for java 7 in branch-2 (much less java 8), so I
> feel moving to java 11 would go along with a move to branch 3. And as you
> mentioned, if people really want to use java 11 on branch-2, we can always
> revive branch-2. But for now I think the convenience of not needing to port
> to both branch-2 and branch-2.10 (and below) outweighs the cost of
> potentially needing to revive branch-2.
>


I don't think we should evern support java 11 in branch-2.

"If you want to use a recent version of java - use a recent version of
hadoop"

I've not been backporting my stuff for a long, long time, and my general
stance with branch-2 bug reports on bits of the code that I work on is
"what does it do on hadoop 3.2?"

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message