Website updates for 0.13.0 release

Jacob Maes · Jacob Maes · commit 29cf374c5cbb · 2017-06-07T10:50:20.000-07:00
Author: Jacob Maes <jmaes@linkedin.com> Reviewers: Jagadish <jvenkatr@linkedin.com>, Prateek Maheshwari <pmaheshw@linkedin.com> Closes apache#215 from jmakes/samza-0.13.0-website
diff --git a/RELEASE.md b/RELEASE.md
@@ -24,7 +24,7 @@ And before you proceed, do the following steps:
 
    * create a branch $VERSION from the latest master branch
    * checkout the $VERSION branch
-   * update the gradle.property s.t. the following property is $VERSION w/o the suffix '-SNAPSHOT':
+   * update the gradle.properties s.t. the following property is $VERSION w/o the suffix '-SNAPSHOT':
       version=$VERSION
    * change the samza_executable variable in samza-test/src/main/python/configs/tests.json to point to a Samza version w/o the suffix '-SNAPSHOT'
    * push the changes to the $VERSION branch
diff --git a/docs/README.md b/docs/README.md
@@ -68,19 +68,29 @@ Following can be done when updating the gradle.properties file
 
 1. in x.x.x branch,
 
-    * modify the docs/_config.yml to make the "version" and "latest-release" to x.x.x
+    * modify the docs/_config.yml to make both the "version" and "latest-release" properties to x.x.x
 
-    * remove "git checkout latest" in docs/startup/hello-samza/versioned/index.md
+    * remove "git checkout latest" line and the "-SNAPSHOT" version suffix in each of the tutorials
+      * docs/startup/hello-samza/versioned/index.md
+      * docs/learn/tutorials/versioned/hello-samza-high-level-code.md
+      * docs/learn/tutorials/versioned/hello-samza-high-level-yarn.md
+      * docs/learn/tutorials/versioned/hello-samza-high-level-zk.md
 
 2. in master branch,
 
     * modify the docs/_config.yml to make the "latest-release" to x.x.x
 
-    * add the x.x.x release to Archive category in docs/_layout/default.html and x.x.x release part in docs/archive/index.html
+    * add the x.x.x release to Archive category in docs/_layouts/default.html and x.x.x release part in docs/archive/index.html
 
     * update the download page to use x.x.x release
-
-    * update the version number in "tar -xvf ./target/hello-samza-y.y.y-dist.tar.gz -C deploy/samza" in docs/startup/hello-samza/versioned/index.md
+      * docs/startup/download/index.md
+
+    * update the version number in "tar -xvf ./target/hello-samza-y.y.y-dist.tar.gz -C deploy/samza" in each of the tutorials (and search for other uses of version x.x.x which may need to be replaced with y.y.y)
+      * docs/startup/hello-samza/versioned/index.md
+      * docs/learn/tutorials/versioned/hello-samza-high-level-code.md
+      * docs/learn/tutorials/versioned/hello-samza-high-level-yarn.md
+      * docs/learn/tutorials/versioned/hello-samza-high-level-zk.md
+      * docs/learn/tutorials/versioned/samza-rest-getting-started.md
 
 After apache mirrors pick up the new release,
 
diff --git a/docs/_config.yml b/docs/_config.yml
@@ -25,4 +25,4 @@ exclude: [_docs]
 baseurl: http://samza.apache.org
 version: latest
 # this is the version you will go if you click 'switch version' in "latest" pages.
-latest-release: '0.12'
+latest-release: '0.13'
diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html
@@ -103,6 +103,7 @@ <h1><i class="fa fa-code"></i> Contribute</h1>
             <h1><i class="fa fa-history"></i> Archive</h1>
             <ul>
               <li><a href="/archive/index.html#latest">latest</a></li>
+              <li><a href="/archive/index.html#13">0.13</a></li>
               <li><a href="/archive/index.html#12">0.12</a></li>
               <li><a href="/archive/index.html#11">0.11</a></li>
               <li><a href="/archive/index.html#10">0.10</a></li>
diff --git a/docs/archive/index.html b/docs/archive/index.html
@@ -27,6 +27,14 @@ <h4 id="latest">Latest Release</h4>
   <li><a href="../startup/hello-samza/latest">Hello Samza</a></li>
 </ul>
 
+<h4 id="13">0.13 Release</h4>
+
+<ul class="documentation-list">
+  <li><a href="../learn/documentation/0.13">Documentation</a></li>
+  <li><a href="../learn/tutorials/0.13">Tutorials</a></li>
+  <li><a href="../startup/hello-samza/0.13">Hello Samza</a></li>
+</ul>
+
 <h4 id="12">0.12 Release</h4>
 
 <ul class="documentation-list">
