Major refactoring of release posts

* Combined all posts about each release into one
* The 'release-notes' category no longer exists
* Removed all 'blog' posts about releases.
* The blog archive nows shows all releases and was renamed news.
* Improved download instructions on release page and include source
  release
* Made all posts use UTC
* Made the /download/ page redirect to latest Fluo release post


Project: http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/repo
Commit: 
http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/commit/05f7bf0d
Tree: 
http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/tree/05f7bf0d
Diff: 
http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/diff/05f7bf0d

Branch: refs/heads/gh-pages
Commit: 05f7bf0db8667af0cd1113bd0de6d5df59185a37
Parents: 0495f99
Author: Mike Walch <mwa...@apache.org>
Authored: Thu Oct 13 17:03:49 2016 -0400
Committer: Mike Walch <mwa...@apache.org>
Committed: Fri Oct 14 14:44:36 2016 -0400

----------------------------------------------------------------------
 README.md                                       |   4 +-
 _config.yml                                     |  13 +-
 _layouts/default.html                           |   2 +-
 _layouts/post.html                              |   2 +-
 _layouts/release-notes.html                     |  21 --
 _layouts/release.html                           |   2 +-
 ...2014-10-02-fluo-1.0.0-alpha-1-is-released.md |  24 ---
 _posts/blog/2014-12-30-stress-test-long-run.md  |   4 +-
 .../2015-05-22-fluo-talk-at-accumulo-summit.md  |   4 +-
 .../2015-06-09-fluo-1.0.0-beta-1-is-released.md |  29 ---
 ...2015-12-22-beta-2-pre-release-stress-test.md |   6 +-
 _posts/blog/2016-01-11-webindex-long-run.md     |   4 +-
 .../2016-01-12-fluo-1.0.0-beta-2-is-released.md |  33 ---
 _posts/blog/2016-05-17-webindex-long-run-2.md   |  10 +-
 _posts/blog/2016-06-02-fluo-moving-to-apache.md |   6 +-
 .../2016-09-27-1.0.0-incubating-is-released.md  |  11 -
 .../2014-10-02-fluo-1.0.0-alpha-1.md            | 129 ------------
 .../2015-06-09-fluo-1.0.0-beta-1.md             | 177 ----------------
 .../2016-01-12-fluo-1.0.0-beta-2.md             | 157 --------------
 .../2016-09-27-fluo-1.0.0-incubating.md         | 117 -----------
 _posts/release/2014-10-02-fluo-1.0.0-alpha-1.md | 148 +++++++++++++-
 _posts/release/2015-06-09-fluo-1.0.0-beta-1.md  | 204 +++++++++++++++++--
 _posts/release/2016-01-12-fluo-1.0.0-beta-2.md  | 193 ++++++++++++++++--
 .../2016-01-13-fluo-recipes-1.0.0-beta-1.md     |   4 +-
 .../2016-03-29-fluo-recipes-1.0.0-beta-2.md     |   4 +-
 .../release/2016-09-27-fluo-1.0.0-incubating.md | 136 +++++++++++--
 docs/fluo/1.0.0-beta-1/applications.md          |   2 +-
 docs/fluo/1.0.0-beta-1/index.md                 |   4 +-
 docs/fluo/1.0.0-beta-2/applications.md          |   2 +-
 docs/fluo/1.0.0-beta-2/index.md                 |   4 +-
 index.html                                      |   4 +-
 pages/blog-archive.html                         |  15 --
 pages/download.md                               |   6 +-
 pages/getinvolved.md                            |   2 +-
 pages/news.html                                 |  16 ++
 pages/pre-asf-release.md                        |   4 +-
 pages/release-notes.md                          |  21 --
 pages/release.md                                |   2 +-
 resources/release-notes/1.0.0-beta-1/queued.png | Bin 23034 -> 0 bytes
 resources/release-notes/1.0.0-beta-1/rate.png   | Bin 25764 -> 0 bytes
 resources/release/1.0.0-beta-1/queued.png       | Bin 0 -> 23034 bytes
 resources/release/1.0.0-beta-1/rate.png         | Bin 0 -> 25764 bytes
 42 files changed, 683 insertions(+), 843 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index f6ede57..f1d2897 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,7 @@ Below are the steps required to update the Fluo project 
website for a new releas
 
 3. Confirm that javadocs are hosted externally and modify `apidocs/index.md` 
to point to link to them.
 
-4. Create release-notes, release, and blog post announcing the release in 
`_posts/`
+4. Create a post in `_posts/release` with release notes and resources to 
announce release.
 
 ## Apache Fluo Recipes releases
 
@@ -62,7 +62,7 @@ Steps to update website for new Fluo Recipes release:
 
 3. Confirm that javadocs are hosted externally and modify `apidocs/index.md` 
to point to link to them.
 
-4. Create release-notes, release, and blog post announcing the release in 
`_posts/`
+4. Create a post in `_posts/release` with release notes and resources to 
announce release.
 
 [Jekyll]: http://jekyllrb.com/
 [Bundler]: http://bundler.io/

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_config.yml
----------------------------------------------------------------------
diff --git a/_config.yml b/_config.yml
index 7540b0e..92a97f2 100644
--- a/_config.yml
+++ b/_config.yml
@@ -1,7 +1,8 @@
 # Site settings
-title: Fluo
+title: Apache Fluo
 baseurl: "" # the subpath of site
-url: "http://fluo.io"; # the base hostname & protocol for your site
+url: "https://fluo.apache.org/"; # the base hostname & protocol for your site
+timezone: Etc/UTC
 
 permalink: pretty
 
@@ -19,14 +20,6 @@ defaults:
     values:
       layout: "post"
       category: "blog"
-  - 
-    scope:
-      path: "_posts/release-notes"
-      type: "posts"
-    values:
-      layout: "release-notes"
-      category: "release-notes"
-      permalink: "/:categories/:title/"
   -
     scope:
       path: "_posts/release"

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_layouts/default.html
----------------------------------------------------------------------
diff --git a/_layouts/default.html b/_layouts/default.html
index 31a75e5..3f6c618 100644
--- a/_layouts/default.html
+++ b/_layouts/default.html
@@ -39,7 +39,7 @@
               <a class="dropdown-toggle" data-toggle="dropdown" 
href="#">Community<span class="caret"></span></a>
               <ul class="dropdown-menu">
                 <li><a href="{{ site.baseurl }}/getinvolved/">Get 
Involved</a></li>
-                <li><a href="{{ site.baseurl }}/blog/">Blog</a></li>
+                <li><a href="{{ site.baseurl }}/news/">News Archive</a></li>
                 <li><a href="{{ site.baseurl }}/people/">People</a></li>
                 <li><a href="{{ site.baseurl }}/related-projects/">Related 
Projects</a></li>
                 <li><a href="{{ site.baseurl }}/poweredby/">Powered By</a></li>

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_layouts/post.html
----------------------------------------------------------------------
diff --git a/_layouts/post.html b/_layouts/post.html
index 5fd539c..a6a3832 100644
--- a/_layouts/post.html
+++ b/_layouts/post.html
@@ -10,5 +10,5 @@ layout: default
 </div>
 
 <div>
-  <p class="text-muted">View more posts in the <a href="{{ site.baseurl 
}}/blog/">Blog archive</a></p>
+  <p class="text-muted">View all posts in the <a href="{{ site.baseurl 
}}/news/">news archive</a></p>
 </div>

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_layouts/release-notes.html
----------------------------------------------------------------------
diff --git a/_layouts/release-notes.html b/_layouts/release-notes.html
deleted file mode 100644
index 035d5e8..0000000
--- a/_layouts/release-notes.html
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: default
----
-<div class="post-header">
-  <h2>{{ page.title }}</h2>
-  <p class="text-muted">{{ page.date | date_to_string }}</p>
-</div>
-
-{% if page.historical %}
-  <div class="alert alert-danger" role="alert">These release notes are for a 
release of Fluo that made before Apache incubation.</div>
-{% endif %}
-
-<div class="post-content">
-  {{ content }}
-</div>
-
-<hr>
-
-<div>
-  <p>All Fluo release notes can be viewed in the <a href="{{ site.baseurl 
}}/release-notes/">archive</a></p>
-</div>

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_layouts/release.html
----------------------------------------------------------------------
diff --git a/_layouts/release.html b/_layouts/release.html
index 979ea0b..0be3915 100644
--- a/_layouts/release.html
+++ b/_layouts/release.html
@@ -7,7 +7,7 @@ layout: default
 </div>
 
 {% if page.historical %}
-  <div class="alert alert-danger" role="alert">This release was made before 
Apache incubation.</div>
+  <div class="alert alert-danger" role="alert">This release was made before 
Apache incubation and is not endorsed by the ASF.</div>
 {% endif %}
 
 <div class="post-content">

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2014-10-02-fluo-1.0.0-alpha-1-is-released.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-10-02-fluo-1.0.0-alpha-1-is-released.md 
b/_posts/blog/2014-10-02-fluo-1.0.0-alpha-1-is-released.md
deleted file mode 100644
index 5b84539..0000000
--- a/_posts/blog/2014-10-02-fluo-1.0.0-alpha-1-is-released.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title:  "Fluo 1.0.0-alpha-1 is released!"
-date:   2014-10-02 15:30:00
-redirect_from: /fluo-1.0.0-alpha-1-is-released/
----
-The Fluo project is happy to announce the [1.0.0-alpha-1][1] release of 
[Fluo][2].
-
-This is the first release of Fluo and is not ready for production use. We 
invite developers to try it out, play with the [quickstart][3] & 
[phrasecount][4] examples, and contribute back in the form of bug reports, new 
feature requests, and pull requests.
-
-Fluo is an implementation of Google's [percolator paper][10], which adds 
large-scale incremental processing of data using distributed transactions and 
notifications. It runs on [YARN][5] using [Twill][9] and stores its data in 
[Accumulo][6]. 
-
-[Release notes][7] and [javadocs][11] are available.  The [fluo jars][8] have 
been deployed to Maven Central
-
-[1]: /release/fluo-1.0.0-alpha-1/
-[2]: https://github.com/fluo-io/fluo
-[3]: https://github.com/fluo-io/fluo-quickstart
-[4]: https://github.com/fluo-io/phrasecount
-[5]: 
http://hadoop.apache.org/docs/r2.5.1/hadoop-yarn/hadoop-yarn-site/YARN.html
-[6]: https://accumulo.apache.org/
-[7]: /release-notes/fluo-1.0.0-alpha-1/
-[8]: http://search.maven.org/#search%7Cga%7C1%7Cfluo
-[9]: http://twill.incubator.apache.org/
-[10]: http://research.google.com/pubs/pub36726.html
-[11]: /apidocs/fluo/1.0.0-alpha-1/

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2014-12-30-stress-test-long-run.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-12-30-stress-test-long-run.md 
b/_posts/blog/2014-12-30-stress-test-long-run.md
index 31bacfc..fe0a5d2 100644
--- a/_posts/blog/2014-12-30-stress-test-long-run.md
+++ b/_posts/blog/2014-12-30-stress-test-long-run.md
@@ -1,6 +1,6 @@
 ---
