accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mmil...@apache.org
Subject [accumulo-website] 02/02: Jekyll build from master:aa8b44d
Date Wed, 05 Jun 2019 21:34:55 GMT
This is an automated email from the ASF dual-hosted git repository.

mmiller pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git

commit d2eef7b3ae3214ba3250e70904fe465168ee3a3f
Author: Mike Miller <mmiller@apache.org>
AuthorDate: Wed Jun 5 12:12:34 2019 -0400

    Jekyll build from master:aa8b44d
    
    Refactored contributor guide (#178)
    
    * Split guide into multiple docs
    * Simplified main index page
    * Remove duplicate section
    Co-authored-by: Tanisha Faulkner <tanisha.faulkner@me.com>
---
 contributor/{rb.html => advanced-contributor.html} | 229 ++++---
 contributor/{rb.html => building.html}             | 180 +++---
 contributor/{rb.html => testing-release.html}      | 161 ++---
 contributors-guide/index.html                      | 717 +--------------------
 feed.xml                                           |   4 +-
 5 files changed, 262 insertions(+), 1029 deletions(-)

diff --git a/contributor/rb.html b/contributor/advanced-contributor.html
similarity index 55%
copy from contributor/rb.html
copy to contributor/advanced-contributor.html
index 2809d22..2b45674 100644
--- a/contributor/rb.html
+++ b/contributor/advanced-contributor.html
@@ -25,7 +25,7 @@
 <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/v/bs/jq-2.2.3/dt-1.10.12/datatables.min.css">
 <link href="/css/accumulo.css" rel="stylesheet" type="text/css">
 
-<title>Using Review Board</title>
+<title>Advanced Contributor</title>
 
 <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"></script>
 <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script>
@@ -136,113 +136,128 @@
         </div>
         <div id="content">
           
-          <h1 class="title">Using Review Board</h1>
+          <h1 class="title">Advanced Contributor</h1>
           
-          <p>The Apache Software Foundation provides an <a href="https://reviews.apache.org">instance</a> of
-<a href="https://www.reviewboard.org">Review Board</a> (RB) for projects to use in code reviews. Here is how RB can
-be used to support development in the context of the
-<a href="/contributor/bylaws">Apache Accumulo bylaws</a>.</p>
-
-<p>Contributors to Accumulo are encouraged to use RB for non-trivial patches and
-any time feedback is desired. No one is required to use RB, but its ready
-availability and better interface for feedback can help with reviews. Committers
-seeking review prior to pushing changes can also benefit similarly. It should
-be noted that more recently the use of GitHub has been overtaking the use of 
-Review Board for code reviews.</p>
-
-<h2 id="roles-for-review-board">Roles for Review Board</h2>
-
-<h3 id="optional-pre-commit-review">Optional Pre-Commit Review</h3>
-
-<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so code
-review does not need to occur prior to commit. However, a committer may opt to
-hold a code review before commit for changes that, in their opinion, would
-benefit from additional attention. RB can be used to conduct such code reviews.</p>
-
-<h3 id="consensus-approval-after-a-code-change-veto">Consensus Approval after a Code Change Veto</h3>
-
-<p>Code changes are approved by lazy approval, with consensus approval following
-a veto (see the <a href="/contributor/bylaws#actions">Actions</a> section of the bylaws). RB can be used
-to coordinate a consensus approval vote by providing a convenient view of the
-code change under consideration. The vote itself must still be held on the
-developer mailing list.</p>
-
-<h2 id="guidelines-for-posting-a-review">Guidelines for Posting a Review</h2>
-
-<ul>
-  <li>It is best to post a git-generated patch as the basis for a review. RB does
-not support patches containing multiple commits, so either squash commits
-first, or submit a diff spanning the changeset. The <code class="highlighter-rouge">rbt</code> and <code class="highlighter-rouge">post-review</code>
-tools generate diffs.</li>
-  <li>Strive to make your changes small. Reviewers are less likely to want to
-trudge through a review with lots of changes, and are more likely to miss
-problems.</li>
-  <li>Begin the summary of the review with a JIRA issue number. A review must
-always be associated with a JIRA issue. The issue number should also be
-entered in the “Bugs” field of the review, providing a link to JIRA.</li>
-  <li>The “Branch” field should contain the name of the branch that the code change
-is based on (e.g., the base of your git feature branch).</li>
-  <li>Include the “accumulo” user group as reviewers. Also include specific people
-as individual reviewers, even if they are in the “accumulo” group, if you
-deem them of primary importance for the review (e.g., you have been working
-out problems with the review with them, they are expert in the area).</li>
-  <li>Use the description to summarize the change under review. Include helpful
-instructions to the reviewers here.</li>
-  <li>Describe any testing done on the change. It is not expected that reviewers
-will do their own testing, and they may reject the review if you have not
-done sufficient testing yourself.</li>
-  <li>Avoid submitting generated code for review if it can be reproduced by a
-reviewer.</li>
-</ul>
-
-<p>After the review is published, set the status of the associated JIRA issue to
-“Patch Available” as a signal to reviewers. Also, link to the review from the
-issue (More -&gt; Link -&gt; Web Link) to help viewers of the issue find the review
-and assess its progress.</p>
-
-<h2 id="guidelines-for-reviewing-code">Guidelines for Reviewing Code</h2>
-
-<ul>
-  <li>Try to associate comments with relevant lines of code in the review.</li>
-  <li>By default, each comment opens a review issue. If a comment pertains to
-something that should not block the review from completing successfully, then
-clear the “Open an issue” checkbox before saving your feedback. Examples that
-might qualify as non-issues: minor formatting/whitespace issues, spelling
-mistakes, general background questions.</li>
-  <li>If a review looks good, be sure to “Ship It” by either using the “Ship It!”
-button or by submitting a general review with the “Ship It” checkbox checked.</li>
-</ul>
-
-<h2 id="guidelines-for-completing-a-review">Guidelines for Completing a Review</h2>
-
-<p>These guidelines do not apply to consensus approval votes, since the vote
-completion depends on the votes registered in the developer mailing list.</p>
-
-<ul>
-  <li>Use your judgement for the number of “Ship It”s you want to receive to
-consider a review passed. Usually, getting one “Ship It” is enough to proceed
-with a commit. It is recommended that the “Ship It” be from a committer who
-is a neutral party not involved in the change under review.</li>
-  <li>Use your judgement for the minimum time length you set for the review. Simple
-changes can be up for just a day, while complex ones should take up to seven.</li>
-  <li>Review time should be extended in the face of problems discovered in the
-review. Update the review with improved code instead of discarding (i.e.,
-closing unsuccessfully) it and beginning a new one.</li>
-  <li>A review should not be “submitted” (i.e., closed successfully) unless there
-are no outstanding issues. Check with reviewers to ensure that their issues
-are resolved satisfactorily.</li>
-  <li>A review should be “discarded” if the code requires major rework or it
-becomes obvious it should never be committed (due to design changes,
-becoming overcome by events, being back-burnered, etc.).</li>
-  <li>Don’t leave a review open indefinitely. Once you have received sufficient
-feedback to submit or discard it, do so. If there has been no activity for
-some time, discard the review. A new one can always be created later.</li>
-</ul>
-
-<p>Once you’ve closed a review as submitted, if you are unable to commit your
-changes yourself, attach the final version of them to the relevant JIRA issue.
-They should be in the form of a patch containing a single commit,
-<a href="/contributor/git#contributors">per the final steps of the contribution process</a>.</p>
+          <h2 id="apply-patch-from-contributor">Apply patch from contributor</h2>
+
+<p>Developers should use the following steps to apply patches from
+contributors:</p>
+
+<ol>
+  <li>
+    <p>Checkout the branch for the major version which the patch is intended:</p>
+
+    <p><code class="highlighter-rouge">git checkout 1.9</code></p>
+  </li>
+  <li>
+    <p>Verify the changes introduced by the patch:</p>
+
+    <p><code class="highlighter-rouge">git apply --stat ACCUMULO-12345.patch</code></p>
+  </li>
+  <li>
+    <p>Verify that the patch applies cleanly:</p>
+
+    <p><code class="highlighter-rouge">git apply --check ACCUMULO-12345.patch</code></p>
+  </li>
+  <li>
+    <p>If all is well, apply the patch:</p>
+
+    <p><code class="highlighter-rouge">git am --signoff &lt; ACCUMULO-12345.patch</code></p>
+  </li>
+  <li>
+    <p>When finished, push the changes:</p>
+
+    <p><code class="highlighter-rouge">git push origin 1.9</code></p>
+  </li>
+  <li>
+    <p>Merge where appropriate:</p>
+
+    <p><code class="highlighter-rouge">git checkout master &amp;&amp; git merge 1.9</code></p>
+  </li>
+</ol>
+
+<h2 id="merging-change-to-multiple-versions">Merging change to multiple versions</h2>
+
+<p>Merging can be a very confusing topic for users switching to Git, but it can be
+summarized fairly easily.</p>
+
+<ol>
+  <li>
+    <p><strong>Precondition</strong>: choose the right branch to start! (lowest, applicable version
+for the change)</p>
+  </li>
+  <li>
+    <p>Get your changes fixed for that earliest version.</p>
+  </li>
+  <li>
+    <p>Switch to the next highest version which future minor versions will be
+released (non-EOL major release series).</p>
+  </li>
+  <li>
+    <p><code class="highlighter-rouge">git-merge</code> the branch from #1 into the current.</p>
+  </li>
+  <li>
+    <p>In the face of conflicts, use options from <code class="highlighter-rouge">git-merge</code> to help you.</p>
+
+    <ul>
+      <li><code class="highlighter-rouge">git checkout new-version &amp;&amp; git merge --stat old-version</code></li>
+      <li><code class="highlighter-rouge">git checkout new-version &amp;&amp; git merge --no-commit old-version</code></li>
+    </ul>
+  </li>
+  <li>
+    <p>Treat your current branch as the branch from #2, and repeat from #2.</p>
+  </li>
+</ol>
+
+<p>When merging changes across major releases, there is always the possibility of
+changes which are applicable/necessary in one release, but not in any future
+releases, changes which are different in implementation due to API changes, or
+any number of other cases. Whatever the actual case is, the developer who made
+the first set of changes (you) is the one responsible for performing the merge
+through the rest of the active versions. Even when the merge may results in a
+zero-length change in content, this is incredibly important to record, as you
+are the one who knows that this zero-length change in content is correct!</p>
+
+<h2 id="code-review-process">Code review process</h2>
+
+<p>Accumulo primarily uses GitHub (via pull requests) for code reviews.</p>
+
+<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so a code review does not need to occur prior to commit. However, a committer has the option to hold a code review before a commit happens if, in their opinion, it would benefit from additional attention. Full details of the code review process for Accumulo is documented <a href="./rb">here</a></p>
+
+<h2 id="coding-practices">Coding Practices</h2>
+
+<table class="table">
+  <tbody>
+    <tr>
+      <td><strong>License Header</strong></td>
+      <td>Always add the current ASF license header as described in [ASF Source Header][srcheaders].</td>
+    </tr>
+    <tr>
+      <td><strong>Trailing Whitespaces</strong></td>
+      <td>Remove all trailing whitespaces. Eclipse users can use Source→Cleanup option to accomplish this.</td>
+    </tr>
+    <tr>
+      <td><strong>Indentation</strong></td>
+      <td>Use 2 space indents and never use tabs!</td>
+    </tr>
+    <tr>
+      <td><strong>Line Wrapping</strong></td>
+      <td>Use 100-column line width for Java code and Javadoc.</td>
+    </tr>
+    <tr>
+      <td><strong>Control Structure New Lines</strong></td>
+      <td>Use a new line with single statement if/else blocks.</td>
+    </tr>
+    <tr>
+      <td><strong>Author Tags</strong></td>
+      <td>Do not use Author Tags. The code is developed and owned by the community.</td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="merging-practices">Merging Practices</h2>
+
+<p>Changes should be merged from earlier branches of Accumulo to later branches. Ask the <a href="mailto:dev@accumulo.apache.org">dev list</a> for instructions.</p>
 
 
         </div>
diff --git a/contributor/rb.html b/contributor/building.html
similarity index 54%
copy from contributor/rb.html
copy to contributor/building.html
index 2809d22..e865893 100644
--- a/contributor/rb.html
+++ b/contributor/building.html
@@ -25,7 +25,7 @@
 <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/v/bs/jq-2.2.3/dt-1.10.12/datatables.min.css">
 <link href="/css/accumulo.css" rel="stylesheet" type="text/css">
 
-<title>Using Review Board</title>
+<title>Building Accumulo</title>
 
 <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"></script>
 <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script>
@@ -136,113 +136,79 @@
         </div>
         <div id="content">
           
-          <h1 class="title">Using Review Board</h1>
+          <h1 class="title">Building Accumulo</h1>
           
-          <p>The Apache Software Foundation provides an <a href="https://reviews.apache.org">instance</a> of
-<a href="https://www.reviewboard.org">Review Board</a> (RB) for projects to use in code reviews. Here is how RB can
-be used to support development in the context of the
-<a href="/contributor/bylaws">Apache Accumulo bylaws</a>.</p>
-
-<p>Contributors to Accumulo are encouraged to use RB for non-trivial patches and
-any time feedback is desired. No one is required to use RB, but its ready
-availability and better interface for feedback can help with reviews. Committers
-seeking review prior to pushing changes can also benefit similarly. It should
-be noted that more recently the use of GitHub has been overtaking the use of 
-Review Board for code reviews.</p>
-
-<h2 id="roles-for-review-board">Roles for Review Board</h2>
-
-<h3 id="optional-pre-commit-review">Optional Pre-Commit Review</h3>
-
-<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so code
-review does not need to occur prior to commit. However, a committer may opt to
-hold a code review before commit for changes that, in their opinion, would
-benefit from additional attention. RB can be used to conduct such code reviews.</p>
-
-<h3 id="consensus-approval-after-a-code-change-veto">Consensus Approval after a Code Change Veto</h3>
-
-<p>Code changes are approved by lazy approval, with consensus approval following
-a veto (see the <a href="/contributor/bylaws#actions">Actions</a> section of the bylaws). RB can be used
-to coordinate a consensus approval vote by providing a convenient view of the
-code change under consideration. The vote itself must still be held on the
-developer mailing list.</p>
-
-<h2 id="guidelines-for-posting-a-review">Guidelines for Posting a Review</h2>
-
-<ul>
-  <li>It is best to post a git-generated patch as the basis for a review. RB does
-not support patches containing multiple commits, so either squash commits
-first, or submit a diff spanning the changeset. The <code class="highlighter-rouge">rbt</code> and <code class="highlighter-rouge">post-review</code>
-tools generate diffs.</li>
-  <li>Strive to make your changes small. Reviewers are less likely to want to
-trudge through a review with lots of changes, and are more likely to miss
-problems.</li>
-  <li>Begin the summary of the review with a JIRA issue number. A review must
-always be associated with a JIRA issue. The issue number should also be
-entered in the “Bugs” field of the review, providing a link to JIRA.</li>
-  <li>The “Branch” field should contain the name of the branch that the code change
-is based on (e.g., the base of your git feature branch).</li>
-  <li>Include the “accumulo” user group as reviewers. Also include specific people
-as individual reviewers, even if they are in the “accumulo” group, if you
-deem them of primary importance for the review (e.g., you have been working
-out problems with the review with them, they are expert in the area).</li>
-  <li>Use the description to summarize the change under review. Include helpful
-instructions to the reviewers here.</li>
-  <li>Describe any testing done on the change. It is not expected that reviewers
-will do their own testing, and they may reject the review if you have not
-done sufficient testing yourself.</li>
-  <li>Avoid submitting generated code for review if it can be reproduced by a
-reviewer.</li>
-</ul>
-
-<p>After the review is published, set the status of the associated JIRA issue to
-“Patch Available” as a signal to reviewers. Also, link to the review from the
-issue (More -&gt; Link -&gt; Web Link) to help viewers of the issue find the review
-and assess its progress.</p>
-
-<h2 id="guidelines-for-reviewing-code">Guidelines for Reviewing Code</h2>
-
-<ul>
-  <li>Try to associate comments with relevant lines of code in the review.</li>
-  <li>By default, each comment opens a review issue. If a comment pertains to
-something that should not block the review from completing successfully, then
-clear the “Open an issue” checkbox before saving your feedback. Examples that
-might qualify as non-issues: minor formatting/whitespace issues, spelling
-mistakes, general background questions.</li>
-  <li>If a review looks good, be sure to “Ship It” by either using the “Ship It!”
-button or by submitting a general review with the “Ship It” checkbox checked.</li>
-</ul>
-
-<h2 id="guidelines-for-completing-a-review">Guidelines for Completing a Review</h2>
-
-<p>These guidelines do not apply to consensus approval votes, since the vote
-completion depends on the votes registered in the developer mailing list.</p>
-
-<ul>
-  <li>Use your judgement for the number of “Ship It”s you want to receive to
-consider a review passed. Usually, getting one “Ship It” is enough to proceed
-with a commit. It is recommended that the “Ship It” be from a committer who
-is a neutral party not involved in the change under review.</li>
-  <li>Use your judgement for the minimum time length you set for the review. Simple
-changes can be up for just a day, while complex ones should take up to seven.</li>
-  <li>Review time should be extended in the face of problems discovered in the
-review. Update the review with improved code instead of discarding (i.e.,
-closing unsuccessfully) it and beginning a new one.</li>
-  <li>A review should not be “submitted” (i.e., closed successfully) unless there
-are no outstanding issues. Check with reviewers to ensure that their issues
-are resolved satisfactorily.</li>
-  <li>A review should be “discarded” if the code requires major rework or it
-becomes obvious it should never be committed (due to design changes,
-becoming overcome by events, being back-burnered, etc.).</li>
-  <li>Don’t leave a review open indefinitely. Once you have received sufficient
-feedback to submit or discard it, do so. If there has been no activity for
-some time, discard the review. A new one can always be created later.</li>
-</ul>
-
-<p>Once you’ve closed a review as submitted, if you are unable to commit your
-changes yourself, attach the final version of them to the relevant JIRA issue.
-They should be in the form of a patch containing a single commit,
-<a href="/contributor/git#contributors">per the final steps of the contribution process</a>.</p>
+          <h3 id="installing-apache-thrift">Installing Apache Thrift</h3>
+
+<p>If you activate the ‘thrift’ Maven profile, the build of some modules will attempt to run the Apache Thrift command line to regenerate
+stubs. If you activate this profile and don’t have Apache Thrift installed and in your path, you will see a warning and
+your build will fail. For Accumulo 1.5.0 and greater, install Thrift 0.9 and make sure that the ‘thrift’ command is in your path. 
+Watch out for THRIFT-1367; you may need to configure Thrift with –without-ruby. Most developers do not
+need to install or modify the Thrift definitions as a part of developing against Apache Accumulo.</p>
+
+<h3 id="running-a-build">Running a Build</h3>
+
+<p>Accumulo uses <a href="https://maven.apache.org">Apache Maven</a> to handle source building, testing, and packaging. To build Accumulo, you will need to use Maven version 3.0.5 or later.</p>
+
+<p>You should familiarize yourself with the <a href="https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle">Maven Build Lifecycle</a>, as well as the various plugins we use in our <a href="https://gitbox.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=pom.xml;hb=HEAD">POM</a>, in order to understand how Maven works and how to use the various build options while building Accumulo.</p>
+
+<p>To build from source (for example, to deploy):</p>
+
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn package -Passemble
+</code></pre></div></div>
+
+<p>This will create a file <code class="highlighter-rouge">accumulo-*-SNAPSHOT-dist.tar.gz</code> in the assemble/target directory. Optionally, append <code class="highlighter-rouge">-DskipTests</code> if you want to skip the build tests.</p>
+
+<p>To build your branch before submitting a pull request, you’ll probably want to run some basic “sunny-day” integration tests to ensure you haven’t made any grave errors, as well as <code class="highlighter-rouge">checkstyle</code> and <code class="highlighter-rouge">findbugs</code>:</p>
+
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn verify -Psunny
+</code></pre></div></div>
+
+<p>To run specific unit tests, you can run:</p>
+
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn package -Dtest=MyTest -DfailIfNoTests=false
+</code></pre></div></div>
+
+<p>Or to run the specific integration tests MyIT and YourIT (and skip all unit tests), you can run:</p>
+
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn verify -Dtest=NoSuchTestExists -Dit.test=MyIT,YourIT -DfailIfNoTests=false
+</code></pre></div></div>
+
+<p>There are plenty of other options. For example, you can skip findbugs with <code class="highlighter-rouge">mvn verify -Dfindbugs.skip</code> or checkstyle <code class="highlighter-rouge">-Dcheckstyle.skip</code>, or control the number of forks to use while executing tests, <code class="highlighter-rouge">-DforkCount=4</code>, etc. You should check with specific plugins to see which command-line options are available to control their behavior. Note that not all options will result in a [...]
+
+<p>If you regularly switch between major development branches, you may receive errors about improperly licensed files from the <a href="https://creadur.apache.org/rat/apache-rat-plugin">RAT plugin</a>. This is caused by modules that exist in one branch and not the other leaving Maven build files that the RAT plugin no longer understands how to ignore.</p>
+
+<p>The easiest fix is to ensure all of your current changes are stored in git and then cleaning your workspace.</p>
+
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$&gt; git add path/to/file/that/has/changed
+$&gt; git add path/to/other/file
+$&gt; git clean -df
+</code></pre></div></div>
+
+<p>Note that this git clean command will delete any files unknown to git in a way that is irreversible. You should check that no important files will be included by first looking at the “untracked files” section in a <code class="highlighter-rouge">git status</code> command.</p>
+
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$&gt; git status
+# On branch master
+nothing to commit (working directory clean)
+$&gt; mvn package
+{ maven output elided }
+$&gt; git checkout 1.6.1-SNAPSHOT
+Switched to branch '1.6.1-SNAPSHOT'
+$&gt; git status
+# On branch 1.6.1-SNAPSHOT
+# Untracked files:
+#   (use "git add &lt;file&gt;..." to include in what will be committed)
+#
+# mapreduce/
+# shell/
+nothing added to commit but untracked files present (use "git add" to track)
+$&gt; git clean -df
+Removing mapreduce/
+Removing shell/
+$&gt; git status
+# On branch 1.6.1-SNAPSHOT
+nothing to commit (working directory clean)
+</code></pre></div></div>
 
 
         </div>
diff --git a/contributor/rb.html b/contributor/testing-release.html
similarity index 54%
rename from contributor/rb.html
rename to contributor/testing-release.html
index 2809d22..3ca36e7 100644
--- a/contributor/rb.html
+++ b/contributor/testing-release.html
@@ -25,7 +25,7 @@
 <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/v/bs/jq-2.2.3/dt-1.10.12/datatables.min.css">
 <link href="/css/accumulo.css" rel="stylesheet" type="text/css">
 
-<title>Using Review Board</title>
+<title>Testing a release</title>
 
 <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"></script>
 <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script>
@@ -136,113 +136,60 @@
         </div>
         <div id="content">
           
-          <h1 class="title">Using Review Board</h1>
+          <h1 class="title">Testing a release</h1>
           
-          <p>The Apache Software Foundation provides an <a href="https://reviews.apache.org">instance</a> of
-<a href="https://www.reviewboard.org">Review Board</a> (RB) for projects to use in code reviews. Here is how RB can
-be used to support development in the context of the
-<a href="/contributor/bylaws">Apache Accumulo bylaws</a>.</p>
-
-<p>Contributors to Accumulo are encouraged to use RB for non-trivial patches and
-any time feedback is desired. No one is required to use RB, but its ready
-availability and better interface for feedback can help with reviews. Committers
-seeking review prior to pushing changes can also benefit similarly. It should
-be noted that more recently the use of GitHub has been overtaking the use of 
-Review Board for code reviews.</p>
-
-<h2 id="roles-for-review-board">Roles for Review Board</h2>
-
-<h3 id="optional-pre-commit-review">Optional Pre-Commit Review</h3>
-
-<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so code
-review does not need to occur prior to commit. However, a committer may opt to
-hold a code review before commit for changes that, in their opinion, would
-benefit from additional attention. RB can be used to conduct such code reviews.</p>
-
-<h3 id="consensus-approval-after-a-code-change-veto">Consensus Approval after a Code Change Veto</h3>
-
-<p>Code changes are approved by lazy approval, with consensus approval following
-a veto (see the <a href="/contributor/bylaws#actions">Actions</a> section of the bylaws). RB can be used
-to coordinate a consensus approval vote by providing a convenient view of the
-code change under consideration. The vote itself must still be held on the
-developer mailing list.</p>
-
-<h2 id="guidelines-for-posting-a-review">Guidelines for Posting a Review</h2>
-
-<ul>
-  <li>It is best to post a git-generated patch as the basis for a review. RB does
-not support patches containing multiple commits, so either squash commits
-first, or submit a diff spanning the changeset. The <code class="highlighter-rouge">rbt</code> and <code class="highlighter-rouge">post-review</code>
-tools generate diffs.</li>
-  <li>Strive to make your changes small. Reviewers are less likely to want to
-trudge through a review with lots of changes, and are more likely to miss
-problems.</li>
-  <li>Begin the summary of the review with a JIRA issue number. A review must
-always be associated with a JIRA issue. The issue number should also be
-entered in the “Bugs” field of the review, providing a link to JIRA.</li>
-  <li>The “Branch” field should contain the name of the branch that the code change
-is based on (e.g., the base of your git feature branch).</li>
-  <li>Include the “accumulo” user group as reviewers. Also include specific people
-as individual reviewers, even if they are in the “accumulo” group, if you
-deem them of primary importance for the review (e.g., you have been working
-out problems with the review with them, they are expert in the area).</li>
-  <li>Use the description to summarize the change under review. Include helpful
-instructions to the reviewers here.</li>
-  <li>Describe any testing done on the change. It is not expected that reviewers
-will do their own testing, and they may reject the review if you have not
-done sufficient testing yourself.</li>
-  <li>Avoid submitting generated code for review if it can be reproduced by a
-reviewer.</li>
-</ul>
-
-<p>After the review is published, set the status of the associated JIRA issue to
-“Patch Available” as a signal to reviewers. Also, link to the review from the
-issue (More -&gt; Link -&gt; Web Link) to help viewers of the issue find the review
-and assess its progress.</p>
-
-<h2 id="guidelines-for-reviewing-code">Guidelines for Reviewing Code</h2>
-
-<ul>
-  <li>Try to associate comments with relevant lines of code in the review.</li>
-  <li>By default, each comment opens a review issue. If a comment pertains to
-something that should not block the review from completing successfully, then
-clear the “Open an issue” checkbox before saving your feedback. Examples that
-might qualify as non-issues: minor formatting/whitespace issues, spelling
-mistakes, general background questions.</li>
-  <li>If a review looks good, be sure to “Ship It” by either using the “Ship It!”
-button or by submitting a general review with the “Ship It” checkbox checked.</li>
-</ul>
-
-<h2 id="guidelines-for-completing-a-review">Guidelines for Completing a Review</h2>
-
-<p>These guidelines do not apply to consensus approval votes, since the vote
-completion depends on the votes registered in the developer mailing list.</p>
-
-<ul>
-  <li>Use your judgement for the number of “Ship It”s you want to receive to
-consider a review passed. Usually, getting one “Ship It” is enough to proceed
-with a commit. It is recommended that the “Ship It” be from a committer who
-is a neutral party not involved in the change under review.</li>
-  <li>Use your judgement for the minimum time length you set for the review. Simple
-changes can be up for just a day, while complex ones should take up to seven.</li>
-  <li>Review time should be extended in the face of problems discovered in the
-review. Update the review with improved code instead of discarding (i.e.,
-closing unsuccessfully) it and beginning a new one.</li>
-  <li>A review should not be “submitted” (i.e., closed successfully) unless there
-are no outstanding issues. Check with reviewers to ensure that their issues
-are resolved satisfactorily.</li>
-  <li>A review should be “discarded” if the code requires major rework or it
-becomes obvious it should never be committed (due to design changes,
-becoming overcome by events, being back-burnered, etc.).</li>
-  <li>Don’t leave a review open indefinitely. Once you have received sufficient
-feedback to submit or discard it, do so. If there has been no activity for
-some time, discard the review. A new one can always be created later.</li>
-</ul>
-
-<p>Once you’ve closed a review as submitted, if you are unable to commit your
-changes yourself, attach the final version of them to the relevant JIRA issue.
-They should be in the form of a patch containing a single commit,
-<a href="/contributor/git#contributors">per the final steps of the contribution process</a>.</p>
+          <h2 id="test-a-accumulo-release">Test a Accumulo release</h2>
+
+<ol>
+  <li>Set the release version, ID for staging repo, and alias to configure Maven with temporary settings:
+    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">export </span><span class="nv">RC_VERSION</span><span class="o">=</span>1.9.0
+<span class="nb">export </span><span class="nv">RC_STAGING</span><span class="o">=</span>1070
+</code></pre></div>    </div>
+  </li>
+  <li>Create temporary Maven settings
+    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">cat</span> <span class="o">&lt;&lt;</span><span class="no">EOF</span><span class="sh"> &gt;/tmp/accumulo-rc-maven.xml
+&lt;settings&gt;
+  &lt;profiles&gt;
+    &lt;profile&gt;
+      &lt;id&gt;accumuloRC&lt;/id&gt;
+      &lt;repositories&gt;
+        &lt;repository&gt;
+          &lt;id&gt;accumulorc&lt;/id&gt;
+          &lt;name&gt;accumulorc&lt;/name&gt;
+          &lt;url&gt;https://repository.apache.org/content/repositories/orgapacheaccumulo-\</span><span class="k">${</span><span class="nv">env</span><span class="p">.RC_STAGING</span><span class="k">}</span><span class="sh">/&lt;/url&gt;
+        &lt;/repository&gt;
+      &lt;/repositories&gt;
+      &lt;pluginRepositories&gt;
+        &lt;pluginRepository&gt;
+          &lt;id&gt;accumulorcp&lt;/id&gt;
+          &lt;name&gt;accumulorcp&lt;/name&gt;
+          &lt;url&gt;https://repository.apache.org/content/repositories/orgapacheaccumulo-\</span><span class="k">${</span><span class="nv">env</span><span class="p">.RC_STAGING</span><span class="k">}</span><span class="sh">/&lt;/url&gt;
+        &lt;/pluginRepository&gt;
+      &lt;/pluginRepositories&gt;
+    &lt;/profile&gt;
+  &lt;/profiles&gt;
+  &lt;activeProfiles&gt;
+    &lt;activeProfile&gt;accumuloRC&lt;/activeProfile&gt;
+  &lt;/activeProfiles&gt;
+&lt;/settings&gt;
+</span><span class="no">EOF
+</span></code></pre></div>    </div>
+    <h4 id="run-the-integration-tests-of-projects-that-use-accumulo">Run the integration tests of projects that use Accumulo</h4>
+  </li>
+  <li>Clone the <a href="https://github.com/apache/accumulo-examples">Accumulo Examples</a> project:
+    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="nv">$ </span>git clone https://github.com/apache/accumulo-examples.git
+</code></pre></div>    </div>
+  </li>
+  <li>Run the integration test
+    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="nv">$ </span>mvn <span class="nt">-s</span> /tmp/accumulo-rc-maven.xml clean verify <span class="nt">-Daccumulo</span>.version<span class="o">=</span><span class="nv">$RC_VERSION</span>
+</code></pre></div>    </div>
+    <p>Below are more projects with integration tests:</p>
+    <ul>
+      <li><a href="https://github.com/apache/accumulo-wikisearch">Wikisearch</a> - <code class="highlighter-rouge">https://github.com/apache/accumulo-wikisearch</code></li>
+      <li><a href="https://github.com/apache/fluo">Apache Fluo</a> - <code class="highlighter-rouge">https://github.com/apache/fluo</code></li>
+    </ul>
+  </li>
+</ol>
 
 
         </div>
diff --git a/contributors-guide/index.html b/contributors-guide/index.html
index dfffa1f..25ba437 100644
--- a/contributors-guide/index.html
+++ b/contributors-guide/index.html
@@ -138,669 +138,27 @@
           
           <h1 class="title">Contributor Guide</h1>
           
-          <p>This page contains resources and documentation of interest to current and potential contributors to the Accumulo project. Any documentation that is helpful to Accumulo users should go in the <a href="/1.9/accumulo_user_manual.html">Accumulo User Manual</a>.</p>
+          <p><strong>Please read the <a href="/how-to-contribute/">How to Contribute</a> page first before reading this guide.</strong> This page contains additional project
+documentation.</p>
 
-<p>If your are interested in quickly getting an Accumulo instance up and running, see the Accumulo Quickstart guides <a href="/quickstart-1.x/">(1.x)</a>/<a href="/quickstart-2.x/">(2.x)</a> or refer to the <a href="https://github.com/apache/fluo-uno">Uno</a> project on Github.</p>
+<h2 id="for-contributors">For Contributors</h2>
+
+<p>The docs below provide additional information for contributors.</p>
 
 <ul>
-  <li><a href="#how-to-contribute-to-apache-accumulo">How to contribute to Apache Accumulo</a></li>
-  <li><a href="#project-resources">Project Resources</a>
-    <ul>
-      <li><a href="#github">GitHub</a></li>
-      <li><a href="#jira">JIRA</a></li>
-      <li><a href="#jenkinstravisci">Jenkins/TravisCI</a></li>
-    </ul>
-  </li>
-  <li><a href="#create-a-ticket-for-new-bugs-or-feature">Create a Ticket for Bugs or New Features</a></li>
-  <li><a href="#building-accumulo-from-source">Building Accumulo from Source</a>
-    <ul>
-      <li><a href="#installing-apache-thrift">Installing Apache Thrift</a></li>
-      <li><a href="#checking-out-from-git">Checking out from Git</a></li>
-      <li><a href="#running-a-build">Running a Build</a></li>
-    </ul>
-  </li>
-  <li><a href="#providing-a-contribution">Providing a contribution</a>
-    <ul>
-      <li><a href="#proposed-workflow">Proposed Workflow</a></li>
-      <li><a href="#the-implementation">The Implementation</a>
-        <ul>
-          <li><a href="#contributors">Contributors</a></li>
-          <li><a href="#developers">Developers</a>
-            <ul>
-              <li><a href="#primary-development">Primary Development</a></li>
-              <li><a href="#reviewing-contributor-changes">Reviewing Contributor Changes</a></li>
-              <li><a href="#submit-contribution-via-patch">Submit Contribution via Patch</a></li>
-              <li><a href="#submit-contribution-via-pull-request">Submit Contribution via Pull Request</a></li>
-              <li><a href="#feature-branches">Feature Branches</a></li>
-              <li><a href="#changes-which-affect-multiple-versions-aka-merging">Changes Which Affect Multiple-Versions (a.k.a Merging)</a></li>
-            </ul>
-          </li>
-        </ul>
-      </li>
-    </ul>
-  </li>
-  <li><a href="#code-review-process">Code Review Process</a></li>
-  <li><a href="#additional-contributor-information">Additional Contributor Information</a>
-    <ul>
-      <li><a href="#coding-practices">Coding Practices</a></li>
-      <li><a href="#merging-practices">Merging Practices</a></li>
-      <li><a href="#project-examples">Project Examples</a></li>
-      <li><a href="#website-contributions">Website Contributions</a></li>
-      <li><a href="#public-api">Public API</a></li>
-      <li><a href="/contributor/contrib-projects">Contrib Projects</a></li>
-    </ul>
-  </li>
-  <li><a href="#committer-documentation">Committer Documentation</a></li>
-  <li><a href="#project-governance">Project Governance</a></li>
+  <li><a href="/contributor/building">Building Accumulo</a></li>
+  <li><a href="/contributor/advanced-contributor">Advanced Contributor</a></li>
 </ul>
 
-<h2 id="how-to-contribute-to-apache-accumulo">How to Contribute to Apache Accumulo</h2>
-
-<p>Apache Accumulo welcomes contributions from the community. This is especially true of new contributors! You don’t need to be a software developer to contribute to Apache Accumulo. So, if you want to get involved in Apache Accumulo, there is almost certainly a role for you. View our <a href="/how-to-contribute/">How to Contribute</a> page for additional details on the many opportunities available.</p>
-
-<h2 id="project-resources">Project Resources</h2>
-
-<p>Accumulo makes use of the following external tools for development.</p>
-
-<h3 id="github">GitHub</h3>
-
-<p>Apache Accumulo® source code is maintained using <a href="https://git-scm.com/">Git</a> version control and mirrored to <a href="https://github.com/apache/accumulo">GitHub</a>. Source files can be browsed <a href="https://gitbox.apache.org/repos/asf?p=accumulo.git;a=summary">here</a> or at the <a href="https://github.com/apache/accumulo">GitHub mirror</a>.</p>
-
-<p>The project code can be checked-out <a href="https://github.com/apache/accumulo">here</a>. It builds with <a href="https://maven.apache.org">Apache Maven</a>.</p>
-
-<h3 id="jira">JIRA</h3>
-
-<p>Accumulo <a href="https://issues.apache.org/jira/browse/ACCUMULO">tracks issues</a> with <a href="https://www.atlassian.com/software/jira">JIRA</a>. Prospective code contributors can view <a href="https://s.apache.org/newbie_accumulo_tickets">open issues labeled for “newbies”</a> to search for starter tickets. Note that every commit should reference a JIRA ticket of the form ACCUMULO-#.</p>
-
-<h3 id="jenkinstravisci">Jenkins/TravisCI</h3>
-
-<p>Accumulo uses <a href="https://builds.apache.org/view/A/view/Accumulo">Jenkins</a> and <a href="https://travis-ci.org/apache/accumulo">TravisCI</a> for automatic builds and continuous integration.</p>
-
-<h2 id="create-a-ticket-for-new-bugs-or-feature">Create a Ticket for New Bugs or Feature</h2>
-
-<p>If you run into a bug or think there is something that would benefit the project, we encourage you to file an issue at the <a href="https://issues.apache.org/jira/browse/ACCUMULO">Apache Accumulo JIRA</a> page. Regardless of whether you have the time to provide the fix or implementation yourself, this will be helpful to the project.</p>
-
-<h2 id="building-accumulo-from-source">Building Accumulo from Source</h2>
-
-<h3 id="installing-apache-thrift">Installing Apache Thrift</h3>
-
-<p>If you activate the ‘thrift’ Maven profile, the build of some modules will attempt to run the Apache Thrift command line to regenerate
-stubs. If you activate this profile and don’t have Apache Thrift installed and in your path, you will see a warning and
-your build will fail. For Accumulo 1.5.0 and greater, install Thrift 0.9 and make sure that the ‘thrift’ command is in your path. 
-Watch out for THRIFT-1367; you may need to configure Thrift with –without-ruby. Most developers do not
-need to install or modify the Thrift definitions as a part of developing against Apache Accumulo.</p>
-
-<h3 id="checking-out-from-git">Checking out from Git</h3>
-
-<p>There are several methods for obtaining the Accumulo source code. If you prefer to use SSH rather than HTTPS you can refer to the <a href="https://help.github.com/">GitHub help pages</a> for help in creating a GitHub account and setting up <a href="https://help.github.com/articles/connecting-to-github-with-ssh/">SSH keys</a>.</p>
-
-<h4 id="--from-your-github-fork">- from your Github Fork</h4>
-
-<p>It is also possible to <a href="https://help.github.com/articles/fork-a-repo/">fork</a> a repository in GitHub so that you can freely experiment with changes without affecting the original project. You can then submit a <a href="https://help.github.com/articles/about-pull-requests/">pull request</a> from your personal fork to the project repository when you wish to supply a contribution.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone git@github.com:&lt;account name&gt;/accumulo.git
-</code></pre></div></div>
-
-<h5 id="retrieval-of-upstream-changes">Retrieval of upstream changes</h5>
-
-<p>Additionally, it is beneficial to add a git remote for the mirror to allow the retrieval of upstream changes.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add upstream http://github.com/apache/accumulo.git
-</code></pre></div></div>
-
-<h4 id="--from-the-github-mirror">- from the Github Mirror</h4>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/apache/accumulo.git
-</code></pre></div></div>
-
-<h4 id="--from-the-apache-hosted-repository">- from the Apache Hosted Repository</h4>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://gitbox.apache.org/repos/asf/accumulo.git
-</code></pre></div></div>
-
-<h2 id="running-a-build">Running a Build</h2>
-
-<p>Accumulo uses <a href="https://maven.apache.org">Apache Maven</a> to handle source building, testing, and packaging. To build Accumulo, you will need to use Maven version 3.0.5 or later.</p>
-
-<p>You should familiarize yourself with the <a href="https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle">Maven Build Lifecycle</a>, as well as the various plugins we use in our <a href="https://gitbox.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=pom.xml;hb=HEAD">POM</a>, in order to understand how Maven works and how to use the various build options while building Accumulo.</p>
-
-<p>To build from source (for example, to deploy):</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn package -Passemble
-</code></pre></div></div>
-
-<p>This will create a file <code class="highlighter-rouge">accumulo-*-SNAPSHOT-dist.tar.gz</code> in the assemble/target directory. Optionally, append <code class="highlighter-rouge">-DskipTests</code> if you want to skip the build tests.</p>
-
-<p>To build your branch before submitting a pull request, you’ll probably want to run some basic “sunny-day” integration tests to ensure you haven’t made any grave errors, as well as <code class="highlighter-rouge">checkstyle</code> and <code class="highlighter-rouge">findbugs</code>:</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn verify -Psunny
-</code></pre></div></div>
-
-<p>To run specific unit tests, you can run:</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn package -Dtest=MyTest -DfailIfNoTests=false
-</code></pre></div></div>
-
-<p>Or to run the specific integration tests MyIT and YourIT (and skip all unit tests), you can run:</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mvn verify -Dtest=NoSuchTestExists -Dit.test=MyIT,YourIT -DfailIfNoTests=false
-</code></pre></div></div>
-
-<p>There are plenty of other options. For example, you can skip findbugs with <code class="highlighter-rouge">mvn verify -Dfindbugs.skip</code> or checkstyle <code class="highlighter-rouge">-Dcheckstyle.skip</code>, or control the number of forks to use while executing tests, <code class="highlighter-rouge">-DforkCount=4</code>, etc. You should check with specific plugins to see which command-line options are available to control their behavior. Note that not all options will result in a [...]
-
-<p>If you regularly switch between major development branches, you may receive errors about improperly licensed files from the <a href="https://creadur.apache.org/rat/apache-rat-plugin">RAT plugin</a>. This is caused by modules that exist in one branch and not the other leaving Maven build files that the RAT plugin no longer understands how to ignore.</p>
-
-<p>The easiest fix is to ensure all of your current changes are stored in git and then cleaning your workspace.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$&gt; git add path/to/file/that/has/changed
-$&gt; git add path/to/other/file
-$&gt; git clean -df
-</code></pre></div></div>
-
-<p>Note that this git clean command will delete any files unknown to git in a way that is irreversible. You should check that no important files will be included by first looking at the “untracked files” section in a <code class="highlighter-rouge">git status</code> command.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$&gt; git status
-# On branch master
-nothing to commit (working directory clean)
-$&gt; mvn package
-{ maven output elided }
-$&gt; git checkout 1.6.1-SNAPSHOT
-Switched to branch '1.6.1-SNAPSHOT'
-$&gt; git status
-# On branch 1.6.1-SNAPSHOT
-# Untracked files:
-#   (use "git add &lt;file&gt;..." to include in what will be committed)
-#
-# mapreduce/
-# shell/
-nothing added to commit but untracked files present (use "git add" to track)
-$&gt; git clean -df
-Removing mapreduce/
-Removing shell/
-$&gt; git status
-# On branch 1.6.1-SNAPSHOT
-nothing to commit (working directory clean)
-</code></pre></div></div>
-
-<h2 id="providing-a-contribution">Providing a Contribution</h2>
-
-<p>The Accumulo source is hosted at <a href="https://gitbox.apache.org/repos/asf?p=accumulo.git;a=summary">https://gitbox.apache.org/</a> .</p>
-
-<p>Like all Apache projects, a mirror of the git repository is also located on GitHub at <a href="https://github.com/apache/accumulo">https://github.com/apache/accumulo</a> which provides ease in <a href="https://help.github.com/articles/fork-a-repo/">forking</a> and generating <a href="https://help.github.com/articles/using-pull-requests/">pull requests (PRs)</a>.</p>
-
-<h3 id="git">Git</h3>
-
-<p><a href="https://git-scm.com/">Git</a> is an open source, distributed version control system
-which has become very popular in large, complicated software projects due to
-its efficient handling of multiple, simultaneously and independently developed
-branches of source code.</p>
-
-<h3 id="workflow-background">Workflow Background</h3>
-
-<p>The most likely contested subject matter regarding switching an active team
-from one SCM tool to another is a shift in the development paradigm.</p>
-
-<p>Some background, the common case, as is present with this team, is that
-developers coming from a Subversion history are very light on merging being a
-critical consideration on how to perform development. Because merging in
-Subversion is typically of no consequence to the complete view of history, not
-to mention that Subversion allows “merging” of specific revisions instead of
-sub-trees. As such, a transition to Git typically requires a shift in mindset
-in which a fix is not arbitrarily applied to trunk (whatever the main
-development is called), but the fix should be applied to the earliest, non
-end-of-life (EOL) version of the application.</p>
-
-<p>For example, say there is a hypothetical application which has just released
-version-3 of their software and have shifted their development to a version-4
-WIP. Version-2 is still supported, while version-1 was just EOL’ed. Each
-version still has a branch. A bug was just found which affects all released
-versions of this application. In Subversion, considering the history in the
-repository, it is of no consequence where the change is initially applied,
-because a Subversion merge is capable of merging it to any other version.
-History does not suffer because Subversion doesn’t have the capacities to
-accurately track the change across multiple branches. In Git, to maintain a
-non-duplicative history, it is imperative that the developer choose the correct
-branch to fix the bug in. In this case, since version-1 is EOL’ed, version-2,
-version-3 and the WIP version-4 are candidates. The earliest version is
-obviously version-2; so, the change should be applied in version-2, merged to
-version-3 and then the version-4 WIP.</p>
-
-<p>The importance of this example is making a best-attempt to preserve history
-when using Git. While Git does have commands like cherry-pick which allow the
-contents of a commit to be applied from one branch to another which are not
-candidates to merge without conflict (which is typically the case when merging
-a higher version into a lower version), this results in a duplication of that
-commit in history when the two trees are eventually merged together. While Git
-is smart enough to not attempt to re-apply the changes, history still contains
-the blemish.</p>
-
-<p>The purpose of this extravagant example is to outline, in the trivial case, how
-the workflow decided upon for development is very important and has direct
-impact on the efficacy of the advanced commands bundled with Git.</p>
-
-<h3 id="proposed-workflow">Proposed Workflow</h3>
-
-<p>This is a summary of what has been agreed upon by vocal committers/PMC members
-on <a href="mailto:dev@accumulo.apache.org">dev@accumulo.apache.org</a>. Enumeration of
-every possible situation out of the scope of this document. This document
-intends to lay the ground work to define the correct course of action regardless
-of circumstances. Some concrete examples will be provided to ensure the
-explanation is clear.</p>
-
-<ol>
-  <li>
-    <p>Active development is performed concurrently over no less than two versions
-of Apache Accumulo at any one point in time. As such, the workflow must
-provide guidance on how and where changes should be made which apply to
-multiple versions and how to ensure that such changes are contained in all
-applicable versions.</p>
-  </li>
-  <li>
-    <p>Releases are considered extremely onerous and time-consuming so no emphasis
-is placed on rapid iterations or development-cycles.</p>
-  </li>
-  <li>
-    <p>New features typically have lengthy development cycles in which more than
-one developer contributes to the creation of the new feature from planning,
-to implementation, to scale testing. Mechanisms/guidance should be provided
-for multiple developers to teach contribute to a remote-shared resource.</p>
-  </li>
-  <li>
-    <p>The repository should be the irrefutable, sole source of information
-regarding the development of Apache Accumulo, and, as such, should have
-best-efforts given in creating a clean, readable history without any single
-entity having to control all write access and changes (a proxy). In other
-words, the developers are the ones responsible for ensuring that previous
-releases are preserved to meet ASF policy, for not rewriting any public
-history of code not yet officially released (also ASF policy relevant) and
-for a best-effort to be given to avoid duplicative commits appearing in
- history created by the application of multiple revisions which have
- different identifying attributes but the same contents (git-rebase and
- git-cherry-pick).</p>
-  </li>
-</ol>
-
-<h2 id="the-implementation">The Implementation</h2>
-
-<p>The following steps, originally derived from Apache kafka’s 
-<a href="https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review#Patchsubmissionandreview-Simplecontributorworkflow">simple contributor workflow</a>, will demonstrate the gitflow implementation.</p>
-
-<h3 id="contributors">Contributors</h3>
-
-<p>To be specific, let’s consider a contributor wanting to work on a fix for the
-Jira issue ACCUMULO-12345 that affects the 1.9 release.</p>
-
-<ol>
-  <li>
-    <p>Ensure you configured Git with your information</p>
-
-    <p><code class="highlighter-rouge">git config --global user.name 'My Name' &amp;&amp; git config --global user.email
- 'myname@mydomain.com'</code></p>
-  </li>
-  <li>
-    <p>Clone the Accumulo repository:</p>
-
-    <p><code class="highlighter-rouge">git clone https://gitbox.apache.org/repos/asf/accumulo.git accumulo</code></p>
-  </li>
-  <li>
-    <p>or update your local copy:</p>
-
-    <p><code class="highlighter-rouge">git fetch &amp;&amp; git fetch --tags</code></p>
-  </li>
-  <li>
-    <p>For the given issue you intend to work on, choose the ‘lowest’ fixVersion
-and create a branch for yourself to work in. This example is against the next release of 1.9</p>
-
-    <p><code class="highlighter-rouge">git checkout -b ACCUMULO-12345-my-work origin/1.9</code></p>
-  </li>
-  <li>
-    <p>Make commits as you see fit as you fix the issue, referencing the issue name
-in the commit message:</p>
-
-    <p><code class="highlighter-rouge">git commit -av</code></p>
-
-    <p>Please include the ticket number at the beginning of the log message, and
- in the first line, as it’s easier to parse quickly. For example:</p>
-
-    <p><code class="highlighter-rouge">ACCUMULO-2428 throw exception when rename fails after compaction</code></p>
-
-    <p>Consider following the git log message format described in
- <a href="https://zachholman.com/talk/more-git-and-github-secrets/">Zach Holman’s talk</a>
- (specifically slides 78-98, beginning at 15:20 into the video). Essentially,
- leave a short descriptive message in the first line, skip a line, and write
- more detailed stuff there, if you need to. For example:</p>
-  </li>
-</ol>
+<h2 id="for-committers">For Committers</h2>
 
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>    ACCUMULO-2194 Add delay for randomwalk Security teardown
-
-    If two Security randomwalk tests run back-to-back, the second test may see that the
-    table user still exists even though it was removed when the first test was torn down.
-    This can happen if the user drop does not propagate through Zookeeper quickly enough.
-    This commit adds a delay to the end of the Security test to give ZK some time.
-</code></pre></div></div>
-
-<ol>
-  <li>
-    <p>Assuming others are developing against the version you also are, as you
-work, or before you create your patch, rebase your branch against the remote
-to lift your changes to the top of your branch. The branch specified here should be the same one you used in step 4.</p>
-
-    <p><code class="highlighter-rouge">git pull --rebase origin 1.9</code></p>
-  </li>
-  <li>
-    <p>At this point, you can create a patch file from the upstream branch to
-attach to the ACCUMULO-12345 Jira issue. The branch specified here should be the same one you used in step 4.</p>
-
-    <p><code class="highlighter-rouge">git format-patch --stdout origin/1.9 &gt; ACCUMULO-12345.patch</code></p>
-  </li>
-</ol>
-
-<p>An alternative to creating a patch is submitting a request to pull your changes
-from some repository, e.g. GitHub. Please include the repository and branch
-name merge in the notice to the Jira issue, e.g.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>repo=git://github.com/&lt;username&gt;/accumulo.git branch=ACCUMULO-12345
-</code></pre></div></div>
-
-<p>A second alternative is to use Github’s “Pull Requests” feature against the
-<a href="https://github.com/apache/accumulo">Apache Accumulo account</a>. Notifications of
-new pull-requests from Github should automatically be sent to
-<a href="mailto:dev@accumulo.apache.org">dev@accumulo.apache.org</a>.</p>
-
-<p>Ignoring specifics, contributors should be sure to make their changes against
-the earlier version in which the fix is intended, <code class="highlighter-rouge">git-rebase</code>‘ing their
-changes against the upstream branch so as to keep their changes co-located and
-free of unnecessary merges.</p>
-
-<h3 id="developers">Developers</h3>
-
-<h4 id="primary-development">Primary Development</h4>
-
-<p>Primary development should take place in <code class="highlighter-rouge">master</code> which is to contain the most
-recent, un-released version of Apache Accumulo. Branches exist for minor releases
-for each previously released major version.</p>
-
-<p>Using long-lived branches that track a major release line simplifies management and
-release practices. Developers are encouraged to make branches for their own purposes,
-for large features, release candidates or whatever else is deemed useful.</p>
-
-<h4 id="reviewing-contributor-changes">Reviewing contributor changes</h4>
-
-<p>It is always the responsibility of committers to determine that a patch is
-intended and able to be contributed.  From the
-<a href="https://www.apache.org/dev/new-committers-guide#cla">new committer’s guide</a>:
-“Please take care to ensure that patches are original works which have been
-clearly contributed to the ASF in public. In the case of any doubt (or when a
-contribution with a more complex history is presented) please consult your
-project PMC before committing it.”</p>
-
-<p>Extra diligence may be necessary when code is contributed via a pull request.
-Committers should verify that the contributor intended to submit the code as a 
-Contribution under the <a href="https://www.apache.org/licenses/LICENSE-2.0.txt">Apache License</a>.
-When pulling the code, committers should also verify that the commits pulled match the 
-list of commits sent to the Accumulo dev list in the pull request.</p>
-
-<h4 id="submit-contribution-via-patch">Submit Contribution via Patch</h4>
-
-<p>Developers should use the following steps to apply patches from
-contributors:</p>
-
-<ol>
-  <li>
-    <p>Checkout the branch for the major version which the patch is intended:</p>
-
-    <p><code class="highlighter-rouge">git checkout 1.9</code></p>
-  </li>
-  <li>
-    <p>Verify the changes introduced by the patch:</p>
-
-    <p><code class="highlighter-rouge">git apply --stat ACCUMULO-12345.patch</code></p>
-  </li>
-  <li>
-    <p>Verify that the patch applies cleanly:</p>
-
-    <p><code class="highlighter-rouge">git apply --check ACCUMULO-12345.patch</code></p>
-  </li>
-  <li>
-    <p>If all is well, apply the patch:</p>
-
-    <p><code class="highlighter-rouge">git am --signoff &lt; ACCUMULO-12345.patch</code></p>
-  </li>
-  <li>
-    <p>When finished, push the changes:</p>
-
-    <p><code class="highlighter-rouge">git push origin 1.9</code></p>
-  </li>
-  <li>
-    <p>Merge where appropriate:</p>
-
-    <p><code class="highlighter-rouge">git checkout master &amp;&amp; git merge 1.9</code></p>
-  </li>
-</ol>
-
-<h4 id="submit-contribution-via-pull-request">Submit Contribution via Pull-Request</h4>
-
-<p>If the contributor submits a repository and branch to pull
-from, the steps are even easier:</p>
-
-<ol>
-  <li>
-    <p>Add their repository as a remote to your repository</p>
-
-    <p><code class="highlighter-rouge">git remote add some_name ${repository}</code></p>
-  </li>
-  <li>
-    <p>Fetch the refs from the given repository</p>
-
-    <p><code class="highlighter-rouge">git fetch ${repository}</code></p>
-  </li>
-  <li>
-    <p>Merge in the given branch to your local branch</p>
-
-    <p><code class="highlighter-rouge">git merge some_name/${branch}</code></p>
-  </li>
-  <li>
-    <p>Delete the remote:</p>
-
-    <p><code class="highlighter-rouge">git remote remove some_name</code></p>
-  </li>
-</ol>
-
-<p>If the branch doesn’t fast-forward merge, you likely want to inform the
-contributor to update their branch to avoid the conflict resolution and merge
-commit. See the <a href="https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging">Git
-manual</a>
-for more information on merging. When merging a pull-request, it’s best to <strong>not</strong>
-include a signoff on the commit(s) as it changes the final commit ID in the
-Accumulo repository. This also has the negative effect of not automatically closing
-the Pull-Request when the changes are made public.</p>
-
-<h4 id="feature-branches">Feature Branches</h4>
-
-<p>Ease in creating and using feature branches is a desirable merit which Git
-provides with little work. Feature branches are a great way in which developers
-to work on multiple, long-running features concurrently, without worry of
-mixing code ready for public-review and code needing more internal work.
-Additionally, this creates an easily consumable series of commits in which
-other developers can track changes, and see how the feature itself evolved.</p>
-
-<p>To prevent developers’ feature branches from colliding with one another, it was
-suggested to impose a “hierarchy” in which shared feature branches are prefixed
-with <code class="highlighter-rouge">&lt;apache_id&gt;/ACCUMULO-&lt;issue#&gt;[-description]</code>.</p>
-
-<ol>
-  <li>
-    <p>Create a branch off of <code class="highlighter-rouge">master</code>.</p>
-
-    <p><code class="highlighter-rouge">git checkout &lt;apache_id&gt;/ACCUMULO-&lt;issue#&gt; master</code></p>
-  </li>
-  <li>
-    <p>Create the feature, committing early and often to appropriately outline the
-“story” behind the feature and it’s implementation.</p>
-  </li>
-  <li>
-    <p>As long as you have not collaborating with others, <code class="highlighter-rouge">git-rebase</code> your feature
-branch against upstream changes in <code class="highlighter-rouge">master</code></p>
-
-    <p><code class="highlighter-rouge">git fetch &amp;&amp; git rebase origin/master</code></p>
-  </li>
-  <li>
-    <p>If you are actively collaborating with others, you should be nice and not
-change their history. Use <code class="highlighter-rouge">git-merge</code> instead.</p>
-
-    <p><code class="highlighter-rouge">git fetch &amp;&amp; git merge origin/master</code></p>
-  </li>
-  <li>
-    <p>Continue steps 2 through 4 until the feature is complete.</p>
-  </li>
-  <li>
-    <p>Depending on the nature, duration and history of the changes in your feature
-branch, you can choose to:</p>
-
-    <ul>
-      <li>
-        <p><strong>‘Simple’ Merge</strong>:</p>
-
-        <p><code class="highlighter-rouge">git checkout master &amp;&amp; git merge &lt;apache_id&gt;/ACCUMULO-&lt;issue#&gt;</code></p>
-      </li>
-      <li>
-        <p><strong>Rebase and merge</strong> – keeps all feature-branch commits
-co-located:</p>
-
-        <p><code class="highlighter-rouge">git fetch &amp;&amp; git rebase origin/master &amp;&amp; git checkout master &amp;&amp; git merge &lt;apache_id&gt;/ACCUMULO-&lt;issue#&gt;</code></p>
-      </li>
-      <li>
-        <p><strong>Merge with squash</strong> – feature branch history is a mess, just make one commit
-with the lump-sum of your feature branch changes:</p>
-
-        <p><code class="highlighter-rouge">git checkout master &amp;&amp; git merge --squash &lt;apache_id&gt;/ACCUMULO-&lt;issue#&gt;</code></p>
-      </li>
-    </ul>
-  </li>
-</ol>
-
-<h4 id="changes-which-affect-multiple-versions-aka-merging">Changes which affect multiple versions (a.k.a. merging)</h4>
-
-<p>Merging can be a very confusing topic for users switching to Git, but it can be
-summarized fairly easily.</p>
-
-<ol>
-  <li>
-    <p><strong>Precondition</strong>: choose the right branch to start! (lowest, applicable version
-for the change)</p>
-  </li>
-  <li>
-    <p>Get your changes fixed for that earliest version.</p>
-  </li>
-  <li>
-    <p>Switch to the next highest version which future minor versions will be
-released (non-EOL major release series).</p>
-  </li>
-  <li>
-    <p><code class="highlighter-rouge">git-merge</code> the branch from #1 into the current.</p>
-  </li>
-  <li>
-    <p>In the face of conflicts, use options from <code class="highlighter-rouge">git-merge</code> to help you.</p>
-
-    <ul>
-      <li><code class="highlighter-rouge">git checkout new-version &amp;&amp; git merge --stat old-version</code></li>
-      <li><code class="highlighter-rouge">git checkout new-version &amp;&amp; git merge --no-commit old-version</code></li>
-    </ul>
-  </li>
-  <li>
-    <p>Treat your current branch as the branch from #2, and repeat from #2.</p>
-  </li>
-</ol>
-
-<p>When merging changes across major releases, there is always the possibility of
-changes which are applicable/necessary in one release, but not in any future
-releases, changes which are different in implementation due to API changes, or
-any number of other cases. Whatever the actual case is, the developer who made
-the first set of changes (you) is the one responsible for performing the merge
-through the rest of the active versions. Even when the merge may results in a
-zero-length change in content, this is incredibly important to record, as you
-are the one who knows that this zero-length change in content is correct!</p>
-
-<h2 id="code-review-process">Code review process</h2>
-
-<p>Accumulo primarily uses GitHub (via pull requests) for code reviews, but has access to an instance of <a href="https://reviews.apache.org/">Review Board</a> as well if that is preferred.</p>
-
-<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so a code review does not need to occur prior to commit. However, a committer has the option to hold a code review before a commit happens if, in their opinion, it would benefit from additional attention. Full details of the code review process for Accumulo is documented <a href="./rb">here</a></p>
-
-<h3 id="review-board">Review Board</h3>
-
-<p>Use of <a href="/contributor/rb">Review Board</a> has slowly diminished and been gradually replaced by GitHub reviews over the past year or so.</p>
-
-<h2 id="additional-contributor-information">Additional Contributor Information</h2>
-
-<h3 id="coding-practices">Coding Practices</h3>
-
-<table class="table">
-  <tbody>
-    <tr>
-      <td><strong>License Header</strong></td>
-      <td>Always add the current ASF license header as described in [ASF Source Header][srcheaders].</td>
-    </tr>
-    <tr>
-      <td><strong>Trailing Whitespaces</strong></td>
-      <td>Remove all trailing whitespaces. Eclipse users can use Source→Cleanup option to accomplish this.</td>
-    </tr>
-    <tr>
-      <td><strong>Indentation</strong></td>
-      <td>Use 2 space indents and never use tabs!</td>
-    </tr>
-    <tr>
-      <td><strong>Line Wrapping</strong></td>
-      <td>Use 100-column line width for Java code and Javadoc.</td>
-    </tr>
-    <tr>
-      <td><strong>Control Structure New Lines</strong></td>
-      <td>Use a new line with single statement if/else blocks.</td>
-    </tr>
-    <tr>
-      <td><strong>Author Tags</strong></td>
-      <td>Do not use Author Tags. The code is developed and owned by the community.</td>
-    </tr>
-  </tbody>
-</table>
-
-<h3 id="merging-practices">Merging Practices</h3>
-
-<p>Changes should be merged from earlier branches of Accumulo to later branches. Ask the <a href="mailto:dev@accumulo.apache.org">dev list</a> for instructions.</p>
-
-<h3 id="project-examples">Project Examples</h3>
-
-<p>A collection of Accumulo example code can be found at the <a href="https://github.com/apache/accumulo-examples">Accumulo Examples repository</a>.</p>
-
-<h3 id="website-contributions">Website Contributions</h3>
-
-<p>The source for this website is a collection of markdown documents that are converted to HTML using
-<a href="https://jekyllrb.com">Jekyll</a>. It can be found in the <a href="https://github.com/apache/accumulo-website">accumulo-website repo</a>. If you would like to make changes to this website, clone the website repo and edit the markdown:</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>    git clone https://github.com/apache/accumulo-website.git
-</code></pre></div></div>
-
-<p>After you have made your changes, follow the instructions in the <a href="https://github.com/apache/accumulo-website/blob/master/README.md">README.md</a> to run the website locally and make a pull request on <a href="https://github.com/apache/accumulo-website">GitHub</a>. If you have problems installing Jekyll or running the website locally, it’s OK to proceed with the pull request. A committer will review your changes before committing them and updating the website.</p>
-
-<h3 id="public-api">Public API</h3>
-
-<p>Refer to the README in the release you are using to see what packages are in the public API.</p>
-
-<p>Changes to non-private members of those classes are subject to additional scrutiny to minimize compatibility problems across Accumulo versions.</p>
-
-<h3 id="installing-apache-thrift-1">Installing Apache Thrift</h3>
-
-<p>If you activate the ‘thrift’ Maven profile, the build of some modules will attempt to run the Apache Thrift command line to regenerate stubs. If you activate this profile and don’t have Apache Thrift installed and in your path, you will see a warning and your build will fail. For Accumulo 1.5.0 and greater, install Thrift 0.9 and make sure that the ‘thrift’ command is in your path. Watch out for THRIFT-1367; you may need to configure Thrift with –without-ruby. Most developers do not n [...]
-
-<h2 id="committer-documentation">Committer Documentation</h2>
-
-<p>The links below are provided primarily for the project committers but may be of interest to contributors as well.</p>
+<p>The docs below are for committers but may be of interest to contributors as well.</p>
 
 <ul>
   <li><a href="/contributor/release-management">Release Management</a></li>
   <li><a href="/contributor/making-release">Making a Release</a></li>
-  <li><a href="https://accumulo.apache.org/contributor/verifying-release">Verifying a Release</a></li>
+  <li><a href="/contributor/verifying-release">Verifying a Release</a></li>
+  <li><a href="/contributor/testing-release">Testing a Release</a></li>
 </ul>
 
 <h2 id="project-governance">Project Governance</h2>
@@ -814,59 +172,6 @@ are the one who knows that this zero-length change in content is correct!</p>
   <li><a href="/contributor/voting">Voting</a></li>
 </ul>
 
-<h2 id="test-a-accumulo-release">Test a Accumulo release</h2>
-
-<ol>
-  <li>Set the release version, ID for staging repo, and alias to configure Maven with temporary settings:
-    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">export </span><span class="nv">RC_VERSION</span><span class="o">=</span>1.9.0
-<span class="nb">export </span><span class="nv">RC_STAGING</span><span class="o">=</span>1070
-</code></pre></div>    </div>
-  </li>
-  <li>Create temporary Maven settings
-    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">cat</span> <span class="o">&lt;&lt;</span><span class="no">EOF</span><span class="sh"> &gt;/tmp/accumulo-rc-maven.xml
-&lt;settings&gt;
-  &lt;profiles&gt;
-    &lt;profile&gt;
-      &lt;id&gt;accumuloRC&lt;/id&gt;
-      &lt;repositories&gt;
-        &lt;repository&gt;
-          &lt;id&gt;accumulorc&lt;/id&gt;
-          &lt;name&gt;accumulorc&lt;/name&gt;
-          &lt;url&gt;https://repository.apache.org/content/repositories/orgapacheaccumulo-\</span><span class="k">${</span><span class="nv">env</span><span class="p">.RC_STAGING</span><span class="k">}</span><span class="sh">/&lt;/url&gt;
-        &lt;/repository&gt;
-      &lt;/repositories&gt;
-      &lt;pluginRepositories&gt;
-        &lt;pluginRepository&gt;
-          &lt;id&gt;accumulorcp&lt;/id&gt;
-          &lt;name&gt;accumulorcp&lt;/name&gt;
-          &lt;url&gt;https://repository.apache.org/content/repositories/orgapacheaccumulo-\</span><span class="k">${</span><span class="nv">env</span><span class="p">.RC_STAGING</span><span class="k">}</span><span class="sh">/&lt;/url&gt;
-        &lt;/pluginRepository&gt;
-      &lt;/pluginRepositories&gt;
-    &lt;/profile&gt;
-  &lt;/profiles&gt;
-  &lt;activeProfiles&gt;
-    &lt;activeProfile&gt;accumuloRC&lt;/activeProfile&gt;
-  &lt;/activeProfiles&gt;
-&lt;/settings&gt;
-</span><span class="no">EOF
-</span></code></pre></div>    </div>
-    <h4 id="run-the-integration-tests-of-projects-that-use-accumulo">Run the integration tests of projects that use Accumulo</h4>
-  </li>
-  <li>Clone the <a href="https://github.com/apache/accumulo-examples">Accumulo Examples</a> project:
-    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="nv">$ </span>git clone https://github.com/apache/accumulo-examples.git
-</code></pre></div>    </div>
-  </li>
-  <li>Run the integration test
-    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="nv">$ </span>mvn <span class="nt">-s</span> /tmp/accumulo-rc-maven.xml clean verify <span class="nt">-Daccumulo</span>.version<span class="o">=</span><span class="nv">$RC_VERSION</span>
-</code></pre></div>    </div>
-    <p>Below are more projects with integration tests:</p>
-    <ul>
-      <li><a href="https://github.com/apache/accumulo-wikisearch">Wikisearch</a> - <code class="highlighter-rouge">https://github.com/apache/accumulo-wikisearch</code></li>
-      <li><a href="https://github.com/apache/fluo">Apache Fluo</a> - <code class="highlighter-rouge">https://github.com/apache/fluo</code></li>
-    </ul>
-  </li>
-</ol>
-
 
         </div>
 
diff --git a/feed.xml b/feed.xml
index 07d940e..21bb1b7 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
 </description>
     <link>https://accumulo.apache.org/</link>
     <atom:link href="https://accumulo.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Tue, 04 Jun 2019 18:15:04 -0400</pubDate>
-    <lastBuildDate>Tue, 04 Jun 2019 18:15:04 -0400</lastBuildDate>
+    <pubDate>Wed, 05 Jun 2019 12:12:24 -0400</pubDate>
+    <lastBuildDate>Wed, 05 Jun 2019 12:12:24 -0400</lastBuildDate>
     <generator>Jekyll v3.8.5</generator>
     
     


Mime
View raw message