Skip to content

Conversation

@AhyoungRyu
Copy link
Contributor

What is this PR for?

Lately, an official location of Zeppelin was changed from https://github.com/apache/incubator-zeppelin.git to http://git.apache.org/incubator-zeppelin.git. So I changed the old location in several documentations to the latest one.

What type of PR is it?

Documentation

Todos

Is there a relevant Jira issue?

ZEPPELIN-657

How should this be tested?

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No

### Getting the source code
First of all, you need the Zeppelin source code. The official location for Zeppelin is [https://github.com/apache/incubator-zeppelin](https://github.com/apache/incubator-zeppelin)
## Getting the source code
First of all, you need Zeppelin source code. The official location of Zeppelin is [http://git.apache.org/incubator.git](http://git.apache.org/incubator-zeppelin.git).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[http://git.apache.org/incubator.git](http://git.apache.org/incubator-zeppelin.git)
I think this should be
[http://git.apache.org/incubator-zeppelin.git](http://git.apache.org/incubator-zeppelin.git)

@felixcheung
Copy link
Member

shouldn't it be git: instead of http:?
git://git.apache.org/incubator-zeppelin.git

echo '# git clone the incubator-zeppelin branch into this directory'
echo
echo 'git clone https://github.com/apache/incubator-zeppelin.git'
echo 'git clone http://git.apache.org/incubator.git'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same for this

@AhyoungRyu
Copy link
Contributor Author

@felixcheung yeah, you're right. I changed all of the locations and also applied it to CONTRIBUTING.md.

CONTRIBUTING.md Outdated
```

You may also want to develop against a specific release. For example, for branch-0.1
You may also want to develop against a specific release. For example, for branch-0.5.6
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Precisely, releases are available through tag in v[X].[Y].[Z] format. Let's change sentence from ... against a specific release. ... to ... against a specific branch.

@AhyoungRyu
Copy link
Contributor Author

@Leemoonsoo I changed them in two files and pushed again : )

@Leemoonsoo
Copy link
Member

Thanks. LGTM

@felixcheung
Copy link
Member

LGTM

@Leemoonsoo
Copy link
Member

Thanks @AhyoungRyu I'm merging it.

@asfgit asfgit closed this in 0d4c3ac Feb 11, 2016
prabhjyotsingh pushed a commit to prabhjyotsingh/zeppelin that referenced this pull request Feb 11, 2016
…tation

### What is this PR for?
Lately, an official location of Zeppelin was changed from **https://github.com/apache/incubator-zeppelin.git** to **http://git.apache.org/incubator-zeppelin.git**. So I changed the old location in several documentations to the latest one.

### What type of PR is it?
Documentation

### Todos

### Is there a relevant Jira issue?
[ZEPPELIN-657](https://issues.apache.org/jira/browse/ZEPPELIN-657)

### How should this be tested?

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: Ryu Ah young <fbdkdud93@hanmail.net>

Closes apache#700 from AhyoungRyu/ZEPPELIN-657 and squashes the following commits:

2144bcc [Ryu Ah young] ZEPPELIN-657: Change 'release' -> 'branch' in howtocontribute.md
813b438 [Ryu Ah young] ZEPPELIN-657: Change 'release' -> 'branch'
23646e5 [Ryu Ah young] ZEPPELIN-657: Fix the wrong locations
c4bef6c [Ryu Ah young] ZEPPELIN-657: fix a typo in howtocontribute.md
a5fb130 [Ryu Ah young] ZEPPELIN-657: Change the official location of Zeppelin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants