[
https://issues.apache.org/jira/browse/GEODE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212517#comment-15212517
]
ASF subversion and git services commented on GEODE-874:
-------------------------------------------------------
Commit 0a9771eb548f5bdb087c45e1c3052d9ee6c675c1 in incubator-geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0a9771e ]
GEODE-874: Move build instructions to BUILDING and update README
Place all build-from-source instructions into file BUILDING.md, update
the README.md file to tell people to look in the BUILDING.md file if
appropriate, update the Geode-In-5-Minutes to not include building
instructions, and remove irrelevant files COMPILING.txt and RUNNING.txt
from the repo.
Reword the README.md claim that Geode can do rolling updates between
major versions, as there are no major versions, and we can't make
promises about the future.
This closes #114
> v1.0.0-incubating.M1.RC2: Text file errors in the source distribution
> ---------------------------------------------------------------------
>
> Key: GEODE-874
> URL: https://issues.apache.org/jira/browse/GEODE-874
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Kenneth Howe
> Assignee: Karen Smoler Miller
> Fix For: 1.0.0-incubating.M2
>
>
> gradlew script is not included in the Geode release packages, but it is
> called out in command examples in the following text files in the release
> source distribution:
> COMPILING.txt
> RUNNING.txt
> docker/Dockerfile
> gemfire-spark-connector/doc/1_building.md
> The easy fix is to change "gradlew" to "gradle" in affected files and include
> a requirement for the user to install gradle from gradle.org.
> There was a similar issue with README.md that was fixed for RC2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
