This is an automated email from the ASF dual-hosted git repository.

srdo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git


The following commit(s) were added to refs/heads/master by this push:
     new b310340  Remove reference to storm-deploy, which looks dead. Link to 
download page on storm.apache.org instead of github for download links. Fix 
link to newbie issues in DEVELOPER.md
     new b9ab5e5  Merge pull request #3018 from srdo/doc-changes
b310340 is described below

commit b3103407ccd84596422733dba72cdb191844623d
Author: Stig Rohde Døssing <s...@apache.org>
AuthorDate: Sat Jun 1 11:39:30 2019 +0200

    Remove reference to storm-deploy, which looks dead. Link to download page 
on storm.apache.org instead of github for download links. Fix link to newbie 
issues in DEVELOPER.md
---
 DEVELOPER.md                       | 2 +-
 docs/Pacemaker.md                  | 2 +-
 docs/Setting-up-a-Storm-cluster.md | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/DEVELOPER.md b/DEVELOPER.md
index 8fd8b83..0000e78 100644
--- a/DEVELOPER.md
+++ b/DEVELOPER.md
@@ -90,7 +90,7 @@ _If you are interested in contributing code to Storm but do 
not know where to be
 In this case you should
 [browse our issue tracker for open issues and 
tasks](https://issues.apache.org/jira/browse/STORM/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel).
 You may want to start with beginner-friendly, easier issues
-([newbie 
issues](https://issues.apache.org/jira/browse/STORM-58?jql=project%20%3D%20STORM%20AND%20labels%20%3D%20newbie%20AND%20status%20%3D%20Open)
+([newbie 
issues](https://issues.apache.org/jira/issues/?jql=project%20%3D%20STORM%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20newbie)
 and
 [trivial 
issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+STORM+AND+resolution+%3D+Unresolved+AND+priority+%3D+Trivial+ORDER+BY+key+DESC&mode=hide))
 because they require learning about only an isolated portion of the codebase 
and are a relatively small amount of work.
diff --git a/docs/Pacemaker.md b/docs/Pacemaker.md
index 5fc789c..75fa748 100644
--- a/docs/Pacemaker.md
+++ b/docs/Pacemaker.md
@@ -19,7 +19,7 @@ The corresponding Pacemaker client is a plugin for the 
`ClusterState` interface,
  - `pacemaker.servers` : The hosts that the Pacemaker daemons are running on
  - `pacemaker.port` : The port that Pacemaker will listen on
  - `pacemaker.max.threads` : Maximum number of threads Pacemaker daemon will 
use to handle requests.
- - `pacemaker.childopts` : Any JVM parameters that need to go to the 
Pacemaker. (used by storm-deploy project)
+ - `pacemaker.childopts` : Any JVM parameters that need to go to the 
Pacemaker. 
  - `pacemaker.auth.method` : The authentication method that is used (more info 
below)
 
 #### Example
diff --git a/docs/Setting-up-a-Storm-cluster.md 
b/docs/Setting-up-a-Storm-cluster.md
index d770a58..ea05da4 100644
--- a/docs/Setting-up-a-Storm-cluster.md
+++ b/docs/Setting-up-a-Storm-cluster.md
@@ -3,7 +3,7 @@ title: Setting up a Storm Cluster
 layout: documentation
 documentation: true
 ---
-This page outlines the steps for getting a Storm cluster up and running. If 
you're on AWS, you should check out the 
[storm-deploy](https://github.com/nathanmarz/storm-deploy/wiki) project. 
[storm-deploy](https://github.com/nathanmarz/storm-deploy/wiki) completely 
automates the provisioning, configuration, and installation of Storm clusters 
on EC2. It also sets up Ganglia for you so you can monitor CPU, disk, and 
network usage.
+This page outlines the steps for getting a Storm cluster up and running. 
 
 If you run into difficulties with your Storm cluster, first check for a 
solution is in the [Troubleshooting](Troubleshooting.html) page. Otherwise, 
email the mailing list.
 
@@ -37,7 +37,7 @@ These are the versions of the dependencies that have been 
tested with Storm. Sto
 
 ### Download and extract a Storm release to Nimbus and worker machines
 
-Next, download a Storm release and extract the zip file somewhere on Nimbus 
and each of the worker machines. The Storm releases can be downloaded [from 
here](http://github.com/apache/storm/releases).
+Next, download a Storm release and extract the zip file somewhere on Nimbus 
and each of the worker machines. The Storm releases can be downloaded [from 
here](../../downloads.html).
 
 ### Fill in mandatory configurations into storm.yaml
 

Reply via email to