I just created a PR with some ideas to consider. IMO, telling users to
download unreleased source (such as from our website) would be a problem.
Anthony
> On Jan 17, 2017, at 2:43 PM, Dan Smith wrote:
>
> Rat checks are already there for the examples project, but yeah it needs a
> LICENSE a
Rat checks are already there for the examples project, but yeah it needs a
LICENSE and NOTICE. Do those files need to include everything from the
geode LICENSE and NOTICE files?
That's an interesting question about source archive generation. Do we want
to produce releases of the examples, or just
Also needed: some build work to make this ‘releasable’. For example:
LICENSE / NOTICE
source archive generation with hashes and sigs
rat checks
etc
Anthony
> On Jan 17, 2017, at 10:51 AM, Dan Smith wrote:
>
> Now that the examples are in a separate repository,
Now that the examples are in a separate repository, I think we should setup
a nightly job to build and test that repo. Can someone with access to
jenkins help set this up?
It should run the ./gradlew build on the geode-examples project; but in
order for that to work it needs access to a build of g