diff --git a/docs/learn/tutorials/versioned/deploy-samza-job-from-hdfs.md b/docs/learn/tutorials/versioned/deploy-samza-job-from-hdfs.md
@@ -24,7 +24,7 @@ This tutorial uses [hello-samza](../../../startup/hello-samza/{{site.version}}/)
 ### Upload the package
 
 {% highlight bash %}
-hadoop fs -put ./target/hello-samza-0.12.0-dist.tar.gz /path/for/tgz
+hadoop fs -put ./target/hello-samza-0.13.1-dist.tar.gz /path/for/tgz
 {% endhighlight %}
 
 ### Add HDFS configuration
diff --git a/docs/learn/tutorials/versioned/deploy-samza-to-CDH.md b/docs/learn/tutorials/versioned/deploy-samza-to-CDH.md
@@ -34,15 +34,15 @@ mvn clean package -Dhadoop.version=cdh5.4.0
 There are a few ways of uploading the package to the cluster's HDFS. If you do not have the job package in your cluster, **scp** from you local machine to the cluster. Then run
 
 {% highlight bash %}
-hadoop fs -put path/to/hello-samza-0.12.0-dist.tar.gz /path/for/tgz
+hadoop fs -put path/to/hello-samza-0.13.1-dist.tar.gz /path/for/tgz
 {% endhighlight %}
 
 ### Get Deploying Scripts
 
 Untar the job package (assume you will run from the current directory)
 
 {% highlight bash %}
-tar -xvf path/to/samza-job-package-0.12.0-dist.tar.gz -C ./
+tar -xvf path/to/samza-job-package-0.13.1-dist.tar.gz -C ./
 {% endhighlight %}
 
 ### Add Package Path to Properties File
diff --git a/docs/learn/tutorials/versioned/hello-samza-high-level-yarn.md b/docs/learn/tutorials/versioned/hello-samza-high-level-yarn.md
@@ -63,7 +63,7 @@ Then, you can continue w/ the following command in hello-samza project:
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-0.13.0-SNAPSHOT-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-0.13.1-SNAPSHOT-dist.tar.gz -C deploy/samza
 {% endhighlight %}
 
 ### Run a Samza Application
diff --git a/docs/learn/tutorials/versioned/hello-samza-high-level-zk.md b/docs/learn/tutorials/versioned/hello-samza-high-level-zk.md
@@ -59,7 +59,7 @@ With the environment setup complete, let us move on to building the hello-samza
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-0.13.0-SNAPSHOT-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-0.13.1-SNAPSHOT-dist.tar.gz -C deploy/samza
 {% endhighlight %}
 
 We are now all set to deploy the application locally.
diff --git a/docs/learn/tutorials/versioned/remote-debugging-samza.md b/docs/learn/tutorials/versioned/remote-debugging-samza.md
@@ -83,7 +83,7 @@ Once the grid starts, you can start the wikipedia-feed Samza job.
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-0.12.0-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-0.13.1-dist.tar.gz -C deploy/samza
 deploy/samza/bin/run-job.sh --config-factory=org.apache.samza.config.factories.PropertiesConfigFactory --config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties
 {% endhighlight %}
 
diff --git a/docs/learn/tutorials/versioned/run-in-multi-node-yarn.md b/docs/learn/tutorials/versioned/run-in-multi-node-yarn.md
@@ -145,15 +145,15 @@ vi src/main/config/wikipedia-feed.properties
 Change the yarn.package.path property to be:
 
 {% highlight jproperties %}
-yarn.package.path=http://yourHostname:8000/target/hello-samza-0.12.0-dist.tar.gz
+yarn.package.path=http://yourHostname:8000/target/hello-samza-0.13.1-dist.tar.gz
 {% endhighlight %}
 
 3\. Compile hello-samza.
 
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-0.12.0-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-0.13.1-dist.tar.gz -C deploy/samza
 {% endhighlight %}
 
 4\. Deploy Samza job package to Http server..
diff --git a/docs/learn/tutorials/versioned/samza-rest-getting-started.md b/docs/learn/tutorials/versioned/samza-rest-getting-started.md
@@ -48,7 +48,7 @@ Run the following commands:
 {% highlight bash %}
 cd samza-rest/build/distributions/
 mkdir -p deploy/samza-rest
-tar -xvf ./samza-rest-0.13.0-SNAPSHOT.tgz -C deploy/samza-rest
+tar -xvf ./samza-rest-0.13.1-SNAPSHOT.tgz -C deploy/samza-rest
 {% endhighlight %}
 
 #### Configure the Installations Path
