On Thu, Jan 19, 2017 at 7:55 AM, Anthony Baker <aba...@pivotal.io> wrote: > Currently our JIRA versions look like this: > > 1.0.0-incubating.M1 > 1.0.0-incubating.M2 > 1.0.0-incubating.M3 > 1.1.0 > > That works great for the geode repo. However, what about the geode-examples > repo? I would like to set a ‘Fix version’ that matches the version in [1]. > Since the repos can release independently of each other, I think we need a > way to completely disambiguate versions like ‘geode-examples-0.1’. We could > also ask for a JIRA project for each repo. Thoughts? > > More stuff: > > - GEODE-2318 didn’t get updated with commit logs from geode-examples. Anyone > know how to fix this? > - Travis-CI is now running on geode-examples. If you notice problems with > PR’s or email notifications let me know.
This is the slippery slope I was alluding to. If the repos, releases, etc. are asynchronous in the eyes of ASF it strongly suggests that communities are asynchronous as well. Which means you're really two separate ASF projects. Which may, very well, be the case I just wanted to point it out. Thanks, Roman.
