> if you unbundle your spark connector from Geode releases how do you know that a given Geode release actually works with it?
Because the Spark Connector will depend on (i.e. have been developed and tested with) a specific version of Apache Geode, and is not guaranteed to work with downstream releases after that version, nor necessarily before that version, though, generally, backwards compatibility is always preferable. The Spring IO platform is a prime example of a curated set of tested and guaranteed to work dependencies within and across the entire Spring ecosystem including all 3rd party dependencies (some 300+ in total). This is exactly the relationship <https://github.com/spring-projects/spring-data-gemfire/blob/apache-geode/gradle.properties#L3> [0] between Spring Data GemFire and Apache Geode right now. -j [0] - https://github.com/spring-projects/spring-data-gemfire/blob/apache-geode/gradle.properties#L3 On Mon, Jul 6, 2015 at 2:58 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > On Thu, Jul 2, 2015 at 5:39 PM, Anthony Baker <aba...@pivotal.io> wrote: > >> > >> We are wondering wether to have this as part of Geode repo or on > separate > >> public GitHub repo? > >> > > > > I think the spark connector belongs in the geode community, which > implies the geode ASF repo. > > I think we can address the other concerns technically. > > I am very much +1 on this. The biggest hurdle Geode community has in front > of it is having its first ASF incubating release. Having one artifact to > worry > about would be way simpler. > > Later on, you may entertain a question of having an independent > subproject, but > that's later. > > >> General Question: > >> Can a module under Geode repo be released independent of Geode Release. > >> E.g.: Can we release the connector without tied to Geode release? > > > > This is an interesting question I don’t know the answer to. However, I > think we can > > handle this by creating a geode release frequently enough to satisfy our > community. > > Huge +1 to the above. Release early, release often and validate > strongly. The later > point is actually very much relevant to this discussion: if you > unbundle your spark > connector from Geode releases how do you know that a given Geode > release actually > works with it? I hope you test. But once you do -- you may as well release > it. > > Thanks, > Roman. > -- -John 503-504-8657 john.blum10101 (skype)
