I think I agree. We should try the same release cycle for all components until we find we can't.
-Jake On Thu, Jan 19, 2017 at 11:21 AM Dan Smith <dsm...@pivotal.io> wrote: > I wonder if we're trying to overcomplicate things there. I don't see why > the geode-examples wouldn't use the same release schedule and version > number as geode. > > The C++ and .NET clients are also somewhat tied to the version of geode > that they support. As long as we can stick to a regular release cadence, It > seems like those clients couldn't also follow the same release schedule and > version numbers. > > -Dan > > 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. > > > > Anthony > > > > [1] https://github.com/apache/geode-examples/blob/develop/ > > gradle.properties#L17 > > > > >
