On Sep 11, 2014, at 3:29 PM, Haohui Mai <h...@hortonworks.com> wrote:
> Though I myself have to take the blame of creating these divergences -- I
> wonder, is it acceptable to resolve these divergences, by committing these
> patches that remove JSP UI to branch-2?
...
>
> Thoughts?
a) We have three years of patches sitting in trunk.
b) What makes this code harder to deal with than other incompatible
changes?
c) We have three years of patches sitting in trunk.
d) Why is the 2.6 change list so fricking huge?
e) We have three years of patches sitting in trunk.
f) We as a community clearly learned nothing about the fiasco that was
1.x -> 2.x.
g) We have three years of patches sitting in trunk.
To summarize:
Let's stop shipping branch-2 (so no 2.6 release) and ship trunk
instead. Some ops teams I've talked to have basically said that 2.6 is looking
to be a release to skip because it is bound to broken with as much churn has
happened in it. Let's bite the bullet, start getting serious about 3.x and
work on that instead. There is more than enough "new stuff" in it, ignoring
2.6, to make it a viable major release.