diff --git a/docs/startup/download/index.md b/docs/startup/download/index.md
@@ -29,6 +29,7 @@ Starting from 2016, Samza will begin requiring JDK8 or higher. Please see [this
 
 ### Source Releases
 
+ * [samza-sources-0.13.0.tgz](http://www.apache.org/dyn/closer.lua/samza/0.13.0)
  * [samza-sources-0.12.0.tgz](http://www.apache.org/dyn/closer.lua/samza/0.12.0)
  * [samza-sources-0.11.0.tgz](http://www.apache.org/dyn/closer.lua/samza/0.11.0)
  * [samza-sources-0.10.1.tgz](http://www.apache.org/dyn/closer.lua/samza/0.10.1)
@@ -50,50 +51,50 @@ A Maven-based Samza project can pull in all required dependencies Samza dependen
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-api</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-core_2.11</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-shell</artifactId>
   <classifier>dist</classifier>
   <type>tgz</type>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-yarn_2.11</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-kv_2.11</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-kv-rocksdb_2.11</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-kv-inmemory_2.11</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.samza</groupId>
   <artifactId>samza-kafka_2.11</artifactId>
-  <version>0.12.0</version>
+  <version>0.13.0</version>
   <scope>runtime</scope>
 </dependency>
 {% endhighlight %}
diff --git a/docs/startup/hello-samza/versioned/index.md b/docs/startup/hello-samza/versioned/index.md
@@ -61,7 +61,7 @@ Then, you can continue w/ the following command in hello-samza project:
 {% highlight bash %}
 mvn clean package
 mkdir -p deploy/samza
-tar -xvf ./target/hello-samza-0.13.0-SNAPSHOT-dist.tar.gz -C deploy/samza
+tar -xvf ./target/hello-samza-0.13.1-SNAPSHOT-dist.tar.gz -C deploy/samza
 {% endhighlight %}
 
 ### Run a Samza Job
diff --git a/docs/startup/preview/index.md b/docs/startup/preview/index.md
@@ -60,7 +60,7 @@ For a deeper dive into the high level API, see [high level API section](#high-le
 
 #### II. ApplicationRunner
 
-Samza uses an [ApplicationRunner]((/learn/documentation/{{site.version}}/api/javadocs/org/apache/samza/runtime/ApplicationRunner.html)) to run a stream application. The ApplicationRunner generates the configs (such as input/output streams), creates intermediate streams, and starts the execution. There are two types of ApplicationRunner:
+Samza uses an [ApplicationRunner](/learn/documentation/{{site.version}}/api/javadocs/org/apache/samza/runtime/ApplicationRunner.html) to run a stream application. The ApplicationRunner generates the configs (such as input/output streams), creates intermediate streams, and starts the execution. There are two types of ApplicationRunner:
 
 **RemoteApplicationRunner** - submits the application to a remote cluster. This runner is invoked via the _run-app.sh_ script. To use RemoteApplicationRunner, set the following configurations
 
@@ -116,7 +116,7 @@ For more details on running Samza in embedded mode, take a look at the [flexible
 
 #### IV. Processor
 
-The lowest execution unit of a Samza application is the processor. It reads the configs generated from the [ApplicationRunner](/learn/documentation/{{site.version}}/api/javadocs/org/apache/samza/runtime/ApplicationRunner.html) and processes the input stream partitions assigned by the JobCoordinator. It can access local state using a [KeyValueStore]((/learn/documentation/{{site.version}}/api/javadocs/org/apache/samza/storage/KeyValueStore.html)) implementation (e.g. RocksDB or in-memory) and remote state (e.g. REST service) using multithreading.
+The lowest execution unit of a Samza application is the processor. It reads the configs generated from the [ApplicationRunner](/learn/documentation/{{site.version}}/api/javadocs/org/apache/samza/runtime/ApplicationRunner.html) and processes the input stream partitions assigned by the JobCoordinator. It can access local state using a [KeyValueStore](/learn/documentation/{{site.version}}/api/javadocs/org/apache/samza/storage/KeyValueStore.html) implementation (e.g. RocksDB or in-memory) and remote state (e.g. REST service) using multithreading.
 
 ---
 
diff --git a/gradle.properties b/gradle.properties
@@ -15,7 +15,7 @@
 # specific language governing permissions and limitations
 # under the License.
 group=org.apache.samza
-version=0.13.0-SNAPSHOT
+version=0.13.1-SNAPSHOT
 scalaVersion=2.11
 
 gradleVersion=2.8