-title:  "First long stress test run on Fluo"
-date:   2014-12-30 17:00:00
+title: "First long stress test run on Fluo"
+date: 2014-12-30 17:00:00 +0000
 redirect_from: /stress-test-long-run/
 ---
 

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2015-05-22-fluo-talk-at-accumulo-summit.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2015-05-22-fluo-talk-at-accumulo-summit.md 
b/_posts/blog/2015-05-22-fluo-talk-at-accumulo-summit.md
index c7c8c47..6395a79 100644
--- a/_posts/blog/2015-05-22-fluo-talk-at-accumulo-summit.md
+++ b/_posts/blog/2015-05-22-fluo-talk-at-accumulo-summit.md
@@ -1,6 +1,6 @@
 ---
-title:  "Fluo talk at Accumulo Summit"
-date:   2015-05-22 14:27:00
+title: "Fluo talk at Accumulo Summit"
+date: 2015-05-22 14:27:00 +0000
 redirect_from: /fluo-talk-at-accumulo-summit/
 ---
 

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2015-06-09-fluo-1.0.0-beta-1-is-released.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2015-06-09-fluo-1.0.0-beta-1-is-released.md 
b/_posts/blog/2015-06-09-fluo-1.0.0-beta-1-is-released.md
deleted file mode 100644
index 488e909..0000000
--- a/_posts/blog/2015-06-09-fluo-1.0.0-beta-1-is-released.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: "Fluo 1.0.0-beta-1 is released!"
-date: 2015-06-09 18:30:00
-redirect_from: /fluo-1.0.0-beta-1-is-released/
----
-The Fluo project is happy to announce the [1.0.0-beta-1] release of [Fluo].  
This is the second 
-release of Fluo.
-
-We invite developers read the Fluo [documentation], play with the [quickstart] 
& [phrasecount] 
-examples, and contribute back in the form of bug reports, new feature 
requests, and pull requests.
-
-Fluo is an implementation of Google's [percolator paper][paper], which adds 
large-scale incremental 
-processing of data using distributed transactions and notifications. It runs 
on [YARN] and stores its 
-data in [Accumulo]. 
-
-[Release notes][notes] and [javadocs] are available.  The Fluo [jars] have 
been deployed to 
-Maven Central.
-
-[1.0.0-beta-1]: /release/fluo-1.0.0-beta-1/
-[Fluo]: https://github.com/fluo-io/fluo
-[documentation]: /docs/fluo/1.0.0-beta-1/
-[quickstart]: https://github.com/fluo-io/fluo-quickstart
-[phrasecount]: https://github.com/fluo-io/phrasecount
-[YARN]: 
http://hadoop.apache.org/docs/r2.5.1/hadoop-yarn/hadoop-yarn-site/YARN.html
-[Accumulo]: https://accumulo.apache.org/
-[notes]: /release-notes/fluo-1.0.0-beta-1/
-[jars]: http://search.maven.org/#search%7Cga%7C1%7Cfluo
-[paper]: http://research.google.com/pubs/pub36726.html
-[javadocs]: /apidocs/fluo/1.0.0-beta-1/

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md 
b/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
index 2936d59..499e574 100644
--- a/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
+++ b/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
@@ -1,6 +1,6 @@
 ---
-title:  "Beta 2 pre-release stress test"
-date:   2015-12-22 15:30:00
+title: "Beta 2 pre-release stress test"
+date: 2015-12-22 15:30:00 +0000
 redirect_from: /beta-2-pre-release-stress-test/
 ---
 
@@ -60,7 +60,7 @@ Further testing
 A long run of webindex will also be run on EC2 before releasing beta-2.
 
 [1]: /blog/2014/12/30/stress-test-long-run/
-[2]: /release-notes/fluo-1.0.0-beta-1/
+[2]: /release/fluo-1.0.0-beta-1/
 [3]: https://github.com/fluo-io/fluo-stress
 [4]: 
https://github.com/fluo-io/fluo/commit/c4789b3100092683b37c57c48ddd87993e84972c
 [5]: 
https://github.com/fluo-io/fluo-stress/commit/32edaf91138bb13b442632262c23e7f13f8fb17c

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2016-01-11-webindex-long-run.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2016-01-11-webindex-long-run.md 
b/_posts/blog/2016-01-11-webindex-long-run.md
index b5894bc..864e734 100644
--- a/_posts/blog/2016-01-11-webindex-long-run.md
+++ b/_posts/blog/2016-01-11-webindex-long-run.md
@@ -1,6 +1,6 @@
 ---
-title:  "Running Webindex for 3 days on EC2"
-date:   2016-01-11 03:30:00
+title: "Running Webindex for 3 days on EC2"
+date: 2016-01-11 15:30:00 +0000
 redirect_from: /webindex-long-run/
 ---
 

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2016-01-12-fluo-1.0.0-beta-2-is-released.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2016-01-12-fluo-1.0.0-beta-2-is-released.md 
b/_posts/blog/2016-01-12-fluo-1.0.0-beta-2-is-released.md
deleted file mode 100644
index 9350ae3..0000000
--- a/_posts/blog/2016-01-12-fluo-1.0.0-beta-2-is-released.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: "Fluo 1.0.0-beta-2 is released!"
-date: 2016-01-12 15:30:00
-redirect_from: /fluo-1.0.0-beta-2-is-released/
----
-
-The Fluo project is happy to announce a [1.0.0-beta-2] release which is the
-third release of Fluo and likely the final release before 1.0.0.  Many
-improvements in this release were driven by the creation of two new Fluo 
related
-projects:
-
-* [Fluo recipes][fluo-recipes] is a collection of common development patterns
-designed to make Fluo application development easier.  Creating Fluo recipes
-required new Fluo functionality and updates to the Fluo API.  The first release
-of Fluo recipes has been made and is available in [Maven Central][central].
-
-* [WebIndex][webindex] is an example Fluo application that indexes links to web
-pages in multiple ways.  Webindex enabled the testing of Fluo on real data at
-scale.  It also inspired improvements to Fluo to allow it to work better with
-Apache Spark.
-
-Fluo is now at a point where its two cluster test suites, [Webindex][webindex]
-and [Stress][fluo-stress], are running well for long periods on Amazon EC2.  We
-invite early adopters to try out the beta-2 release and help flush out problems
-before 1.0.0.
-
-[1.0.0-beta-2]: /release/fluo-1.0.0-beta-2/
-[Fluo]: https://github.com/fluo-io/fluo
-[notes]: /release-notes/fluo-1.0.0-beta-2/
-[webindex]: https://github.com/fluo-io/webindex
-[fluo-recipes]: https://github.com/fluo-io/fluo-recipes
-[fluo-stress]: https://github.com/fluo-io/fluo-stress
-[central]: http://search.maven.org/#search|ga|1|fluo-recipes

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2016-05-17-webindex-long-run-2.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2016-05-17-webindex-long-run-2.md 
b/_posts/blog/2016-05-17-webindex-long-run-2.md
index 0141bd4..fdfece7 100644
--- a/_posts/blog/2016-05-17-webindex-long-run-2.md
+++ b/_posts/blog/2016-05-17-webindex-long-run-2.md
@@ -1,6 +1,6 @@
 ---
-title:  "Running Webindex for 3 days on EC2 Again"
-date:   2016-05-17 05:44:00
+title: "Running Webindex for 3 days on EC2 Again"
+date: 2016-05-17 08:44:00 +0000
 ---
 
 Another long run of [Webindex] was done to test changes made since beta-2
@@ -272,9 +272,9 @@ Software used
 [ACCUMULO-1124]: https://issues.apache.org/jira/browse/ACCUMULO-1124
 [ACCUMULO-4314]: https://issues.apache.org/jira/browse/ACCUMULO-4314
 [ACCUMULO-4066]: https://issues.apache.org/jira/browse/ACCUMULO-4066
-[lr1]: /blog/2016/01/10/webindex-long-run/
-[lr1-overview]: /blog/2016/01/10/webindex-long-run/#webindex-overview
-[lr1-plots]: /blog/2016/01/10/webindex-long-run/#grafana-plots
+[lr1]: /blog/2016/01/11/webindex-long-run/
+[lr1-overview]: /blog/2016/01/11/webindex-long-run/#webindex-overview
+[lr1-plots]: /blog/2016/01/11/webindex-long-run/#grafana-plots
 [fluo-623]: https://github.com/fluo-io/fluo/issues/623
 [fluo-648]: https://github.com/fluo-io/fluo/issues/648
 [fluo-593]: https://github.com/fluo-io/fluo/issues/593

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2016-06-02-fluo-moving-to-apache.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2016-06-02-fluo-moving-to-apache.md 
b/_posts/blog/2016-06-02-fluo-moving-to-apache.md
index 7b4148d..e6c57e5 100644
--- a/_posts/blog/2016-06-02-fluo-moving-to-apache.md
+++ b/_posts/blog/2016-06-02-fluo-moving-to-apache.md
@@ -1,11 +1,11 @@
 ---
-title:  "Fluo is moving to Apache"
-date:   2016-06-02 11:43:00
+title: "Fluo is moving to Apache"
+date: 2016-06-02 11:43:00 +0000
 ---
 
 Fluo was recently [proposed][1] as an Apache Podling.  The [vote][2] passed and
 now we are in the process of moving to Apache.  See [INFRA-11900][3] for more
