Hi Lyndon, Maybe you're getting confused between what language levels geode supports and what language level geode code is written in? We don't need different branches to support java 8, java 9, etc. Geode should already work with later versions of java. If there are issues running on java 8 or 9 those should just get filed and fixed.
Geode is current written in java 7 so that we can continue to support java 7 users. We may want to drop java 7 at some point to make life better for geode *developers*, but geode *users* should already be able to use the latest JVM versions. -Dan On Tue, Jul 28, 2015 at 2:10 AM, Lyndon Adams <[email protected]> wrote: > Maybe run independent got branches for each JVM version that way users can > get early access to latest supported JVM releases > > Sent from my iPhone > > On 27 Jul 2015, at 19:19, Kirk Lund <[email protected]> wrote: > > The key here is probably to replace the term "customer" with "user". As > long as "users" want or need to use Geode in JDK 1.7 then we need to keep > 1.7 in the picture. Users can of course participate in the community, and > it's up to those of us in the community to represent them as best we can. > > If you want to propose moving the build to 1.8, then I think you would > simply propose that on the dev@geode email list. Then everyone on the > Geode PMC could discuss it or even vote on it. > > Ultimately, it probably comes down to this: if each person in the Geode > PMC group believes that all "users" are ready to leave 1.7 behind and move > to 1.8, then they should vote +1, else they should vote -1. > > Even though there hasn't been a Geode release yet, we probably have to > assume or at least hope that existing GemFire users will eventually become > Geode users. > > -Kirk > > On Mon, Jul 27, 2015 at 10:27 AM, Lyndon Adams <[email protected]> > wrote: > >> "Customer support" is a paid service, Geode is for all. Geode OSS should >> sit on the curve of technology evolution and should embrace all advances >> with velocity. Thus any reference to "customer" should not be a concern for >> the Geode vision and code base. >> >> The decision of language level should be driven by OSS community and the >> general Apache minimum supported JVM platform. >> >> Just a penny for my thoughts. >> >> Lyndon Adams >> London, SW11 >> >> On 27 Jul 2015, at 18:17, John Blum <[email protected]> wrote: >> >> I would caution that Java 6 and 7 will be around for quite sometime >> despite Oracle's EOL policy for Java 6/7. There shall be (extended) >> "supported" versions of Java 6 and 7 runtimes running in customer sites for >> sometime... >> >> >> http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings >> >> Most application servers still ship with Java 6, don't even fully support >> the Java 7 spec, and have opted to start moving directly to Java 8 support, >> no double because they are lagging behind and that Java 7 was not really a >> huge success. >> >> For the first time ever, the core *Spring Framework* will concurrently >> support and run on Java 6, 7, 8, and 9. This is significant because it >> allows newer Java features to be used with the core SF based application >> while simultaneously preserving compatibility with older runtimes. >> >> Of course, the core *Spring Framework* dwarfs GemFire/Geode >> installations several orders of magnitude over, and the core SF is highly >> modular unlike GemFire/Geode that enables certain parts of the Framework to >> leverage Java 8 features that are not necessarily required by applications. >> >> Food for thought. >> >> On Mon, Jul 27, 2015 at 10:06 AM, William Markito Oliveira < >> [email protected]> wrote: >> >>> +1 for JDK 8 / Language Level 8 as well. >>> >>> Please remember that JDK 7 is already no longer updated - >>> https://www.java.com/en/download/faq/java_7.xml since April/2015. >>> >>> >>> ~/William >>> >>> On Jul 27, 2015, at 9:43 AM, Kirk Lund <[email protected]> wrote: >>> >>> True enough! I guess there's nothing preventing us from moving Geode to >>> JDK 1.8 now. >>> >>> >>> On Mon, Jul 27, 2015 at 9:39 AM, Lyndon Adams <[email protected]> >>> wrote: >>> >>>> Why do you need to wait until "customers move to 1.8" when geode is an >>>> open source product? Surely customers are using a paid support version. Am >>>> I missing something? >>>> >>>> Lyndon Adams >>>> London, SW11 >>>> >>>> On 25 Jul 2015, at 07:33, Kirk Lund <[email protected]> wrote: >>>> >>>> Oi João, >>>> >>>> Our current source code level is Java 1.7. We just added 1.8 support >>>> meaning that we build/compile the product under 1.7 JDK and then >>>> test with both 1.7 and 1.8 JREs. >>>> >>>> We won't be able to drop 1.7 support until all customers move to 1.8 >>>> (hopefully soon but probably not in 2015). >>>> >>>> -Kirk >>>> >>>> On Friday, July 24, 2015, João Peixoto <[email protected]> wrote: >>>> >>>>> Thanks (obrigado ;) ) William. >>>>> >>>>> If I were to contribute to the project with a PR, which level should I >>>>> respect? >>>>> >>>>> On Fri, Jul 24, 2015 at 9:40 PM William Markito <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi João (Opa, tudo bem ?) >>>>>> >>>>>> Actually it's supposed to be Java 7 but there are areas that needs to >>>>>> be updated. >>>>>> >>>>>> But you should be also fine to run and compile with Java 8. >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>> > On Jul 24, 2015, at 9:32 PM, João Peixoto <[email protected]> >>>>>> wrote: >>>>>> > >>>>>> > I'm looking at the source code and I was wondering what is the >>>>>> language level that Geode is aiming for. Currently it seems compatible >>>>>> with >>>>>> Java 1.6, wondering if that minimum will be raised. >>>>>> >>>>> >>> >>> >> >> >> -- >> -John >> 503-504-8657 >> john.blum10101 (skype) >> >> >
