In a few recent email threads [1] [2] [3] we discussed repos and versioning. After reviewing the comments, the consensus seems to be this:
1) Move the native client source into a new repo. 2) Manage the geode-* repos with common versioning and releases in a single community. I suggest the following actions: 1) Update the version in geode-examples to 1.2.0-SNAPSHOT to match the geode repo. Plan on including the geode-examples source in the 1.2.0 release. 2) Create a geode-nativelicent repo and move the next-gen-native-client-software-grant branch to the new repo on the develop branch. 3) Update the release wiki [4] to include instructions on creating release artifacts for geode-examples and geode-nativeclient (when ready). Thoughts? Anthony [1] http://mail-archives.apache.org/mod_mbox/geode-dev/201701.mbox/%3cdb3f0e86-1d8f-4acc-8323-fe8c135b3...@pivotal.io%3e [2] http://mail-archives.apache.org/mod_mbox/geode-dev/201701.mbox/%3cCAA1wVxqdvaOZVPFHcDu77P=7lqbmwgk+hhzrpw4jqqhh3ve...@mail.gmail.com%3e [3] http://mail-archives.apache.org/mod_mbox/geode-dev/201701.mbox/%3cca+oe_e3m0vtzxxsko5ejadyjo4x1przvlxudwrwuq2ympiw...@mail.gmail.com%3e [4] https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