-details.   
+details.
 
 Currently the only thing setup in Apache land is the mailing list.  If you
 would like to subscribe to the new list, send an email to

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/blog/2016-09-27-1.0.0-incubating-is-released.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2016-09-27-1.0.0-incubating-is-released.md 
b/_posts/blog/2016-09-27-1.0.0-incubating-is-released.md
deleted file mode 100644
index 2addbe6..0000000
--- a/_posts/blog/2016-09-27-1.0.0-incubating-is-released.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Fluo 1.0.0-incubating is released!"
-date: 2016-09-27 15:30:00
----
-
-Apache Fluo is happy to announce a [1.0.0-incubating][rel] release. This is 
the first
-release of Fluo as an Apache project and the fourth release for the project. 
Starting
-with this release, Fluo will follow [semver][semver] for all future API 
changes. 
-
-[semver]: http://semver.org/
-[rel]: /release/fluo-1.0.0-incubating/

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/release-notes/2014-10-02-fluo-1.0.0-alpha-1.md
----------------------------------------------------------------------
diff --git a/_posts/release-notes/2014-10-02-fluo-1.0.0-alpha-1.md 
b/_posts/release-notes/2014-10-02-fluo-1.0.0-alpha-1.md
deleted file mode 100644
index 02913da..0000000
--- a/_posts/release-notes/2014-10-02-fluo-1.0.0-alpha-1.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Fluo 1.0.0-alpha-1 Release Notes
-date: 2014-10-02 15:30:00
-version: fluo-1.0.0-alpha-1
-historical: true
-redirect_from: /1.0.0-alpha-1-release-notes/
----
-
-Fluo 1.0.0-alpha-1 is the first official release of Fluo. It contains 83 
initial tickets marked for this first milestone. The roadmap for this release 
included a working initial implementation, completing an initial pass at the 
client API (which will be finalized in 1.0.0), and writing a stress test 
application.  This release has not been tested much at scale.  More scale and 
peformance testing will be done for the beta release.
-
-## Significant features
-
-This alpha release contained a lot of initial features to help establish the 
basic implementation and client API. All of these features will be expected to 
become more robust over time.
-
-#### MiniFluo
-
-MiniAccumulo and MiniFluo make it easy to start a local Fluo instance for 
integration testing. MiniFluo also makes it easy for developers to experiment 
with Fluo locally without installing it on an Accumulo cluster.
-
-#### Garbage Collection
-
-Without garbage collection, the columnns in a Fluo table would grow without 
bound as updates are applied over time. Because of this, it's important to 
clean up old fully-processed (and no longer being read) transaction data. The 
initial implementation of garbage collection kept N versions of columns. 
[Fluo-8][8] added the ability to garbage collect all column versions that are 
no longer being read by transactions anywhere else in the cluster.
-
-#### MapReduce InputFormat
-
-The FluoInputFormat allows a specific snapshot to be read into a mapreduce 
job. It was established in [Fluo-7][7].
-
-#### FluoFileOutputFormat and FluoOutputFormat
-
-The FluoFileOuputFormat enables the bulk ingest of a Fluo table using 
mapreduce by creating the Accumulo r-files in HDFS. The FluoOutputFormat pushes 
keys directly into the Accumulo tablet servers through the client API. 
[Fluo-35][35] added this feature.
-
-#### Fluo Workers and Oracle running in Yarn
-
-Fluo can use Yarn to manage fault tolerance and guarantee multiple worker 
processes and some number of Oracle processes are kept running across the 
cluster. [Apache Twill][twill] was used for the Yarn integration. [Fluo-11][11] 
added an application that will deploy Fluo to a Yarn cluster.
-
-#### Fluo API
-
-Fluo provides a fluent-builder API for creating transactions to read and 
mutate data of various different data types in the Fluo table. This API was 
finalized in [Fluo-23][23] and [Fluo-98][98] when it was moved into its own 
module.  It includes a type layer (finished in [Fluo-153][153]) that makes it 
easier to work with different types, default values, null return types, and 
row/column maps.
-
-#### Stress test
-
-A [stress test][stress] was created that uses a tree to force collisions on 
transactions trying to mutate multiple columns at the same time. This was 
established in [Fluo-24][24].
-
-Other important improvements and features:
-
-* [Fluo-1][1]     - Create scripts for starting/stopping services
-* [Fluo-3][3]     - use Curator for leader election and leader discovery
-* [Fluo-13][13]   - Register clients that perform transactions in Zookeeper
-* [Fluo-15][15]   - Leader election for the Oracle Server
-* [Fluo-16][16]   - Allow observer notification to be configured in 
AbstractObserver class
-* [Fluo-89][89]   - OracleApp should allow configurable number of instances
-* [Fluo-98][98]   - Create a Range class for Fluo
-* [Fluo-123][123] - Hide implementation of Bytes in the API
-* [Fluo-130][130] - Expose MiniFluo in public API
-* [Fluo-131][131] - Make LoaderExector implement closeable
-* [Fluo-147][147] - Create fluo-accumulo module for Accumulo iterators and 
formatter
-* [Fluo-175][175] - Add newTransaction() method to FluoClient
-* [Fluo-186][186] - Add Exceptions to API
-
-## Testing
-
-All unit and integration tests passed.  Two [stress tests][stress] were run 
successfully on a 20-node cluster with one test generating 2000 integers and 
another generating 5000 integers.  The 5000 integer test took about 10 minutes 
to run after the MapReduce load of integers was complete.
-
-## Current Status of Percolator Implementation
-
-The following tables identify the features necessary for a full implementation 
of Percolator and the current state of Fluo with regards to the implementation. 
For alpha, a test to excercise some of these features at scale was created, 
however, it was not run at scale for long periods. One of the goals for beta is 
to have at least a 24hr run of the scale test, on at least 20 nodes, succeed.
-
-### Necessary features:
-
-| Percolator Feature         |  Details | Testing |
-|----------|-------------------|------|
-| ACID-compliant cross-row transactions | Provides distributed transactions 
with ACID guarantees that work across Accumulo rows. Rows are distributed 
across tablet servers. | IT,CST,[#240][240]<sup>1</sup> |
-| Observers |    Perform transactions by sending read/write RPCs to Accumulo 
tablet servers, which in turn send read/write RPCs to HDFS.   |  IT,CST |
-| Worker Process | Scans Accumulo for changed columns and invokes necessary 
observers as function calls on the worker. | IT,CST |
-| Timestamp Oracle | Provides strictly increasing timestamps; a property 
required for correct operation of the snapshot isolation protocol. |  IT,CST |
-| Oracle Failover | When an active Oracle process dies, timestamps should be 
served from a different Oracle. They should never go backwards. | 
IT,[#37][37],[#241][241]<sup>1</sup> |
-| Lightweight Lock Service | Makes searches for dirty notifications more 
efficient. Zookeeper is used in this case. Should be low-latency, replicated, 
balanced, and persist to a backing store. |    IT,CST |
-| Multithreaded Transasctions | Allows highly parallel execution of 
transactions and synchronization only during get() and commit() upon which 
transactions actually collide. |    IT,CST |
-| Snapshot Isolation | Non-serializable isolation mostly implemented through 
MVCC provided through Accumulo's timestamp portion of the key. | 
IT,CST,[#240][240]<sup>1</sup> |
-| Roll-back / Roll-forward semantics | Failures during the first phase of 
commit cause transactions to be rolled back while failures during the second 
phase can cause them to be rolled forward. | IT,[#240][240]<sup>1</sup> |
-
-<sup>1</sup> This feature has been at least partially tested.
-
-### Performance enhancements:
-
-| Enhancement         |  Details | Testing |
-|----------|-------------------|------|
-| Locality Group for NOTIFY column |  Add an extra index in the underlying 
r-files for the notify column where it can be scanned faster by workers.  | 
IT,CST  | 
-| Worker scan conflict resolution | Workers register random tablets they 
choose to scan. When two workers generate the same tablet, one of them 
re-generates a new random tablet. | [#5][5] |
-| Worker advertisement | Workers advertise through the lock service so that 
the system can know if they failed and any transactions upon which they are 
working can be rolled back or rolled forward | IT | 
-| Oracle batching | Timestamps get allocated in batch to workers. Each worker 
should share one connection to Oracle to limit RPCs across threads | IT,CST |
-| Weak Notifications | Allows notification of a cell without the possibility 
of transactional conflict through a special type of column that can be notified 
but not written to | IT |
-| Conditional Mutations | Allows READ-MODIFY-WRITE of a mutation in a single 
RPC.  | IT,CST |
-| Conditional Mutation batching | Delay sending of conditional mutations 
destined for same tablet server so they can be batched. Lowers number of RPCs, 
adds latency but provides better parallelism. | IT,CST |
-| Read batching | Delaying of read operations on tablet server for batching | 
[#138][138] |
-| Prefetching & read-ahead caching | Prediction made each time a column is 
read, which other columns will be read in the same transaction based on 
previous behavior. | [#12][12] |
-
-* IT = Integration tests, CST = Cluster stress tests
-* Testing columns providing a ticket number have not yet been implemented.
-
-[ACCUMULO-1000]: https://issues.apache.org/jira/browse/ACCUMULO-1000
-[percolator]: http://research.google.com/pubs/pub36726.html
-[twill]: http://twill.incubator.apache.org/
-[stress]: 
https://github.com/fluo-io/fluo/blob/1.0.0-alpha-1/modules/stress/README.md
-[241]: https://github.com/fluo-io/fluo/issues/241
-[240]: https://github.com/fluo-io/fluo/issues/240
-[186]: https://github.com/fluo-io/fluo/issues/186
-[175]: https://github.com/fluo-io/fluo/issues/175
-[153]: https://github.com/fluo-io/fluo/issues/153
-[147]: https://github.com/fluo-io/fluo/issues/147
-[138]: https://github.com/fluo-io/fluo/issues/138
-[131]: https://github.com/fluo-io/fluo/issues/131
-[130]: https://github.com/fluo-io/fluo/issues/130
-[123]: https://github.com/fluo-io/fluo/issues/123
-[98]: https://github.com/fluo-io/fluo/issues/98
-[89]: https://github.com/fluo-io/fluo/issues/89
-[37]: https://github.com/fluo-io/fluo/issues/37
-[35]: https://github.com/fluo-io/fluo/issues/35
-[24]: https://github.com/fluo-io/fluo/issues/24
-[23]: https://github.com/fluo-io/fluo/issues/23
-[16]: https://github.com/fluo-io/fluo/issues/16
-[15]: https://github.com/fluo-io/fluo/issues/15
-[13]: https://github.com/fluo-io/fluo/issues/13
-[12]: https://github.com/fluo-io/fluo/issues/12
-[11]: https://github.com/fluo-io/fluo/issues/11
-[8]: https://github.com/fluo-io/fluo/issues/8
-[7]: https://github.com/fluo-io/fluo/issues/7
-[5]: https://github.com/fluo-io/fluo/issues/5
-[3]: https://github.com/fluo-io/fluo/issues/3
-[1]: https://github.com/fluo-io/fluo/issues/1

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/release-notes/2015-06-09-fluo-1.0.0-beta-1.md
----------------------------------------------------------------------
diff --git a/_posts/release-notes/2015-06-09-fluo-1.0.0-beta-1.md 
b/_posts/release-notes/2015-06-09-fluo-1.0.0-beta-1.md
deleted file mode 100644
index 108e312..0000000
--- a/_posts/release-notes/2015-06-09-fluo-1.0.0-beta-1.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
-title: Fluo 1.0.0-beta-1 Release Notes
-date: 2015-06-09 18:30:00
-version: fluo-1.0.0-beta-1
-historical: true
-redirect_from: /1.0.0-beta-1-release-notes/
----
-
-Fluo 1.0.0-beta-1 is the second official release of Fluo.  The release closed 
[133 tickets][tickets].  This release is not recommended for production use.
-
-## Significant features
-
-This release contains many new features that makes it easier to run, develop, 
and monitor Fluo applications.
-
-#### Simplified Fluo administration on a local machine or EC2 cluster
-
-Developers can now run Fluo and its dependencies on their local machine 
([#92][92]) or an AWS EC2 cluster ([#356][356]) using a few simple commands.
-This was done by creating two administration tools called [Fluo-dev][fluo-dev] 
and [Fluo-deploy][fluo-deploy] whose scripts and configuration reside in repos
-separate from the Fluo code base.  These tools allow developers to collaborate 
and share configuration for running Fluo.
-
-#### Transaction metrics are viewable using common monitoring tools
-
-Fluo now publishes metrics ([#20][20]) about transactions, collisions, and 
timestamps using [Dropwizard metrics][dropwizard].  These metrics are by 
default published 
-using JMX and are viewable using JConsole or JVisualVM.  Fluo can also be 
configured to publish metrics to Graphite or Ganglia.  View the [metrics 
documentation][metrics]
-for more information.
-
-#### Improved processing of notifications in Fluo workers
-
-Fluo workers were refactored to separate the code used for finding and 
executing work.  Each worker uses a single thread for finding 
-work ([#19][19]).  A new method was introduced to partition work among workers 
using a hash+mod of notifications ([#282][282]).
-The commit message for [4100e23][4100e23] contains a good description of some 
of the benefits and drawback of the current
-hashing approach.
-
-#### Improved the deletion of observer notifications
-
-When a cell is deleted in Accumulo, a delete marker is inserted.  Delete 
markers stay around until
-all files in a tablet are compacted.  For Fluo this could cause a lot of 
notification delete markers
-to build up over time.  To avoid this buildup, the way Fluo deletes 
notifications was changed in
-([#457][457]).  Accumulo delete markers are no longer used, Fluo now uses a 
custom delete marker for
-notifications.  The custom deleter marker allows Fluo to do analysis when 
Accumulo flushes memory to
-disk and avoid writing many delete markers to persistent storage.
-
-#### Easier management of Fluo from the command line
-
-Fluo now provides different scripts (**fluo**, **mini-fluo**, & 
**local-fluo**) for managing Fluo using a YARN cluster, MiniFluo, or local 
processes.  Several commands
-were created for these scripts.  A **scan** command allows users to print a 
snapshot of a Fluo table ([#319][319]).  A **info** command shows locations of 
containers
-when running Fluo in YARN ([#297][297]).  A **classpath** command gives users 
a list of jars needed to execute Fluo client code ([#436][436]).  A **wait** 
command will
-sleep until all notifications are processed ([#434][434]).
-
-#### Support for running multiple Fluo applications on a single cluster
-
-Users can now run multiple Fluo applications using a single cluster 
([#454][454]).  This enables different Fluo users to share the same cluster.  
Fluo applications
-can be started and stopped independently.  Each application has its own 
configuration.
-
-#### Fluo build improvements
-
-On each build, all Java code is automatically formatted based on Google Java 
Style ([#479][479]).  Also, checkstyle and findbugs will fail the build if 
certain
-standards are not reached ([#185][185]).  The POM is also sorted ([#493][493]).
-
-#### Organized Fluo code base
-
-The Fluo stress test was moved to its own [repo][fluo-stress] and is no longer 
a sub-module ([#385][385]).  MiniFluo was moved from fluo-core to the fluo-mini 
-module/jar ([#439][439]).  This reduced the number of dependencies in 
fluo-core.  However, developers will now need to include the fluo-mini jar in 
their Maven
-POM if they start MiniFluo.
-
-#### Fluo testing improvements
-
-Integration tests can now be run from Eclipse ([#322][322]).  Several new 
[unit tests][unit] were created.
-
-
-#### Other important improvements and bug fixes
-
-* [#470][470] - Replaced FluoFileOutputFormat with an Accumulo Key/Value 
generator
-* [#460][460] - Reduced Fluo API module dependencies
-* [#456][456] - Fixed bug with notifications being lost when processes died
-* [#446][446] - Simplified log configuration and configure rolling log files 
in YARN
-* [#442][442] - Reduced the number of curator clients in FluoAdmin
-* [#383][383] - Improved transaction logging to help users debug collisions. 
See [debugging documentation][debug].
-* [#365][365] - Analyze Fluo code to see what non-public Accumulo APIs are used
-* [#362][362] - Made API data objects immutable
-* [#349][349] - Support application level configuration in fluo.properties
-* [#342][342] - Add a configurable retry timeout to Fluo clients
-* [#294][294] - Fluo now uses chroot suffix in its Zookeeper connection.
-* [#293][293] - Add argument checking to FluoConfiguration
-* [#244][244] - Make re-initialization easier for user
-
-## Testing
-
-A successful long stress test run was conducted using Fluo built from commit
-[fb647dd][fb647dd].  The test ran very well and never fell behind like a
-[previous long run][old-stress-run] of stress did.  The test had the following
-properties.
- 
- * Initialized stress test using 1 billion random integers.
- * Ran 150 incremental loads of 100 thousand integers.  Slept 3 minutes 
between loads. 
- * Used 19 m3.xlarge nodes on EC2.  16 workers and 3 masters
- * Configuration for the test committed and tagged in git : [fluo-deploy 
tag][fd-tag-1] and [fluo-stress tag][fs-tag-1]
- * Opened two issues as a result of test [#499][499] and 
[fluo-stress#30][fs-30]
-
-Below is the trailing output from running the test.
-
-
-    *****Generating and loading incremental data set 148*****
-    *****Generating and loading incremental data set 149*****
-    *****Generating and loading incremental data set 150*****
-    *****Calculating # of unique integers using MapReduce*****
-                    UNIQUE=1014486419
-    *****Wait for Fluo to finish processing*****
-    05:33:40.158 [main] INFO  io.fluo.cluster.runner.AppRunner - The wait 
command will exit when all notifications are processed
-    05:33:40.417 [Thread-3] INFO  io.fluo.core.oracle.OracleClient - Connected 
to oracle at worker4:9913
-    05:33:41.308 [main] INFO  io.fluo.cluster.runner.AppRunner - All 
processing has finished!
-    *****Printing # of unique integers calculated by Fluo*****
-    Total at root : 1014486419
-    Nodes Scanned : 59605
-    *****Verifying Fluo & MapReduce results match*****
-    Success! Fluo & MapReduce both calculated 1014486419 unique integers
-
-The test ran for a little over 12 hours.  Below are two plots pulled from
-graphite showing the number of notifications queued and transaction rate over
-the entire test run.  Load transactions are not included in the rate.  The rate
-is transactions per second.  The accuracy of these plots is uncertain because
-no graphite configuration changes were made.  The plots do seem within the
-ballpark.
-
-![Notifications Queued](/resources/release-notes/1.0.0-beta-1/queued.png 
"Notifications Queued") ![Transaction 
rate](/resources/release-notes/1.0.0-beta-1/rate.png "Transaction Rate")
-
-[tickets]: 
https://github.com/fluo-io/fluo/issues?q=milestone%3A1.0.0-beta-1+is%3Aclosed
-[fd-tag-1]: https://github.com/keith-turner/fluo-deploy/tree/beta-long-test-1
-[fs-tag-1]: https://github.com/keith-turner/fluo-stress/tree/beta-long-test-1
-[fluo-dev]: https://github.com/fluo-io/fluo-dev
-[fluo-deploy]: https://github.com/fluo-io/fluo-deploy
-[fluo-stress]: https://github.com/fluo-io/fluo-stress
-[dropwizard]: https://dropwizard.github.io/metrics/3.1.0/
-[debug]: 
https://github.com/fluo-io/fluo/blob/1.0.0-beta-1/docs/applications.md#debugging-applications
-[metrics]: https://github.com/fluo-io/fluo/blob/1.0.0-beta-1/docs/metrics.md
-[old-stress-run]: /blog/2014/12/30/stress-test-long-run/
-[unit]: 
https://github.com/fluo-io/fluo/issues?utf8=%E2%9C%93&q=milestone%3A1.0.0-beta-1+is%3Aclosed+%22unit+test%22
-[4100e23]: 
https://github.com/fluo-io/fluo/commit/4100e236b8438350e30eda924a6360e2c722ae37
-[fb647dd]: 
https://github.com/fluo-io/fluo/commit/fb647dd6a470e8015654f8ed99b9196f5f49582a
-[499]: https://github.com/fluo-io/fluo/issues/499
-[493]: https://github.com/fluo-io/fluo/issues/493
-[479]: https://github.com/fluo-io/fluo/issues/479
-[470]: https://github.com/fluo-io/fluo/issues/470
-[460]: https://github.com/fluo-io/fluo/issues/460
-[457]: https://github.com/fluo-io/fluo/issues/457
-[456]: https://github.com/fluo-io/fluo/issues/456
-[454]: https://github.com/fluo-io/fluo/issues/454
-[446]: https://github.com/fluo-io/fluo/issues/446
-[442]: https://github.com/fluo-io/fluo/issues/442
-[439]: https://github.com/fluo-io/fluo/issues/439
-[436]: https://github.com/fluo-io/fluo/issues/436
-[434]: https://github.com/fluo-io/fluo/issues/434
-[385]: https://github.com/fluo-io/fluo/issues/385
-[383]: https://github.com/fluo-io/fluo/issues/383
-[365]: https://github.com/fluo-io/fluo/issues/365
-[362]: https://github.com/fluo-io/fluo/issues/362
-[356]: https://github.com/fluo-io/fluo/issues/356
-[342]: https://github.com/fluo-io/fluo/issues/342
-[349]: https://github.com/fluo-io/fluo/issues/349
-[322]: https://github.com/fluo-io/fluo/issues/322
-[319]: https://github.com/fluo-io/fluo/issues/319
-[297]: https://github.com/fluo-io/fluo/issues/297
-[293]: https://github.com/fluo-io/fluo/issues/293
-[294]: https://github.com/fluo-io/fluo/issues/294
-[282]: https://github.com/fluo-io/fluo/issues/282
-[244]: https://github.com/fluo-io/fluo/issues/244
-[241]: https://github.com/fluo-io/fluo/issues/241
-[240]: https://github.com/fluo-io/fluo/issues/240
-[185]: https://github.com/fluo-io/fluo/issues/185
-[138]: https://github.com/fluo-io/fluo/issues/138
-[92]: https://github.com/fluo-io/fluo/issues/92
-[37]: https://github.com/fluo-io/fluo/issues/37
-[20]: https://github.com/fluo-io/fluo/issues/20
-[19]: https://github.com/fluo-io/fluo/issues/19
-[12]: https://github.com/fluo-io/fluo/issues/12
-[5]: https://github.com/fluo-io/fluo/issues/5
-[fs-30]: https://github.com/fluo-io/fluo-stress/issues/30

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/release-notes/2016-01-12-fluo-1.0.0-beta-2.md
----------------------------------------------------------------------
diff --git a/_posts/release-notes/2016-01-12-fluo-1.0.0-beta-2.md 
b/_posts/release-notes/2016-01-12-fluo-1.0.0-beta-2.md
deleted file mode 100644
index d694b1e..0000000
--- a/_posts/release-notes/2016-01-12-fluo-1.0.0-beta-2.md
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: Fluo 1.0.0-beta-2 Release Notes
-date: 2016-01-12 15:30:00
-version: fluo-1.0.0-beta-2
-historical: true
-redirect_from: /1.0.0-beta-2-release-notes/
----
-
-Fluo 1.0.0-beta-2 is the third official release of Fluo.  This release closed
-[48 tickets][tickets].  There is no upgrade path from 1.0.0-beta-1 to
-1.0.0-beta-2.
-
-## Significant features
-
-This release contains many new features that makes it easier to run, develop, 
and monitor Fluo applications.
-
-#### Improved Fluo metrics that can be sent to InfluxDB and viewed in Grafana
-
-In [#569][569], [#570][570], & [#580][580], Fluo metrics and monitoring were 
refactored to fix several
-bugs and allow metrics to be sent to [InfluxDB][influxdb] and viewed in 
[Grafana][grafana].  Fluo metrics 
-are still instrumented using [Dropwizard metrics][dropwizard] but in 
[#574][574] metrics configuration was 
-moved from its own file and to now reside in `fluo.properties`.  While Fluo 
metrics can still be sent to 
-many different tools (i.e Graphite, Ganglia), Fluo now ships with 
configuration that can be used to configure 
-a Fluo dashboard in Grafana that queries InfluxDB.  To set up the sending of 
Fluo metrics to InfluxDB/Grafana,
-view this [documentation][grafana-docs] or consider using [Fluo-dev][fluo-dev] 
or [Zetten][zetten]
-to run Fluo as they can install InfluxDB+Grafana and setup metrics for you.
-
-#### Improved Fluo administration
-
-Several commands were added to the `fluo` script which is used to administer 
Fluo.  A `fluo exec` command
-([#581][581]) was created to provide an easy way to execute application code 
using Fluo classes and dependencies.
-A `fluo list` command ([#523][523]) was created to let users list all Fluo 
applications within a Fluo instance.
-The `fluo scan` command now has a `--raw` option ([#597][597]) that prints 
Fluo data as stored in Accumulo. This
-was accomplished by moving the Fluo formatter from Accumulo shell to the scan 
command.  The scan command can now
-format non-ascii characters as hex ([#568][568]).  The `fluo new` command was 
improved to prevent users from
-setting invalid Fluo application names ([#510][510]).  A bug was fixed in the 
`fluo start` command that was causing
-time outs when starting applications ([#562][562]).  Finally, the `fluo` 
command can now be run without the `apps/`
-directory configured for an application for most commands ([#524][524]). Only 
the `init` and `start` commands need
-this directory configured.  All other commands only require the default 
properties file to be configured at 
-`conf/fluo.properties`.
-
-#### Made Fluo work better with Spark
-
-Several changes were made to Fluo to allow it work better with Apache Spark.  
All Fluo data types now implement
-`Serializable` and can be use in Spark RDDs ([#539][539]).  Fluo data types 
also now implement `Comparable` which
-allows RDDs of Fluo data types to be sorted ([#544][544]).  Also, a no args 
constructor was created for the
-MutableBytes data type to enable Kryo serialization in Spark ([#549][549]).  
Finally, a new InputFormat called
-`FluoEntryInputFormat` was created that returns key/value entries and the 
existing `FluoInputFormat` that returns
-rows was renamed `FluoRowInputFormat` ([#538][538],[#540][540]).
-
-#### Performance improvements
-
-A good bit of time was spent analyzing Fluo while it was running to determine
-where time is spent when executing transactions.   Based on this analysis, it
-was found that a good bit of time was spent committing transactions.  Changes
-were made in Fluo and Accumulo in order to decrease commit time.  For Fluo, the
-following changes were made :
-
-* [#591][591] - Shared batch writer increases transaction history
-* [#590][590] - Increased batch writer threads and made configurable
-* [#589][589] - Added 2nd conditional writer and logging of commit times
-* [#584][584] - Adjust number of conditional writer threads based on cluster 
size
-
-For Accumulo, changes are being made in [ACCUMULO-4066] to decrease the time it
-takes to process conditional mutations.  Conditional mutations are used when
-Fluo commits a transaction.
-
-These changes resulted in nice improvements over beta-1 in testing.  However 
there
-is probably still room for improvement.  More analysis is needed.
-
-#### API Changes
-
-Once Fluo 1.0.0 is released, all releases after that will follow
-[semver](http://semver.org/).  For now some small API changes are still being
-made.  The following API changes happened between beta-1 and beta-2.
-
-* [#566][566] - Added RowColumnValue and made Accumulo init code use it
-* [#551][551] - Added method to get start timestamp of transaction
-* [#550][550] - Changed setObservers() to addObservers()
-
-#### Other important improvements and bug fixes
-
-* [#598][598] - Upgraded Hadoop to 2.6.3 and Accumulo to 1.6.4
-* [#587][587] - Specified datasource for all graphs in fluo's Grafana dashboard
-* [#586][586] - Added efficient and easy way to build Bytes objects
-* [#578][578] - Plot nothing in Grafana when no data exists
-* [#573][573] - Fixed issues building against Accumulo 1.8.0-SNAPSHOT
-* [#561][561] - Stopped checkstyle mvn plugin from running at validate
-* [#559][559] - Eventually drop deleted data
-* [#558][558] - Added arguments to deploy command to skip findbugs, 
checkstyle, and auto-formatting
-* [#556][556] - Make TravisCI deploy snapshot jars after successful builds
-* [#552][552] - Made eclipse stop complaining about unknown plugins
-* [#547][547] - Provide better documentation for LoaderExecutor
-* [#535][535] - Upgraded Twill to 0.6.0-incubating
-* [#520][520] - Consolidate all implementation properties into 
FluoConfigurationImpl
-* [#518][518] - Make Oracle run on a random port
-* [#513][513] - Unable to pass spaces to scan command
-* [#495][495] - Add support for notifications to Fluo formatter
-
-## Testing
-
-For this release, a long run of the [Webindex][webindex] application was 
performed and is documented in
-[a blog post][webindex-post].  A long run of [Fluo stress][fluo-stress] was 
run and documented in 
-[another blog post][stress-post].
-
-[ACCUMULO-4066]: https://issues.apache.org/jira/browse/ACCUMULO-4066
-[tickets]: 
https://github.com/fluo-io/fluo/issues?q=milestone%3A1.0.0-beta-2+is%3Aclosed
-[fluo-dev]: https://github.com/fluo-io/fluo-dev
-[zetten]: https://github.com/fluo-io/zetten
-[fluo-stress]: https://github.com/fluo-io/fluo-stress
-[dropwizard]: https://dropwizard.github.io/metrics/3.1.0/
-[grafana-docs]: /docs/fluo/1.0.0-beta-2/grafana/
-[influxdb]: https://github.com/influxdata/influxdb
-[grafana]: http://grafana.org/
-[webindex]: https://github.com/fluo-io/webindex
-[stress-post]: /blog/2015/12/22/beta-2-pre-release-stress-test/
-[webindex-post]: /blog/2016/01/11/webindex-long-run/
-[598]: https://github.com/fluo-io/fluo/pull/598
-[597]: https://github.com/fluo-io/fluo/issues/597
-[591]: https://github.com/fluo-io/fluo/issues/591
-[590]: https://github.com/fluo-io/fluo/pull/590
-[589]: https://github.com/fluo-io/fluo/pull/589
-[587]: https://github.com/fluo-io/fluo/pull/587
-[586]: https://github.com/fluo-io/fluo/pull/586
-[584]: https://github.com/fluo-io/fluo/pull/584
-[581]: https://github.com/fluo-io/fluo/pull/581
-[580]: https://github.com/fluo-io/fluo/issues/580
-[578]: https://github.com/fluo-io/fluo/pull/578
-[574]: https://github.com/fluo-io/fluo/issues/574
-[573]: https://github.com/fluo-io/fluo/pull/573
-[570]: https://github.com/fluo-io/fluo/issues/570
-[569]: https://github.com/fluo-io/fluo/issues/569
-[568]: https://github.com/fluo-io/fluo/issues/568
-[566]: https://github.com/fluo-io/fluo/pull/566
-[562]: https://github.com/fluo-io/fluo/issues/562
-[561]: https://github.com/fluo-io/fluo/pull/561
-[559]: https://github.com/fluo-io/fluo/issues/559
-[558]: https://github.com/fluo-io/fluo/pull/558
-[556]: https://github.com/fluo-io/fluo/issues/556
-[552]: https://github.com/fluo-io/fluo/pull/552
-[551]: https://github.com/fluo-io/fluo/pull/551
-[550]: https://github.com/fluo-io/fluo/pull/550
-[549]: https://github.com/fluo-io/fluo/pull/549
-[547]: https://github.com/fluo-io/fluo/issues/547
-[544]: https://github.com/fluo-io/fluo/issues/544
-[540]: https://github.com/fluo-io/fluo/issues/540
-[539]: https://github.com/fluo-io/fluo/issues/539
-[538]: https://github.com/fluo-io/fluo/issues/538
-[535]: https://github.com/fluo-io/fluo/pull/535
-[524]: https://github.com/fluo-io/fluo/issues/524
-[523]: https://github.com/fluo-io/fluo/issues/523
-[520]: https://github.com/fluo-io/fluo/issues/520
-[518]: https://github.com/fluo-io/fluo/issues/518
-[513]: https://github.com/fluo-io/fluo/issues/513
-[510]: https://github.com/fluo-io/fluo/issues/510
-[495]: https://github.com/fluo-io/fluo/issues/495
-[20]: https://github.com/fluo-io/fluo/issues/20

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/release-notes/2016-09-27-fluo-1.0.0-incubating.md
----------------------------------------------------------------------
diff --git a/_posts/release-notes/2016-09-27-fluo-1.0.0-incubating.md 
b/_posts/release-notes/2016-09-27-fluo-1.0.0-incubating.md
deleted file mode 100644
index acf9596..0000000
--- a/_posts/release-notes/2016-09-27-fluo-1.0.0-incubating.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Fluo 1.0.0-incubating Release Notes
-date: 2016-09-27 15:30:00
-version: fluo-1.0.0-incubating
----
-
-Apache Fluo 1.0.0-incubating is the first release of Fluo as an Apache project 
and the fourth
-release for the project. For information about changes before this release, 
see the
-[release notes archive](/release-notes/).
-
-## Significant changes
-
-The 1.0.0-incubating release includes [167 commits][commits] that made since 
the last release 
-(1.0.0-beta-2).  The significant changes are summarized below.
-
-#### Stabilized API 
-
-Starting with this release, Apache Fluo's API will follow [semver].  The API 
is defined as
-everything under the org.apache.fluo.api Java package.  Given that the plan is 
to support this API
-for a long time, a lot of API improvements were made since the beta-2 release. 
 The following is a
-list of significant API changes since beta-2.
-
- * [#772][772] : Get with default
- * [#770][770] : Use varargs for Columns
- * [#768][768] : Made Obsever and Application configuration consistent
- * [#743][743] : Make data classes final
- * [#723][723] : Removed FluoAdmin.InitOps()
- * [#714][714] : Use Charsequence in API
- * [#695][695] : Removed all 3rd party types from API
- * [#680][680] : Changed package prefix from io.fluo to org.apache
- * [#647][647] : Added Oracle and Worker to API
- * [#639][639] : Improved scanning API
- * [#626][626] : Added operation to get row+column pairs.  Further improved by 
[#758][758].
- * [#119][119] - Consistently offer String in API
-
-#### Configurable classpath
-
-The previous releases of Fluo contained specific versions of Accumulo, Hadoop, 
Zookeeper, and other
-Fluo dependencies.  However, the actual dependencies needed should be 
determined by the existing
-version of software where Fluo is run.  Fluo changed to a model of making its 
classpath be
-completely configurable by an administrator.  Example classpath configuration 
and download scripts
-ship with Fluo to help make setup easier.  These script were only tested with 
specific versions of
-Hadoop and Accumulo and may not work with all versions.  These changes were 
made in [#706][706] and
-[#687][687]. 
-
-#### New Fluo version command
-
-Added a version command to the Fluo scripts in [#779][779].  This makes it 
easy to automatically
-build shaded jars with the correct version of Fluo for use in Spark and Map 
Reduce.
-
-#### User and historical metrics
-
-Two major improvements related to metrics were made.  Support for user metrics 
was added by
-[#767][767].  This allows observers to easily report application specific 
metrics.  In [#635][635]
-the example InfluxDB and Grafana configurations were updated to show 
historical metrics.
-
-#### Improved transaction processing
-
-Transaction processing throughput was increased by changes in [#593][593] and 
some subsequent bug
-fixes.   These changes moved commit processing from the threads executing user 
code to an
-asynchronous background process.  This allows user threads to queue a 
transaction for commit an
-immediately start working on another notification.  This new process allows 
many more transactions
-to be working through the commit process concurrently.  Before the change a 
worker could only be
-committing up to a few hundred transactions at any time.   After the change, a 
single worker could
-easily be committing tens of thousands of transactions at a time.  These 
changes increase the latency of 
-individual transactions, which can have some drawbacks [#650][650].   For this 
release changes were
-made in [#654][654] to use a priority queue for notifications in the worker.  
The changes in
-[#654][654] partially solves the lock wait problem identified in [#650][650].
-
-#### Improved Accumulo scanning
-
-Fluo utilizes server side Accumulo iterators.  For this release these 
iterators were modified to
-leverage seeking on the sever side.  Before these changes the iterators used 
to sequentially scan
-data.  For popular cells that had a lot versions, this could be slow.  These 
changes were made in
-[#623][623].
-
-## Other changes of interest
-
-* [#668][668] - Added method to append byte to BytesBuilder
-* [#648][648] - Added documentation to help users if YARN is killing containers
-* [#619][619] [#621][621] - Created Fluo logo
-
-## Testing
-
-A two day run of Webindex was started on September 7th using the latest 
snapshot version of Fluo.
-This test used 11 EC2 m3.xlarge nodes.  The test ran without problem.   A good 
bit before that a [3
-day run](/blog/2016/05/17/webindex-long-run-2/) of Webindex was conducted.
-
-[semver]: http://semver.org/
-[commits]: 
https://github.com/apache/incubator-fluo/compare/1.0.0-beta-2...e1dbc60
-[779]: https://github.com/fluo-io/fluo/issues/779
-[772]: https://github.com/fluo-io/fluo/issues/772
-[770]: https://github.com/fluo-io/fluo/issues/770
-[768]: https://github.com/fluo-io/fluo/issues/768
-[767]: https://github.com/fluo-io/fluo/issues/767
-[758]: https://github.com/fluo-io/fluo/issues/758
-[743]: https://github.com/fluo-io/fluo/issues/743
-[723]: https://github.com/fluo-io/fluo/issues/723
-[714]: https://github.com/fluo-io/fluo/issues/714
-[706]: https://github.com/fluo-io/fluo/issues/706
-[695]: https://github.com/fluo-io/fluo/issues/695
-[687]: https://github.com/fluo-io/fluo/issues/687
-[680]: https://github.com/fluo-io/fluo/issues/680
-[668]: https://github.com/fluo-io/fluo/issues/668
-[654]: https://github.com/fluo-io/fluo/issues/654
-[650]: https://github.com/fluo-io/fluo/issues/650
-[648]: https://github.com/fluo-io/fluo/issues/648
-[647]: https://github.com/fluo-io/fluo/issues/647
-[639]: https://github.com/fluo-io/fluo/issues/639
-[635]: https://github.com/fluo-io/fluo/issues/635
-[626]: https://github.com/fluo-io/fluo/issues/626
-[623]: https://github.com/fluo-io/fluo/issues/623
-[621]: https://github.com/fluo-io/fluo/issues/621
-[619]: https://github.com/fluo-io/fluo/issues/619
-[593]: https://github.com/fluo-io/fluo/issues/593
-[119]: https://github.com/fluo-io/fluo/issues/119
-

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
----------------------------------------------------------------------
diff --git a/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md 
b/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
index cba0e24..5f04f8e 100644
--- a/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
+++ b/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
@@ -1,13 +1,113 @@
 ---
-title: Fluo 1.0.0-alpha-1 Release
-date: 2014-10-02 15:30:00
+title: Fluo 1.0.0-alpha-1 released
+date: 2014-10-02 15:30:00 +0000
 version: fluo-1.0.0-alpha-1
 historical: true
-redirect_from: /1.0.0-alpha-1-release/
+redirect_from: 
+  - /1.0.0-alpha-1-release/
+  - /1.0.0-alpha-1-release-notes/
+  - /release-notes/1.0.0-alpha-1/
 ---
 
-The [1.0.0-alpha-1][release] release is the first release of Fluo.  It is not 
ready for production use.  See the [release notes][notes] for 
-significant features. [Javadocs][apidocs] are also available.
+Fluo 1.0.0-alpha-1 is the first official release of Fluo. It contains 83 
initial tickets marked for this first milestone. The roadmap for this release 
included a working initial implementation, completing an initial pass at the 
client API (which will be finalized in 1.0.0), and writing a stress test 
application.  This release has not been tested much at scale and is not ready 
for production use.  More scale and peformance testing will be done for the 
beta release.
+
+Below are resources for this release:
+
+* Download the [Fluo binary tarball][release] for 1.0.0-alpha-1 from GitHub.
+* View the [documentation][docs] for this release.
+* Read the [Javadocs][apidocs].
+* The Fluo [jars] have been deploy to Maven Central.
+
+Fluo is an implementation of Google's [percolator paper][percolator], which 
adds large-scale incremental processing of data using distributed transactions 
and notifications. It runs on [YARN] using [Twill] and stores its data in 
[Accumulo]. 
+
+## Significant features
+
+This alpha release contained a lot of initial features to help establish the 
basic implementation and client API. All of these features will be expected to 
become more robust over time.
+
+#### MiniFluo
+
+MiniAccumulo and MiniFluo make it easy to start a local Fluo instance for 
integration testing. MiniFluo also makes it easy for developers to experiment 
with Fluo locally without installing it on an Accumulo cluster.
+
+#### Garbage Collection
+
+Without garbage collection, the columnns in a Fluo table would grow without 
bound as updates are applied over time. Because of this, it's important to 
clean up old fully-processed (and no longer being read) transaction data. The 
initial implementation of garbage collection kept N versions of columns. 
[Fluo-8][8] added the ability to garbage collect all column versions that are 
no longer being read by transactions anywhere else in the cluster.
+
+#### MapReduce InputFormat
+
+The FluoInputFormat allows a specific snapshot to be read into a mapreduce 
job. It was established in [Fluo-7][7].
+
+#### FluoFileOutputFormat and FluoOutputFormat
+
+The FluoFileOuputFormat enables the bulk ingest of a Fluo table using 
mapreduce by creating the Accumulo r-files in HDFS. The FluoOutputFormat pushes 
keys directly into the Accumulo tablet servers through the client API. 
[Fluo-35][35] added this feature.
+
+#### Fluo Workers and Oracle running in Yarn
+
+Fluo can use Yarn to manage fault tolerance and guarantee multiple worker 
processes and some number of Oracle processes are kept running across the 
cluster. [Apache Twill][twill] was used for the Yarn integration. [Fluo-11][11] 
added an application that will deploy Fluo to a Yarn cluster.
+
+#### Fluo API
+
+Fluo provides a fluent-builder API for creating transactions to read and 
mutate data of various different data types in the Fluo table. This API was 
finalized in [Fluo-23][23] and [Fluo-98][98] when it was moved into its own 
module.  It includes a type layer (finished in [Fluo-153][153]) that makes it 
easier to work with different types, default values, null return types, and 
row/column maps.
+
+#### Stress test
+
+A [stress test][stress] was created that uses a tree to force collisions on 
transactions trying to mutate multiple columns at the same time. This was 
established in [Fluo-24][24].
+
+Other important improvements and features:
+
+* [Fluo-1][1]     - Create scripts for starting/stopping services
+* [Fluo-3][3]     - use Curator for leader election and leader discovery
+* [Fluo-13][13]   - Register clients that perform transactions in Zookeeper
+* [Fluo-15][15]   - Leader election for the Oracle Server
+* [Fluo-16][16]   - Allow observer notification to be configured in 
AbstractObserver class
+* [Fluo-89][89]   - OracleApp should allow configurable number of instances
+* [Fluo-98][98]   - Create a Range class for Fluo
+* [Fluo-123][123] - Hide implementation of Bytes in the API
+* [Fluo-130][130] - Expose MiniFluo in public API
+* [Fluo-131][131] - Make LoaderExector implement closeable
+* [Fluo-147][147] - Create fluo-accumulo module for Accumulo iterators and 
formatter
+* [Fluo-175][175] - Add newTransaction() method to FluoClient
+* [Fluo-186][186] - Add Exceptions to API
+
+## Testing
+
+All unit and integration tests passed.  Two [stress tests][stress] were run 
successfully on a 20-node cluster with one test generating 2000 integers and 
another generating 5000 integers.  The 5000 integer test took about 10 minutes 
to run after the MapReduce load of integers was complete.
+
+## Current Status of Percolator Implementation
+
+The following tables identify the features necessary for a full implementation 
of Percolator and the current state of Fluo with regards to the implementation. 
For alpha, a test to excercise some of these features at scale was created, 
however, it was not run at scale for long periods. One of the goals for beta is 
to have at least a 24hr run of the scale test, on at least 20 nodes, succeed.
+
+### Necessary features:
+
+| Percolator Feature         |  Details | Testing |
+|----------|-------------------|------|
+| ACID-compliant cross-row transactions | Provides distributed transactions 
with ACID guarantees that work across Accumulo rows. Rows are distributed 
across tablet servers. | IT,CST,[#240][240]<sup>1</sup> |
+| Observers |    Perform transactions by sending read/write RPCs to Accumulo 
tablet servers, which in turn send read/write RPCs to HDFS.   |  IT,CST |
+| Worker Process | Scans Accumulo for changed columns and invokes necessary 
observers as function calls on the worker. | IT,CST |
+| Timestamp Oracle | Provides strictly increasing timestamps; a property 
required for correct operation of the snapshot isolation protocol. |  IT,CST |
+| Oracle Failover | When an active Oracle process dies, timestamps should be 
served from a different Oracle. They should never go backwards. | 
IT,[#37][37],[#241][241]<sup>1</sup> |
+| Lightweight Lock Service | Makes searches for dirty notifications more 
efficient. Zookeeper is used in this case. Should be low-latency, replicated, 
balanced, and persist to a backing store. |    IT,CST |
+| Multithreaded Transasctions | Allows highly parallel execution of 
transactions and synchronization only during get() and commit() upon which 
transactions actually collide. |    IT,CST |
+| Snapshot Isolation | Non-serializable isolation mostly implemented through 
MVCC provided through Accumulo's timestamp portion of the key. | 
IT,CST,[#240][240]<sup>1</sup> |
+| Roll-back / Roll-forward semantics | Failures during the first phase of 
commit cause transactions to be rolled back while failures during the second 
phase can cause them to be rolled forward. | IT,[#240][240]<sup>1</sup> |
+
+<sup>1</sup> This feature has been at least partially tested.
+
+### Performance enhancements:
+
+| Enhancement         |  Details | Testing |
+|----------|-------------------|------|
+| Locality Group for NOTIFY column |  Add an extra index in the underlying 
r-files for the notify column where it can be scanned faster by workers.  | 
IT,CST  | 
+| Worker scan conflict resolution | Workers register random tablets they 
choose to scan. When two workers generate the same tablet, one of them 
re-generates a new random tablet. | [#5][5] |
+| Worker advertisement | Workers advertise through the lock service so that 
the system can know if they failed and any transactions upon which they are 
working can be rolled back or rolled forward | IT | 
+| Oracle batching | Timestamps get allocated in batch to workers. Each worker 
should share one connection to Oracle to limit RPCs across threads | IT,CST |
+| Weak Notifications | Allows notification of a cell without the possibility 
of transactional conflict through a special type of column that can be notified 
but not written to | IT |
+| Conditional Mutations | Allows READ-MODIFY-WRITE of a mutation in a single 
RPC.  | IT,CST |
+| Conditional Mutation batching | Delay sending of conditional mutations 
destined for same tablet server so they can be batched. Lowers number of RPCs, 
adds latency but provides better parallelism. | IT,CST |
+| Read batching | Delaying of read operations on tablet server for batching | 
[#138][138] |
+| Prefetching & read-ahead caching | Prediction made each time a column is 
read, which other columns will be read in the same transaction based on 
previous behavior. | [#12][12] |
+
+* IT = Integration tests, CST = Cluster stress tests
+* Testing columns providing a ticket number have not yet been implemented.
 
 ## Quickstart
 
@@ -75,10 +175,14 @@ To create an observer, follow these steps:
 3. Configure your Fluo instance to use this observer by modifying the Observer 
section of [fluo.properties].  
 4. Restart your Fluo instance so that your Fluo workers load the new observer.
 
+[YARN]: 
http://hadoop.apache.org/docs/r2.5.1/hadoop-yarn/hadoop-yarn-site/YARN.html
+[Accumulo]: https://accumulo.apache.org/
+[jars]: http://search.maven.org/#search%7Cga%7C1%7Cfluo
+[Twill]: http://twill.incubator.apache.org/
+[percolator]: http://research.google.com/pubs/pub36726.html
 [apidocs]: /apidocs/fluo/1.0.0-alpha-1/
+[docs]: /docs/fluo/1.0.0-alpha-1/
 [quickstart]: https://github.com/fluo-io/fluo-quickstart
-[notes]: /release-notes/fluo-1.0.0-alpha-1/
-[Accumulo]: https://accumulo.apache.org/
 [Hadoop]: http://hadoop.apache.org/
 [Zookeeper]: http://zookeeper.apache.org/
 [release]: https://github.com/fluo-io/fluo/releases/tag/1.0.0-alpha-1
@@ -88,3 +192,33 @@ To create an observer, follow these steps:
 [FluoClient]: 
https://github.com/fluo-io/fluo/blob/1.0.0-alpha-1/modules/api/src/main/java/io/fluo/api/client/FluoClient.java
 [fluo.properties]: 
https://github.com/fluo-io/fluo/blob/1.0.0-alpha-1/modules/distribution/src/main/config/fluo.properties
 [AbstractObserver]: 
https://github.com/fluo-io/fluo/blob/1.0.0-alpha-1/modules/api/src/main/java/io/fluo/api/observer/AbstractObserver.java
+[ACCUMULO-1000]: https://issues.apache.org/jira/browse/ACCUMULO-1000
+[percolator]: http://research.google.com/pubs/pub36726.html
+[twill]: http://twill.incubator.apache.org/
+[stress]: 
https://github.com/fluo-io/fluo/blob/1.0.0-alpha-1/modules/stress/README.md
+[241]: https://github.com/fluo-io/fluo/issues/241
+[240]: https://github.com/fluo-io/fluo/issues/240
+[186]: https://github.com/fluo-io/fluo/issues/186
+[175]: https://github.com/fluo-io/fluo/issues/175
+[153]: https://github.com/fluo-io/fluo/issues/153
+[147]: https://github.com/fluo-io/fluo/issues/147
+[138]: https://github.com/fluo-io/fluo/issues/138
+[131]: https://github.com/fluo-io/fluo/issues/131
+[130]: https://github.com/fluo-io/fluo/issues/130
+[123]: https://github.com/fluo-io/fluo/issues/123
+[98]: https://github.com/fluo-io/fluo/issues/98
+[89]: https://github.com/fluo-io/fluo/issues/89
+[37]: https://github.com/fluo-io/fluo/issues/37
+[35]: https://github.com/fluo-io/fluo/issues/35
+[24]: https://github.com/fluo-io/fluo/issues/24
+[23]: https://github.com/fluo-io/fluo/issues/23
+[16]: https://github.com/fluo-io/fluo/issues/16
+[15]: https://github.com/fluo-io/fluo/issues/15
+[13]: https://github.com/fluo-io/fluo/issues/13
+[12]: https://github.com/fluo-io/fluo/issues/12
+[11]: https://github.com/fluo-io/fluo/issues/11
+[8]: https://github.com/fluo-io/fluo/issues/8
+[7]: https://github.com/fluo-io/fluo/issues/7
+[5]: https://github.com/fluo-io/fluo/issues/5
+[3]: https://github.com/fluo-io/fluo/issues/3
+[1]: https://github.com/fluo-io/fluo/issues/1

http://git-wip-us.apache.org/repos/asf/incubator-fluo-website/blob/05f7bf0d/_posts/release/2015-06-09-fluo-1.0.0-beta-1.md
----------------------------------------------------------------------
diff --git a/_posts/release/2015-06-09-fluo-1.0.0-beta-1.md 
b/_posts/release/2015-06-09-fluo-1.0.0-beta-1.md
index 99fa56b..1ccaf09 100644
--- a/_posts/release/2015-06-09-fluo-1.0.0-beta-1.md
+++ b/_posts/release/2015-06-09-fluo-1.0.0-beta-1.md
@@ -1,35 +1,207 @@
 ---
-title: Fluo 1.0.0-beta-1 Release
-date: 2015-06-09 18:30:00
+title: Fluo 1.0.0-beta-1 released
+date: 2015-06-09 18:30:00 +0000
 version: fluo-1.0.0-beta-1
 historical: true
-redirect_from: /1.0.0-beta-1-release/
+redirect_from:
+  - /1.0.0-beta-1-release/
+  - /1.0.0-beta-1-release-notes/
+  - /release-notes/fluo-1.0.0-beta-1/
 ---
 
-The [1.0.0-beta-1][release] release is the second release of Fluo.  It 
contains the following significant improvements:
-
- * Simplified administration of Fluo on a local machine or EC2 cluster
- * Transaction metrics are now viewable using common monitoring tools
- * Improved processing of notifications in Fluo workers
- * Easier management of Fluo from the command line
- * Support for running multiple Fluo applications on a single cluster
- * Improved the deletion of observer notifications
-
-This release is not recommended for production use.  There is no upgrade path 
from 1.0.0-alpha-1 to 1.0.0-beta-1.
+Fluo 1.0.0-beta-1 is the second official release of Fluo. Fluo is an 
implementation of Google's [percolator paper][paper], which adds large-scale 
incremental 
+processing of data using distributed transactions and notifications. It runs 
on [YARN] and stores its data in [Accumulo]. 
 
 Below are resources for this release:
 
- * Read the [release notes][notes] for a full list of notable features and bug 
fixes.
- * View the [documentation] for help getting started with Fluo.
  * Download the [Fluo binary tarball][release] for 1.0.0-beta-1 from GitHub.
+ * View the [documentation] for help getting started with Fluo.
  * [Javadocs][apidocs] are available for this release.
  * A [tag] of Fluo codebase for 1.0.0-beta-1 is available.
+ * Fluo [jars] have been deployed to Maven Central.
  * The [Quickstart] and [Phrasecount] applications were updated to work with 
this release.
 
+This release closed [133 tickets][tickets]. This release is not recommended 
for production use.
+There is no upgrade path from 1.0.0-alpha-1 to 1.0.0-beta-1.
+
+## Significant features
+
+This release contains many new features that makes it easier to run, develop, 
and monitor Fluo applications.
+
+#### Simplified Fluo administration on a local machine or EC2 cluster
+
+Developers can now run Fluo and its dependencies on their local machine 
([#92][92]) or an AWS EC2 cluster ([#356][356]) using a few simple commands.
+This was done by creating two administration tools called [Fluo-dev][fluo-dev] 
and [Fluo-deploy][fluo-deploy] whose scripts and configuration reside in repos
+separate from the Fluo code base.  These tools allow developers to collaborate 
and share configuration for running Fluo.
+
+#### Transaction metrics are viewable using common monitoring tools
+
+Fluo now publishes metrics ([#20][20]) about transactions, collisions, and 
timestamps using [Dropwizard metrics][dropwizard].  These metrics are by 
default published 
+using JMX and are viewable using JConsole or JVisualVM.  Fluo can also be 
configured to publish metrics to Graphite or Ganglia.  View the [metrics 
documentation][metrics]
+for more information.
+
+#### Improved processing of notifications in Fluo workers
+
+Fluo workers were refactored to separate the code used for finding and 
executing work.  Each worker uses a single thread for finding 
+work ([#19][19]).  A new method was introduced to partition work among workers 
using a hash+mod of notifications ([#282][282]).
+The commit message for [4100e23][4100e23] contains a good description of some 
of the benefits and drawback of the current
+hashing approach.
+
+#### Improved the deletion of observer notifications
+
+When a cell is deleted in Accumulo, a delete marker is inserted.  Delete 
markers stay around until
+all files in a tablet are compacted.  For Fluo this could cause a lot of 
notification delete markers
+to build up over time.  To avoid this buildup, the way Fluo deletes 
notifications was changed in
+([#457][457]).  Accumulo delete markers are no longer used, Fluo now uses a 
custom delete marker for
+notifications.  The custom deleter marker allows Fluo to do analysis when 
Accumulo flushes memory to
+disk and avoid writing many delete markers to persistent storage.
+
+#### Easier management of Fluo from the command line
+
+Fluo now provides different scripts (**fluo**, **mini-fluo**, & 
**local-fluo**) for managing Fluo using a YARN cluster, MiniFluo, or local 
processes.  Several commands
+were created for these scripts.  A **scan** command allows users to print a 
snapshot of a Fluo table ([#319][319]).  A **info** command shows locations of 
containers
+when running Fluo in YARN ([#297][297]).  A **classpath** command gives users 
a list of jars needed to execute Fluo client code ([#436][436]).  A **wait** 
command will
+sleep until all notifications are processed ([#434][434]).
+
+#### Support for running multiple Fluo applications on a single cluster
+
+Users can now run multiple Fluo applications using a single cluster 
([#454][454]).  This enables different Fluo users to share the same cluster.  
Fluo applications
+can be started and stopped independently.  Each application has its own 
configuration.
+
+#### Fluo build improvements
+
+On each build, all Java code is automatically formatted based on Google Java 
Style ([#479][479]).  Also, checkstyle and findbugs will fail the build if 
certain
+standards are not reached ([#185][185]).  The POM is also sorted ([#493][493]).
+
+#### Organized Fluo code base
+
+The Fluo stress test was moved to its own [repo][fluo-stress] and is no longer 
a sub-module ([#385][385]).  MiniFluo was moved from fluo-core to the fluo-mini 
+module/jar ([#439][439]).  This reduced the number of dependencies in 
fluo-core.  However, developers will now need to include the fluo-mini jar in 
their Maven
+POM if they start MiniFluo.
+
+#### Fluo testing improvements
+
+Integration tests can now be run from Eclipse ([#322][322]).  Several new 
[unit tests][unit] were created.
+
+#### Other important improvements and bug fixes
+
+* [#470][470] - Replaced FluoFileOutputFormat with an Accumulo Key/Value 
generator
+* [#460][460] - Reduced Fluo API module dependencies
+* [#456][456] - Fixed bug with notifications being lost when processes died
+* [#446][446] - Simplified log configuration and configure rolling log files 
in YARN
+* [#442][442] - Reduced the number of curator clients in FluoAdmin
+* [#383][383] - Improved transaction logging to help users debug collisions. 
See [debugging documentation][debug].
+* [#365][365] - Analyze Fluo code to see what non-public Accumulo APIs are used
+* [#362][362] - Made API data objects immutable
+* [#349][349] - Support application level configuration in fluo.properties
+* [#342][342] - Add a configurable retry timeout to Fluo clients
+* [#294][294] - Fluo now uses chroot suffix in its Zookeeper connection.
+* [#293][293] - Add argument checking to FluoConfiguration
+* [#244][244] - Make re-initialization easier for user
+
+## Testing
+
+A successful long stress test run was conducted using Fluo built from commit
+[fb647dd][fb647dd].  The test ran very well and never fell behind like a
+[previous long run][old-stress-run] of stress did.  The test had the following
+properties.
+ 
+ * Initialized stress test using 1 billion random integers.
+ * Ran 150 incremental loads of 100 thousand integers.  Slept 3 minutes 
between loads. 
+ * Used 19 m3.xlarge nodes on EC2.  16 workers and 3 masters
+ * Configuration for the test committed and tagged in git : [fluo-deploy 
tag][fd-tag-1] and [fluo-stress tag][fs-tag-1]
+ * Opened two issues as a result of test [#499][499] and 
[fluo-stress#30][fs-30]
+
+Below is the trailing output from running the test.
+
+    *****Generating and loading incremental data set 148*****
+    *****Generating and loading incremental data set 149*****
+    *****Generating and loading incremental data set 150*****
+    *****Calculating # of unique integers using MapReduce*****
+                    UNIQUE=1014486419
+    *****Wait for Fluo to finish processing*****
+    05:33:40.158 [main] INFO  io.fluo.cluster.runner.AppRunner - The wait 
command will exit when all notifications are processed
+    05:33:40.417 [Thread-3] INFO  io.fluo.core.oracle.OracleClient - Connected 
to oracle at worker4:9913
+    05:33:41.308 [main] INFO  io.fluo.cluster.runner.AppRunner - All 
processing has finished!
+    *****Printing # of unique integers calculated by Fluo*****
+    Total at root : 1014486419
+    Nodes Scanned : 59605
+    *****Verifying Fluo & MapReduce results match*****
+    Success! Fluo & MapReduce both calculated 1014486419 unique integers
+
+The test ran for a little over 12 hours.  Below are two plots pulled from
+graphite showing the number of notifications queued and transaction rate over
+the entire test run.  Load transactions are not included in the rate.  The rate
+is transactions per second.  The accuracy of these plots is uncertain because
+no graphite configuration changes were made.  The plots do seem within the
+ballpark.
+
+![Notifications Queued](/resources/release/1.0.0-beta-1/queued.png 
"Notifications Queued") ![Transaction 
rate](/resources/release/1.0.0-beta-1/rate.png "Transaction Rate")
+
+[documentation]: /docs/fluo/1.0.0-beta-1/
+[quickstart]: https://github.com/fluo-io/fluo-quickstart
+[phrasecount]: https://github.com/fluo-io/phrasecount
+[YARN]: 
http://hadoop.apache.org/docs/r2.5.1/hadoop-yarn/hadoop-yarn-site/YARN.html
+[Accumulo]: https://accumulo.apache.org/
+[jars]: http://search.maven.org/#search%7Cga%7C1%7Cfluo
+[paper]: http://research.google.com/pubs/pub36726.html
+[javadocs]: /apidocs/fluo/1.0.0-beta-1/
 [release]: https://github.com/fluo-io/fluo/releases/tag/1.0.0-beta-1
-[notes]: /release-notes/fluo-1.0.0-beta-1/
 [apidocs]: /apidocs/fluo/1.0.0-beta-1/
 [documentation]: /docs/fluo/1.0.0-beta-1/
 [tag]: https://github.com/fluo-io/fluo/tree/1.0.0-beta-1
 [Quickstart]: https://github.com/fluo-io/fluo-quickstart
 [Phrasecount]: https://github.com/fluo-io/phrasecount
+[tickets]: 
https://github.com/fluo-io/fluo/issues?q=milestone%3A1.0.0-beta-1+is%3Aclosed
+[fd-tag-1]: https://github.com/keith-turner/fluo-deploy/tree/beta-long-test-1
+[fs-tag-1]: https://github.com/keith-turner/fluo-stress/tree/beta-long-test-1
+[fluo-dev]: https://github.com/fluo-io/fluo-dev
+[fluo-deploy]: https://github.com/fluo-io/fluo-deploy
+[fluo-stress]: https://github.com/fluo-io/fluo-stress
+[dropwizard]: https://dropwizard.github.io/metrics/3.1.0/
+[debug]: 
https://github.com/fluo-io/fluo/blob/1.0.0-beta-1/docs/applications.md#debugging-applications
+[metrics]: https://github.com/fluo-io/fluo/blob/1.0.0-beta-1/docs/metrics.md
+[old-stress-run]: /blog/2014/12/30/stress-test-long-run/
+[unit]: 
https://github.com/fluo-io/fluo/issues?utf8=%E2%9C%93&q=milestone%3A1.0.0-beta-1+is%3Aclosed+%22unit+test%22
+[4100e23]: 
https://github.com/fluo-io/fluo/commit/4100e236b8438350e30eda924a6360e2c722ae37
+[fb647dd]: 
https://github.com/fluo-io/fluo/commit/fb647dd6a470e8015654f8ed99b9196f5f49582a
+[499]: https://github.com/fluo-io/fluo/issues/499
+[493]: https://github.com/fluo-io/fluo/issues/493
+[479]: https://github.com/fluo-io/fluo/issues/479
+[470]: https://github.com/fluo-io/fluo/issues/470
+[460]: https://github.com/fluo-io/fluo/issues/460
+[457]: https://github.com/fluo-io/fluo/issues/457
+[456]: https://github.com/fluo-io/fluo/issues/456
+[454]: https://github.com/fluo-io/fluo/issues/454
+[446]: https://github.com/fluo-io/fluo/issues/446
+[442]: https://github.com/fluo-io/fluo/issues/442
+[439]: https://github.com/fluo-io/fluo/issues/439
+[436]: https://github.com/fluo-io/fluo/issues/436
+[434]: https://github.com/fluo-io/fluo/issues/434
+[385]: https://github.com/fluo-io/fluo/issues/385
+[383]: https://github.com/fluo-io/fluo/issues/383
+[365]: https://github.com/fluo-io/fluo/issues/365
+[362]: https://github.com/fluo-io/fluo/issues/362
+[356]: https://github.com/fluo-io/fluo/issues/356
+[342]: https://github.com/fluo-io/fluo/issues/342
+[349]: https://github.com/fluo-io/fluo/issues/349
+[322]: https://github.com/fluo-io/fluo/issues/322
+[319]: https://github.com/fluo-io/fluo/issues/319
+[297]: https://github.com/fluo-io/fluo/issues/297
+[293]: https://github.com/fluo-io/fluo/issues/293
+[294]: https://github.com/fluo-io/fluo/issues/294
+[282]: https://github.com/fluo-io/fluo/issues/282
+[244]: https://github.com/fluo-io/fluo/issues/244
+[241]: https://github.com/fluo-io/fluo/issues/241
+[240]: https://github.com/fluo-io/fluo/issues/240
+[185]: https://github.com/fluo-io/fluo/issues/185
+[138]: https://github.com/fluo-io/fluo/issues/138
+[92]: https://github.com/fluo-io/fluo/issues/92
+[37]: https://github.com/fluo-io/fluo/issues/37
+[20]: https://github.com/fluo-io/fluo/issues/20
+[19]: https://github.com/fluo-io/fluo/issues/19
+[12]: https://github.com/fluo-io/fluo/issues/12
+[5]: https://github.com/fluo-io/fluo/issues/5
+[fs-30]: https://github.com/fluo-io/fluo-stress/issues/30
+
+

Reply via email to