On Wed, 24 Oct 2018 21:13:53 -0700
Julian Hyde <[email protected]> wrote:
Regarding binary artifacts. I really don’t know how to review them.
I started a discussion thread on general@incubator[1].
I don't think it is feasible to put license headers in each rst
file. I checked multiple other projects
and non of them do this, that is why I excluded the doc directory.
CouchDB uses the “..” syntax. See [2].
Ok. We will add the license to all the rst files and revert the rat
excludes.
We switched to the Apache parent pom for the release and have not
figured out yet how to fix the naming and some other issues, but we
have opened a JIRA to investigate:
https://jira.apache.org/jira/projects/CRAIL/issues/CRAIL-56
We solved this one in Calcite. I’ve added comments to the JIRA case.
Thanks, we will take a look and implement the changes for the next rc.
Our new documentation (linked in the readme and on the webpage)
talks about how to build Crail:
https://incubator-crail.readthedocs.io/en/latest/source.html
Or do you want this to be part of the call for vote email?
Definitely not in the vote email - it’s not for my benefit, it’s for
whoever downloads the source tarball.
I see now that there’s a line in README.md, "Please check out the
documentation for information about how to deploy, run, test and
program against Crail”. Sorry I missed it.
Julian
[1]
https://lists.apache.org/thread.html/ceb357513ff0403414b5fff7dbeb1ea43961e71f9e48425d6e3cea8f@%3Cgeneral.incubator.apache.org%3E
<https://lists.apache.org/thread.html/ceb357513ff0403414b5fff7dbeb1ea43961e71f9e48425d6e3cea8f@%3Cgeneral.incubator.apache.org%3E>
[2]
https://raw.githubusercontent.com/apache/couchdb-documentation/master/src/intro/why.rst
<https://raw.githubusercontent.com/apache/couchdb-documentation/master/src/intro/why.rst>
