On Wed, Jul 1, 2015 at 5:42 PM, John Blum <[email protected]> wrote: > Another item to add to the "report" is that I have updated *Spring Data > GemFire* to include support for *Apache Geode*. Therefore it is not > possible to build Spring/Java-based applications that use Apache Geode > under-the-hood. I wrote about this on the spring.io/blog here... > https://spring.io/blog/2015/06/12/spring-data-gemfire-supports-apache-geode > > This article caught the attention of DZone (thanks to the help of Pieter > Humphrey) and was republished here... > http://java.dzone.com/articles/spring-data-gemfire-supports > > Cheers! > -John > > While we appreciate the effort and the additional users Spring integration will eventually bring, please do not point the general public to unreleased Geode code.
This disclaimer: > So, why announce a “snapshot-like” release when traditional Spring release announcements > center around milestones, release candidates and final GA? > Mainly because *Apache Geode* has no official releases yet. But more importantly, we want to > give developers a chance to try out *Apache Geode* in Spring-based applications using > *Spring Data GemFire* in order to get feedback as soon as possible. Fails to adequately express the risk to downstream users of relying on the Geode prior to it having a release. Especially given that the first release is blocked *on a licensing issue*, this is inappropriate. -- Sean
