This is an automated email from the ASF dual-hosted git repository.
ctubbsii pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/fluo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c3fa231 Jekyll build from gh-pages:4162937
c3fa231 is described below
commit c3fa231837b3d23e23aab3929c1c000ac6828bf5
Author: Christopher Tubbs <ctubb...@apache.org>
AuthorDate: Fri Aug 4 22:52:12 2017 -0400
Jekyll build from gh-pages:4162937
remove incubator from github links
---
contactus/index.html | 2 +-
feed.xml | 4 ++--
how-to-contribute/index.html | 8 ++++----
people/index.html | 2 +-
poweredby/index.html | 2 +-
related-projects/index.html | 2 +-
release-process/index.html | 10 +++++-----
tour/basic-read-write/index.html | 2 +-
tour/index.html | 2 +-
tour/writing-code/index.html | 4 ++--
10 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/contactus/index.html b/contactus/index.html
index 8678372..c73df34 100644
--- a/contactus/index.html
+++ b/contactus/index.html
@@ -164,7 +164,7 @@ current issues.</p>
<ul>
<li><a href="https://github.com/apache/fluo/issues";>Fluo issues</a></li>
<li><a href="https://github.com/apache/fluo-recipes/issues";>Fluo Recipes
issues</a></li>
- <li><a
href="https://github.com/apache/incubator-fluo-website/issues";>Website
issues</a></li>
+ <li><a href="https://github.com/apache/fluo-website/issues";>Website
issues</a></li>
</ul>
<h3 id="irc">IRC</h3>
diff --git a/feed.xml b/feed.xml
index e9500e2..93e0018 100644
--- a/feed.xml
+++ b/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>https://fluo.apache.org//</link>
<atom:link href="https://fluo.apache.org//feed.xml"; rel="self"
type="application/rss+xml" />
- <pubDate>Thu, 27 Jul 2017 15:30:56 +0000</pubDate>
- <lastBuildDate>Thu, 27 Jul 2017 15:30:56 +0000</lastBuildDate>
+ <pubDate>Sat, 05 Aug 2017 02:52:09 +0000</pubDate>
+ <lastBuildDate>Sat, 05 Aug 2017 02:52:09 +0000</lastBuildDate>
<generator>Jekyll v3.3.1</generator>
<item>
diff --git a/how-to-contribute/index.html b/how-to-contribute/index.html
index 6d5e96f..a4721a0 100644
--- a/how-to-contribute/index.html
+++ b/how-to-contribute/index.html
@@ -110,14 +110,14 @@
</header>
<article id="page-content">
- <p>Contributions are welcome to all Apache Fluo repositories (<a
href="https://github.com/apache/fluo";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes";>Fluo Recipes</a>) and the <a
href="https://github.com/apache/incubator-fluo-website";>Fluo project
website</a>. All repositories follow a <a
href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit";>review-then-commit</a>
process.
+ <p>Contributions are welcome to all Apache Fluo repositories (<a
href="https://github.com/apache/fluo";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes";>Fluo Recipes</a>) and the <a
href="https://github.com/apache/fluo-website";>Fluo project website</a>. All
repositories follow a <a
href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit";>review-then-commit</a>
process.
This means that all contributions must pass any integration tests and be
reviewed before being committed. Code reviews are done by commenting on a
GitHub pull request.</p>
<h3 id="contribution-workflow">Contribution workflow</h3>
<ol>
- <li>Make sure you have a fork of the repository (<a
href="https://github.com/apache/fluo";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes";>Fluo Recipes</a>, <a
href="https://github.com/apache/incubator-fluo-website";>Fluo Website</a>) that
you want contribute to.</li>
- <li>Create an issue that describes the work. Each Fluo repository has its
own issue tracker: <a href="https://github.com/apache/fluo/issues";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes/issues";>Fluo Recipes</a>, <a
href="https://github.com/apache/incubator-fluo-website/issues";>Fluo
Website</a></li>
+ <li>Make sure you have a fork of the repository (<a
href="https://github.com/apache/fluo";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes";>Fluo Recipes</a>, <a
href="https://github.com/apache/fluo-website";>Fluo Website</a>) that you want
contribute to.</li>
+ <li>Create an issue that describes the work. Each Fluo repository has its
own issue tracker: <a href="https://github.com/apache/fluo/issues";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes/issues";>Fluo Recipes</a>, <a
href="https://github.com/apache/fluo-website/issues";>Fluo Website</a></li>
<li>
<p>Create a branch in the local clone of your fork. An example branch name
is <code class="highlighter-rouge">fluo-301</code> which describes the repo and
issue number.</p>
@@ -153,7 +153,7 @@ git push origin fluo-301
</code></pre>
</div>
</li>
- <li>Create a pull request on the GitHub page of the repo (e.g. <a
href="https://github.com/apache/fluo";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes";>Fluo Recipes</a>, <a
href="https://github.com/apache/incubator-fluo-website";>Fluo Website</a>) that
you want to contribute to. The pull request should merge your branch (e.g.
<code class="highlighter-rouge">fluo-301</code>) in your fork into the master
branch of the repo.</li>
+ <li>Create a pull request on the GitHub page of the repo (e.g. <a
href="https://github.com/apache/fluo";>Fluo</a>, <a
href="https://github.com/apache/fluo-recipes";>Fluo Recipes</a>, <a
href="https://github.com/apache/fluo-website";>Fluo Website</a>) that you want
to contribute to. The pull request should merge your branch (e.g. <code
class="highlighter-rouge">fluo-301</code>) in your fork into the master branch
of the repo.</li>
<li>At least one committer (and others in the community) will review your
pull request and add any comments to your code.</li>
<li>Reviewers should make comments at bottom of the pull request or in
“Files Changed”. Avoid commenting on commits as these comments will disappear
if the branch is rebased as rebasing generates new commits for the pull
request.</li>
<li>Push any changes from the review to the branch as new commits so the
reviewer only needs to review new changes.</li>
diff --git a/people/index.html b/people/index.html
index 6c6d701..1032340 100644
--- a/people/index.html
+++ b/people/index.html
@@ -168,7 +168,7 @@
<h2 id="contributors">Contributors</h2>
-<p>GitHub also has a <a
href="https://github.com/apache/incubator-fluo/graphs/contributors";>contributor
list</a>
+<p>GitHub also has a <a
href="https://github.com/apache/fluo/graphs/contributors";>contributor list</a>
based on commits.</p>
<table>
diff --git a/poweredby/index.html b/poweredby/index.html
index 3890ab8..63ef6b3 100644
--- a/poweredby/index.html
+++ b/poweredby/index.html
@@ -118,7 +118,7 @@
<li><a href="http://curator.apache.org/";>Apache Curator</a></li>
<li><a href="http://hadoop.apache.org/";>Apache Hadoop</a></li>
<li><a href="http://maven.apache.org/";>Apache Maven</a></li>
- <li><a href="http://twill.incubator.apache.org/";>Apache Twill</a></li>
+ <li><a href="http://twill.apache.org/";>Apache Twill</a></li>
<li><a href="http://zookeeper.apache.org/";>Apache Zookeeper</a></li>
<li><a href="https://dropwizard.github.io/metrics/3.1.0/";>Dropwizard
Metrics</a></li>
<li><a href="http://junit.org/";>Junit</a></li>
diff --git a/related-projects/index.html b/related-projects/index.html
index c8f3183..c78958a 100644
--- a/related-projects/index.html
+++ b/related-projects/index.html
@@ -113,7 +113,7 @@
<p>This page list external projects that build on Apache Fluo and may be
useful.
These projects are not necessarily affiliated with or endorsed by the
<a href="https://www.apache.org/";>Apache Software Foundation</a>. If you would
like to add a project to this
-list, please open an issue or submit a pull request <a
href="https://github.com/apache/incubator-fluo-website";>on Github</a>.</p>
+list, please open an issue or submit a pull request <a
href="https://github.com/apache/fluo-website";>on Github</a>.</p>
<h3 id="projects-using-fluo">Projects Using Fluo</h3>
diff --git a/release-process/index.html b/release-process/index.html
index 0497aed..e96199a 100644
--- a/release-process/index.html
+++ b/release-process/index.html
@@ -114,11 +114,11 @@
<p>Before you can release Fluo or Fluo Recipes, you will need a GPG key. For
information on generating
a key look at this <a href="https://www.apache.org/dev/openpgp.html";>ASF GPG
page</a>. After generating a key,
-add it to the <a
href="https://www.apache.org/dist/incubator/fluo/KEYS";>KEYS</a> file. The <a
href="https://www.apache.org/dist/incubator/fluo/KEYS";>KEYS</a> files contains
instructions for adding to itself. Use the
+add it to the <a href="https://www.apache.org/dist/fluo/KEYS";>KEYS</a> file.
The <a href="https://www.apache.org/dist/fluo/KEYS";>KEYS</a> files contains
instructions for adding to itself. Use the
following command to checkout the svn repository that contains the KEYS files.
Updates to this
repository will eventually sync to the website.</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>svn
co https://dist.apache.org/repos/dist/release/incubator/fluo/
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>svn
co https://dist.apache.org/repos/dist/release/fluo/
</code></pre>
</div>
@@ -178,7 +178,7 @@ for <code class="highlighter-rouge">RCV</code>.</p>
for download at <code
class="highlighter-rouge">https://repository.apache.org/content/repositories/orgapachefluo-REPO_ID</code></li>
<li>Its very important to only close the staging repository and not
release or promote it at this point. Releasing publishes
the artifacts to Maven central and this can not be undone. Releasing is done
after a successful vote.</li>
- <li>When closing, add a comment like <code
class="highlighter-rouge">Apache Fluo (incubating) 1.1.0-rc3</code></li>
+ <li>When closing, add a comment like <code
class="highlighter-rouge">Apache Fluo 1.2.0-rc3</code></li>
</ul>
</li>
<li>
@@ -261,7 +261,7 @@ git branch -d <releaseVersion>-rc<RCV>
</div>
</li>
<li>
- <p>View the <a
href="https://github.com/apache/incubator-fluo-website/blob/master/README.md";>website
README</a> for instructions on how to generate Javadocs and documentation using
+ <p>View the <a
href="https://github.com/apache/fluo-website/blob/master/README.md";>website
README</a> for instructions on how to generate Javadocs and documentation using
the released tag. Submit PR to the website repo to publish.</p>
</li>
<li>
@@ -270,7 +270,7 @@ This is the same svn repo mentioned earlier for the KEYS
file. Follow the <a hr
hashes and signatures. This step publishes the files to the ASF mirrors.</p>
</li>
<li>
- <p>Send an email to <code
class="highlighter-rouge">d...@fluo.incubator.apache.org</code> announcing new
release.</p>
+ <p>Send an email to <code
class="highlighter-rouge">d...@fluo.apache.org</code> announcing new
release.</p>
</li>
</ol>
diff --git a/tour/basic-read-write/index.html b/tour/basic-read-write/index.html
index 5debd2a..995dc33 100644
--- a/tour/basic-read-write/index.html
+++ b/tour/basic-read-write/index.html
@@ -112,7 +112,7 @@
</div>
<div id="tour-content">
<p>The following shows Java code for writing and reading data using Fluo.
In your local clone, modify
-the <code class="highlighter-rouge">exercise(MiniFluo, FluoClient)</code>
function in <a
href="https://github.com/apache/incubator-fluo-website/tree/fluo-tour/src/main/java/ft/Main.java";>src/main/java/ft/Main.java</a>.
Then run
+the <code class="highlighter-rouge">exercise(MiniFluo, FluoClient)</code>
function in <a
href="https://github.com/apache/fluo-website/tree/fluo-tour/src/main/java/ft/Main.java";>src/main/java/ft/Main.java</a>.
Then run
<code class="highlighter-rouge">ft.Main</code> as previously mentioned.</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code>
<span class="kd">private</span> <span class="kd">static</span> <span
class="kt">void</span> <span class="nf">exercises</span><span
class="o">(</span><span class="n">MiniFluo</span> <span
class="n">mini</span><span class="o">,</span> <span class="n">FluoClient</span>
<span class="n">client</span><span class="o">)</span> <span class="o">{</span>
diff --git a/tour/index.html b/tour/index.html
index 6ca7f7b..772ce4e 100644
--- a/tour/index.html
+++ b/tour/index.html
@@ -128,7 +128,7 @@ updated using them. Later in the tour, you can implement
this use case.</p>
<p>We recommend following the tour in order. However, all pages are listed
below for review. When on a
tour page, the left and right keys on the keyboard can be used to navigate.
If you have any
questions or suggestions while going through the tour, please contact us.
There are multiple
-options for getting in touch : <a href="/contactus/">mailing list, IRC</a>,
and <a href="https://github.com/apache/incubator-fluo-website/issues";>Github
Issues</a>. Any
+options for getting in touch : <a href="/contactus/">mailing list, IRC</a>,
and <a href="https://github.com/apache/fluo-website/issues";>Github Issues</a>.
Any
thoughts, solutions, etc related to this tour can also be tweeted using the
hashtag
<a href="https://twitter.com/hashtag/apachefluotour";>#apachefluotour</a>.</p>
diff --git a/tour/writing-code/index.html b/tour/writing-code/index.html
index 79f612e..ac67dd7 100644
--- a/tour/writing-code/index.html
+++ b/tour/writing-code/index.html
@@ -116,7 +116,7 @@ with a basic skeleton that will help you get started
quickly. The commands bel
obtain, edit, and run this basic skeleton.</p>
<div class="language-bash highlighter-rouge"><pre
class="highlight"><code><span class="c">#clone branch with starter code</span>
-git clone -b fluo-tour
https://gitbox.apache.org/repos/asf/incubator-fluo-website fluo-tour
+git clone -b fluo-tour https://gitbox.apache.org/repos/asf/fluo-website
fluo-tour
<span class="nb">cd </span>fluo-tour
<span class="c">#edit Main (all of the following excercises will require
this)</span>
@@ -128,7 +128,7 @@ mvn -q clean compile <span class="nb">exec</span>:java
</div>
<p>Because it is so closely related to the website, this starter code is
located in a branch of Fluo’s
-website. The starter project has its <a
href="https://github.com/apache/incubator-fluo-website/tree/fluo-tour";>own
readme</a> also.</p>
+website. The starter project has its <a
href="https://github.com/apache/fluo-website/tree/fluo-tour";>own readme</a>
also.</p>
</div>
--
To stop receiving notification emails like this one, please contact
['"comm...@fluo.apache.org" <comm...@fluo.apache.org>'].
