Yes, I found the examples, but having a top-level guided HelloWorld walk
through would be helpful. I’ll hold this thought until we publish the docs and
see what’s there.
Thanks,
Anthony
> On Nov 7, 2018, at 9:01 AM, Jacob Barrett wrote:
>
> There are examples that should cover this.
>
>> O
There are examples that should cover this.
> On Nov 7, 2018, at 8:47 AM, Anthony Baker wrote:
>
> I think the source headers and LICENSE are in good shape. I was able to
> follow BUILDING.md on macOS. At some point it would be nice to provide a
> simple a quick start guide (e.g. How to creat
I think the source headers and LICENSE are in good shape. I was able to follow
BUILDING.md on macOS. At some point it would be nice to provide a simple a
quick start guide (e.g. How to create a geode-native app in 5 simple steps).
Perhaps that is already included in the docs though.
Anthony
geode-native should be ready to go now
On Tue, Oct 30, 2018 at 2:56 PM Dave Barnes wrote:
> unix_index.html and win_index.html cannot simply be removed, as they're
> referenced by Cmake. I created a ticket to address this:
> https://issues.apache.org/jira/browse/GEODE-5958.
>
> On Tue, Oct 30, 2
unix_index.html and win_index.html cannot simply be removed, as they're
referenced by Cmake. I created a ticket to address this:
https://issues.apache.org/jira/browse/GEODE-5958.
On Tue, Oct 30, 2018 at 11:48 AM Dave Barnes wrote:
> Re: the docs links mentioned in Anthony's message:
>
> docs/REA
Re: the docs links mentioned in Anthony's message:
docs/README.md - the reference to the Geode CONTRIBUTE.md file is useful. I
think we can assume that a user of the geode-native API will have a Geode
installation, too.
docs/api/unix_index.html and docs/api/win_index.html - These files (and
their
I ran rat manually and got this:
Files with unapproved licenses:
/geode/.cpackignore
/geode/.lcovrc
/geode/clicache/src/native_shared_ptr.hpp
/geode/templates/security/CMakeLists.txt.forInstall
Shouldn’t these failures be causing travis to fail?
Many of the files rat that marks as binar
There are a lot of files that rat is seeing as binary files and ignoring
the headers. Many of those files are not binary. Perhaps they have the
wrong metadata associated with them in git as a result of bad commits. We
should clean all those files up so that rat is checking everything
correctly.
On
Following up on this - is there anything we still need to do before we cut
the 1.8 release branch in 2 weeks?
Overall I think the native client source code looks like it's in good shape
- we're running rat, the LICENSE and NOTICE look good, no binaries in the
source, etc.
For cutting the release
+1 for a source release. Awesome!
-Dan
On Thu, Oct 11, 2018 at 2:32 PM Michael Oleske wrote:
> Plus 1 for source release. Exciting times we live in!
>
> For verifying, plus one to a pipeline that's not just travis. Though
> they're instructions in the repo about how to run tests to get that
> b
Plus 1 for source release. Exciting times we live in!
For verifying, plus one to a pipeline that's not just travis. Though
they're instructions in the repo about how to run tests to get that
baseline confidence.
-michael
On Wednesday, October 10, 2018, Anilkumar Gingade
wrote:
> Good work team
Good work team.
+1 to get this as part of Geode 1.8 release.
It will be good to see community taking advantage of this. And building new
native client apps.
I assume it will have all the docs about client-server compatibility
version info. And framework for backward compatibility testing with new
g
+1 for a source release
On Wed, Oct 10, 2018 at 12:59 PM Anthony Baker wrote:
> I think starting with a source-only release of the native client is a good
> first step. That lets us focus on verifying that all the tasks outlined in
> [1] are complete and correct.
>
> Anthony
>
> [1] https://is
I think starting with a source-only release of the native client is a good
first step. That lets us focus on verifying that all the tasks outlined in [1]
are complete and correct.
Anthony
[1] https://issues.apache.org/jira/browse/GEODE-1416
> On Oct 10, 2018, at 11:52 AM, Dan Smith wrote:
>
That is awesome! Let's get it in!
I think there are some details to work out:
- Do we need to build any automation for creating the native source
release (similar to ./gradlew srcDist on the java side)?
- Will we release binaries? Which platforms and how to does the release
manager build them?
15 matches
Mail list logo