Avoiding the use of JDK8 language features (and, presumably, APIs) means you've abandoned #1, i.e., you haven't (really) bumped the JDK source version to JDK8.
Also, note that releasing from trunk is a way of achieving #3, it's not a way of abandoning it. On Mon, Mar 9, 2015 at 7:10 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: > Hi Raymie, > > Konst proposed just releasing off of trunk rather than cutting a branch-2, > and there was general agreement there. So, consider #3 abandoned. 1&2 can > be achieved at the same time, we just need to avoid using JDK8 language > features in trunk so things can be backported. > > Best, > Andrew > > On Mon, Mar 9, 2015 at 7:01 PM, Raymie Stata <rst...@altiscale.com> wrote: > >> In this (and the related threads), I see the following three requirements: >> >> 1. "Bump the source JDK version to JDK8" (ie, drop JDK7 support). >> >> 2. "We'll still be releasing 2.x releases for a while, with similar >> feature sets as 3.x." >> >> 3. Avoid the "risk of split-brain behavior" by "minimize backporting >> headaches. Pulling trunk > branch-2 > branch-2.x is already tedious. >> Adding a branch-3, branch-3.x would be obnoxious." >> >> These three cannot be achieved at the same time. Which do we abandon? >> >> >> On Mon, Mar 9, 2015 at 12:45 PM, sanjay Radia <sanjayo...@gmail.com> >> wrote: >> > >> >> On Mar 5, 2015, at 3:21 PM, Siddharth Seth <ss...@apache.org> wrote: >> >> >> >> 2) Simplification of configs - potentially separating client side >> configs >> >> and those used by daemons. This is another source of perpetual confusion >> >> for users. >> > + 1 on this. >> > >> > sanjay >>