You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by mm...@apache.org on 2019/11/14 23:49:30 UTC
[accumulo-website] branch asf-site updated: Jekyll build from
master:ade3b60
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
The following commit(s) were added to refs/heads/asf-site by this push:
new 4e9cd0c Jekyll build from master:ade3b60
4e9cd0c is described below
commit 4e9cd0ce63a10d3c14f3bb38aff33e41fe32b10d
Author: Mike Miller <mm...@apache.org>
AuthorDate: Thu Nov 14 18:48:49 2019 -0500
Jekyll build from master:ade3b60
Update contribute pages (#209)
* Move information not for first time committers to the in depth guide
* Update links on how to contribute to point to new first issue label
* Add link to draft pull requests
---
contributors-guide/index.html | 31 ++++++++++
feed.xml | 24 ++++----
how-to-contribute/index.html | 140 ++++++++----------------------------------
redirects.json | 2 +-
4 files changed, 71 insertions(+), 126 deletions(-)
diff --git a/contributors-guide/index.html b/contributors-guide/index.html
index 6fcf29b..29d719c 100644
--- a/contributors-guide/index.html
+++ b/contributors-guide/index.html
@@ -143,6 +143,32 @@
<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>Accumulo previously used <a href="https://issues.apache.org/jira/browse/ACCUMULO">JIRA</a>, but now uses GitHub issues.
+All new issues should be opened using GitHub. If working an existing JIRA
+issue, please do the following :</p>
+
+<ul>
+ <li>Open a new GitHub issue or pull request.</li>
+ <li>Link the GitHub issue to the JIRA issue.</li>
+ <li>Link the JIRA issue to the GitHub issue.</li>
+ <li>Close the JIRA issue as a duplicate.</li>
+</ul>
+
+<p>Eventually, JIRA will be transitioned to a read-only state for reference. For
+finding issues to work, there may still be
+<a href="https://s.apache.org/newbie_accumulo_tickets">open issues labeled for newbies</a> in JIRA.</p>
+
+<h2 id="github-project-boards-projects">GitHub Project Boards (Projects)</h2>
+
+<p>Project boards (also “projects”) are used to track the status of issues and
+pull requests for a specific milestone. Projects with names such as <code class="highlighter-rouge">2.1.0</code>,
+and <code class="highlighter-rouge">1.9.2</code> are used for tracking issues associated with a particular release
+and release planning. These are set up as basic Kanban boards with automation,
+with <code class="highlighter-rouge">To do</code>, <code class="highlighter-rouge">In progress</code>, and <code class="highlighter-rouge">Done</code> statuses. These projects are marked as
+“closed” when the version indicated is released. Other projects may exist for
+miscellaneous puposes, such as tracking multiple issues related to a larger
+effort. These projects will be named appropriately to indicate their purpose.</p>
+
<h2 id="for-contributors">For Contributors</h2>
<p>The docs below provide additional information for contributors.</p>
@@ -163,6 +189,11 @@ documentation.</p>
<li><a href="/contributor/testing-release">Testing a Release</a></li>
</ul>
+<h2 id="code-editors">Code Editors</h2>
+
+<p>Feel free to use any editor when contributing Accumulo. If you are looking for a recommendation, many Accumulo
+developers use [IntelliJ] or [Eclipse]. Below are some basic instructions to help you get started.</p>
+
<h2 id="project-governance">Project Governance</h2>
<p>For details about governance policies for the Accumulo project view the following links.</p>
diff --git a/feed.xml b/feed.xml
index 7cc4f1b..7bf1dac 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>Thu, 14 Nov 2019 10:30:38 -0800</pubDate>
- <lastBuildDate>Thu, 14 Nov 2019 10:30:38 -0800</lastBuildDate>
+ <pubDate>Thu, 14 Nov 2019 18:48:44 -0500</pubDate>
+ <lastBuildDate>Thu, 14 Nov 2019 18:48:44 -0500</lastBuildDate>
<generator>Jekyll v4.0.0</generator>
@@ -97,7 +97,7 @@ they can be removed. This strategy prevents new usages of non-public APIs while
to the maven-checkstyle-plugin configuration.</p>
</description>
- <pubDate>Mon, 04 Nov 2019 00:00:00 -0800</pubDate>
+ <pubDate>Mon, 04 Nov 2019 00:00:00 -0500</pubDate>
<link>https://accumulo.apache.org/blog/2019/11/04/checkstyle-import-control.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/11/04/checkstyle-import-control.html</guid>
@@ -240,7 +240,7 @@ we are able to successfully run the continuos ingest test. Going forward, we’l
with ADLS Gen2 and add/update blog as we come along.</p>
</description>
- <pubDate>Tue, 15 Oct 2019 00:00:00 -0700</pubDate>
+ <pubDate>Tue, 15 Oct 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/blog/2019/10/15/accumulo-adlsgen2-notes.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/10/15/accumulo-adlsgen2-notes.html</guid>
@@ -564,7 +564,7 @@ to Accumulo to make working with EC a bit easier. Our initial thoughts are colle
Accumulo dev list <a href="https://lists.apache.org/thread.html/4ac5b0f664e15fa120e748892612f1e417b7dee3e1539669d179900c@%3Cdev.accumulo.apache.org%3E">post</a>.</p>
</description>
- <pubDate>Tue, 17 Sep 2019 00:00:00 -0700</pubDate>
+ <pubDate>Tue, 17 Sep 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/blog/2019/09/17/erasure-coding.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/09/17/erasure-coding.html</guid>
@@ -705,7 +705,7 @@ S3Gaurd. If this is the case then only the write ahead logs would need to be
stored in HDFS.</p>
</description>
- <pubDate>Tue, 10 Sep 2019 00:00:00 -0700</pubDate>
+ <pubDate>Tue, 10 Sep 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/blog/2019/09/10/accumulo-S3-notes.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/09/10/accumulo-S3-notes.html</guid>
@@ -846,7 +846,7 @@ to configure the cluster in a way that allows the one fast scan to be prioritize
<p>Checkout some examples in the <a href="/docs/2.x//administration/scan-executors">user guide</a>.</p>
</description>
- <pubDate>Mon, 12 Aug 2019 00:00:00 -0700</pubDate>
+ <pubDate>Mon, 12 Aug 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/blog/2019/08/12/why-upgrade.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/08/12/why-upgrade.html</guid>
@@ -1054,7 +1054,7 @@ at table creation time can be much faster than adding splits after creation.<
<p>View the <a href="/docs/2.x/administration/upgrading">Upgrading Accumulo documentation</a> for guidance.</p>
</description>
- <pubDate>Fri, 02 Aug 2019 00:00:00 -0700</pubDate>
+ <pubDate>Fri, 02 Aug 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/release/accumulo-2.0.0/</link>
<guid isPermaLink="true">https://accumulo.apache.org/release/accumulo-2.0.0/</guid>
@@ -1071,7 +1071,7 @@ the 2.0 Accumulo user manual. The <a href="https://github.com/apache/acc
for using Spark with Accumulo.</p>
</description>
- <pubDate>Wed, 24 Apr 2019 00:00:00 -0700</pubDate>
+ <pubDate>Wed, 24 Apr 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/blog/2019/04/24/using-spark-with-accumulo.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/04/24/using-spark-with-accumulo.html</guid>
@@ -1251,7 +1251,7 @@ address thrift CVE. Issue <a href="https://github.com/apache/accumulo/is
<p>View the <a href="/docs/2.x/administration/upgrading">Upgrading Accumulo documentation</a> for guidance.</p>
</description>
- <pubDate>Wed, 10 Apr 2019 00:00:00 -0700</pubDate>
+ <pubDate>Wed, 10 Apr 2019 00:00:00 -0400</pubDate>
<link>https://accumulo.apache.org/release/accumulo-1.9.3/</link>
<guid isPermaLink="true">https://accumulo.apache.org/release/accumulo-1.9.3/</guid>
@@ -1281,7 +1281,7 @@ to attendees. If you are interested in a corporate sponsorship, please feel free
<a href="mailto:elserj@apache.org">Josh Elser</a> for more information.</p>
</description>
- <pubDate>Thu, 28 Feb 2019 00:00:00 -0800</pubDate>
+ <pubDate>Thu, 28 Feb 2019 00:00:00 -0500</pubDate>
<link>https://accumulo.apache.org/blog/2019/02/28/nosql-day.html</link>
<guid isPermaLink="true">https://accumulo.apache.org/blog/2019/02/28/nosql-day.html</guid>
@@ -1323,7 +1323,7 @@ complete in this alpha release.</li>
</ul>
</description>
- <pubDate>Thu, 31 Jan 2019 00:00:00 -0800</pubDate>
+ <pubDate>Thu, 31 Jan 2019 00:00:00 -0500</pubDate>
<link>https://accumulo.apache.org/release/accumulo-2.0.0-alpha-2/</link>
<guid isPermaLink="true">https://accumulo.apache.org/release/accumulo-2.0.0-alpha-2/</guid>
diff --git a/how-to-contribute/index.html b/how-to-contribute/index.html
index a281e69..5edcda1 100644
--- a/how-to-contribute/index.html
+++ b/how-to-contribute/index.html
@@ -144,71 +144,18 @@
there are other ways to contribute to Accumulo:</p>
<ul>
- <li>answer questions on <a href="/contact-us/#mailing-lists">mailing lists</a></li>
+ <li>communicate on one of the <a href="/contact-us/#mailing-lists">mailing lists</a></li>
<li>review <a href="https://github.com/apache/accumulo/pulls">pull requests</a></li>
<li>verify and test new <a href="/release/">releases</a></li>
<li>update the <a href="https://github.com/apache/accumulo-website">Accumulo website and documentation</a></li>
+ <li>report bugs or triage issues</li>
</ul>
-<p>Contributions are reviewed (via GitHub pull requests) by
-the community before being merged by a committer.</p>
+<p>First time developers should start with an issue labeled <a href="https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">good first issue</a>.</p>
-<p>This document provides basic instructions for contributing to Accumulo. If you are looking for more information, check out the more comprehensive <a href="/contributors-guide/">contributor guide</a>.</p>
+<p>Any questions/ideas don’t hesitate to <a href="/contact-us/">contact us</a>.</p>
-<h2 id="issues">Issues</h2>
-
-<p>Accumulo uses GitHub issues to track bugs and features. Each git repository
-has its own issues. In GitHub pull request are issues, therefore creating an
-issue before a pull request is optional. If unsure whether to start with an
-issue or pull request, then create an issue. If you need help finding an issue
-to work on, check out the <a href="https://github.com/search?utf8=%E2%9C%93&q=state%3Aopen+label%3A%22help+wanted%22+repo%3Aapache%2Faccumulo+repo%3Aapache%2Faccumulo-website+repo%3Aapache%2Faccumulo-examples+repo%3Aapache%2Faccumulo-testing&type=">open issues labeled ‘helpwanted’</a> or
-<a href="/contact-us/">contact us</a>.</p>
-
-<p>Accumulo previously used <a href="https://issues.apache.org/jira/browse/ACCUMULO">JIRA</a>, but is now transitioning to GitHub issues.
-All new issues should be opened using GitHub. When working an existing JIRA
-issue, please do the following :</p>
-
-<ul>
- <li>Open a new GitHub issue or pull request.</li>
- <li>Link the GitHub issue to the JIRA issue.</li>
- <li>Link the JIRA issue to the GitHub issue.</li>
- <li>Close the JIRA issue as a duplicate.</li>
-</ul>
-
-<p>Eventually JIRA will be transitioned to a read-only state for reference. For
-finding issues to work, there may still be
-<a href="https://s.apache.org/newbie_accumulo_tickets">open issues labeled for newbies</a> in JIRA.</p>
-
-<h2 id="labels">Labels</h2>
-
-<p>Labels, such as <code class="highlighter-rouge">bug</code>, <code class="highlighter-rouge">enhancement</code>, and <code class="highlighter-rouge">duplicate</code>, are used to
-descriptively organize issues and pull requests. Issues labeled with <code class="highlighter-rouge">blocker</code>
-indicate that the developers have determined that the issue must be fixed prior
-to a release (to be used in conjunction with a version-specific project board;
-see the next section for information on project boards).</p>
-
-<p>Currently only Accumulo committers can set labels. If you think a label should
-be set, comment on the issue and someone will help.</p>
-
-<h2 id="project-boards-projects">Project Boards (Projects)</h2>
-
-<p>Project boards (also “projects”) are used to track the status of issues and
-pull requests for a specific milestone. Projects with names such as <code class="highlighter-rouge">2.1.0</code>,
-and <code class="highlighter-rouge">1.9.2</code> are used for tracking issues associated with a particular release
-and release planning. These are set up as basic Kanban boards with automation,
-with <code class="highlighter-rouge">To do</code>, <code class="highlighter-rouge">In progress</code>, and <code class="highlighter-rouge">Done</code> statuses. These projects are marked as
-“closed” when the version indicated is released. Other projects may exist for
-miscellaneous puposes, such as tracking multiple issues related to a larger
-effort. These projects will be named appropriate to indicate their purpose.</p>
-
-<p>Committers manage the project boards. If you need help with a project board or
-have questions, contact the developers using the link at the top of this page.</p>
-
-<h2 id="repositories">Repositories</h2>
-
-<p>Contributions can be made to the following repositories. While the general contribution workflow is
-described below, repositories have special instructions in their <code class="highlighter-rouge">CONTRIBUTING.md</code> file which can be
-viewed by clicking on <code class="highlighter-rouge">contribute</code> in the Links column below.</p>
+<h2 id="accumulo-repositories">Accumulo Repositories</h2>
<table>
<thead>
@@ -225,38 +172,48 @@ viewed by clicking on <code class="highlighter-rouge">contribute</code> in the L
<td>Core Project</td>
</tr>
<tr>
- <td><a href="https://github.com/apache/accumulo-website">Accumulo Website</a></td>
+ <td><a href="https://github.com/apache/accumulo-website">Website</a></td>
<td><a href="https://github.com/apache/accumulo-website/blob/master/CONTRIBUTING.md">Contribute</a> <a href="https://github.com/apache/accumulo-website/issues">Issues</a></td>
<td>Source for this website</td>
</tr>
<tr>
- <td><a href="https://github.com/apache/accumulo-examples">Accumulo Examples</a></td>
+ <td><a href="https://github.com/apache/accumulo-examples">Examples</a></td>
<td><a href="https://github.com/apache/accumulo-examples/blob/master/CONTRIBUTING.md">Contribute</a> <a href="https://github.com/apache/accumulo-examples/issues">Issues</a></td>
- <td>Accumulo example code</td>
+ <td>Example code</td>
</tr>
<tr>
- <td><a href="https://github.com/apache/accumulo-testing">Accumulo Testing</a></td>
+ <td><a href="https://github.com/apache/accumulo-testing">Testing</a></td>
<td><a href="https://github.com/apache/accumulo-testing/blob/master/CONTRIBUTING.md">Contribute</a> <a href="https://github.com/apache/accumulo-testing/issues">Issues</a></td>
- <td>Accumulo test suites such as continuous ingest and random walk</td>
+ <td>Test suites such as continuous ingest and random walk</td>
</tr>
<tr>
- <td><a href="https://github.com/apache/accumulo-docker">Accumulo Docker</a></td>
+ <td><a href="https://github.com/apache/accumulo-docker">Docker</a></td>
<td><a href="https://github.com/apache/accumulo-docker/blob/master/CONTRIBUTING.md">Contribute</a> <a href="https://github.com/apache/accumulo-docker/issues">Issues</a></td>
<td>Source for Accumulo Docker image</td>
</tr>
<tr>
- <td><a href="https://github.com/apache/accumulo-wikisearch">Accumulo Wikisearch</a></td>
+ <td><a href="https://github.com/apache/accumulo-wikisearch">Wikisearch</a></td>
<td><a href="https://github.com/apache/accumulo-wikisearch/blob/master/CONTRIBUTING.md">Contribute</a> <a href="https://github.com/apache/accumulo-wikisearch/issues">Issues</a></td>
- <td>Accumulo example application that indexes and queries Wikipedia data</td>
+ <td>Example application that indexes and queries Wikipedia data</td>
+ </tr>
+ <tr>
+ <td><a href="https://github.com/apache/accumulo-proxy">Proxy</a></td>
+ <td><a href="https://github.com/apache/accumulo-proxy/issues">Issues</a></td>
+ <td>Apache Thrift service that exposes Accumulo to other languages</td>
+ </tr>
+ <tr>
+ <td><a href="https://github.com/apache/accumulo-maven-plugin">Maven plugin</a></td>
+ <td><a href="https://github.com/apache/accumulo-maven-plugin/issues">Issues</a></td>
+ <td>Maven plugin that runs Accumulo</td>
</tr>
</tbody>
</table>
-<h2 id="contribution-workflow">Contribution workflow</h2>
+<h2 id="example-contribution-workflow">Example Contribution workflow</h2>
<ol>
<li>Create a <a href="https://github.com/join">GitHub account</a> for issues and pull requests.</li>
- <li>Find an <a href="https://github.com/search?utf8=%E2%9C%93&q=state%3Aopen+label%3A%22help+wanted%22+repo%3Aapache%2Faccumulo+repo%3Aapache%2Faccumulo-website+repo%3Aapache%2Faccumulo-examples+repo%3Aapache%2Faccumulo-testing&type=">issue</a> to work on or optionally create one that describes the work that you want to do.</li>
+ <li>Find an <a href="https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">issue</a> to work on or optionally create one that describes the work that you want to do.</li>
<li><a href="https://help.github.com/articles/fork-a-repo/">Fork</a> and <a href="https://help.github.com/articles/cloning-a-repository/">clone</a> the GitHub repository that you want to contribute to.</li>
<li>Create a branch in the local clone of your fork.
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> git checkout -b accumulo-4321
@@ -269,7 +226,7 @@ viewed by clicking on <code class="highlighter-rouge">contribute</code> in the L
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> git push origin accumulo-4321
</code></pre></div> </div>
</li>
- <li>Create a <a href="https://help.github.com/articles/about-pull-requests/">Pull Request</a> on GitHub to the appropriate repository. If the work is not complete and the Pull Request is for feedback, please put <code class="highlighter-rouge">[WIP]</code> in the subject.</li>
+ <li>Create a <a href="https://help.github.com/articles/about-pull-requests/">Pull Request</a> on GitHub to the appropriate repository. A <a href="https://github.blog/2019-02-14-introducing-draft-pull-requests/">draft pull request</a> can be used if the work is not complete.</li>
<li>At least one committer (and others in the community) will review your pull request and add any comments to your code.</li>
<li>Push any changes from the review to the branch as new commits so the reviewer only needs to review new changes. Please avoid squashing commits after the review starts. Squashing makes it hard for the reviewer to follow the changes.</li>
<li>Repeat this process until a reviewer approves the pull request.</li>
@@ -279,54 +236,11 @@ viewed by clicking on <code class="highlighter-rouge">contribute</code> in the L
<h2 id="coding-guidelines">Coding Guidelines</h2>
<ul>
- <li>If a change needs to go into multiple branches of Accumulo, it should be merged into earlier branches then later branches.</li>
<li>Accumulo follows <a href="http://semver.org/spec/v2.0.0.html">semver</a> for its <a href="/api/">public API</a>.</li>
<li>Every file requires the ASF license header as described in <a href="https://www.apache.org/legal/src-headers">ASF Source Header</a>.</li>
- <li>Remove all trailing whitespaces. Eclipse users can use Source→Cleanup option to accomplish this.</li>
- <li>Use 2 space indents and never use tabs!</li>
- <li>Use 100-column line width for Java code and Javadoc.</li>
- <li>Use a new line with single statement if/else blocks.</li>
<li>Do not use Author Tags. The code is developed and owned by the community.</li>
</ul>
-<h2 id="code-editors">Code Editors</h2>
-
-<p>Feel free to use any editor when contributing Accumulo. If you are looking for a recommendation, many Accumulo
-developers use <a href="https://www.jetbrains.com/idea/">IntelliJ</a> or <a href="https://www.eclipse.org/">Eclipse</a>. Below are some basic instructions to help you get started.</p>
-
-<h3 id="intellij">IntelliJ</h3>
-
-<ol>
- <li>Download and install <a href="https://www.jetbrains.com/idea/">IntelliJ</a></li>
- <li>Clone the Accumulo repository that you want to work on.
- <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/apache/accumulo.git
-</code></pre></div> </div>
- </li>
- <li><a href="https://www.jetbrains.com/help/idea/maven.html#maven_import_project_start">Import</a> the repository as a Maven project into IntelliJ</li>
- <li>(Optional) Download and import <code class="highlighter-rouge">Eclipse-Accumulo-Codestyle.xml</code> from Accumulo’s <a href="https://github.com/apache/accumulo/tree/master/contrib">contrib</a> directory
- <ul>
- <li>Import via <code class="highlighter-rouge">File</code> > <code class="highlighter-rouge">Settings</code> > <code class="highlighter-rouge">Code Style</code> and clicking on cog wheel</li>
- </ul>
- </li>
-</ol>
-
-<h3 id="eclipse">Eclipse</h3>
-
-<ol>
- <li>Download and install <a href="https://www.eclipse.org/">Eclipse</a>.</li>
- <li>Clone the Accumulo repository that you want to work on.
- <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/apache/accumulo.git
-</code></pre></div> </div>
- </li>
- <li><a href="https://stackoverflow.com/questions/2061094/importing-maven-project-into-eclipse">Import</a> the repository as a Maven project into Eclipse</li>
- <li>(Optional) Download and import Eclipse formatting and style guides from Accumulo’s <a href="https://github.com/apache/accumulo/tree/master/contrib">contrib</a> directory
- <ul>
- <li>Import Formatter: <code class="highlighter-rouge">Preferences</code> > <code class="highlighter-rouge">Java</code> > <code class="highlighter-rouge">Code Style</code> > <code class="highlighter-rouge">Formatter</code> and import the <code class="highlighter-rouge">Eclipse-Accumulo-Codestyle.xml</code> downloaded in the previous step.</li>
- <li>Import Template: <code class="highlighter-rouge">Preferences</code> > <code class="highlighter-rouge">Java</code> > <code class="highlighter-rouge">Code Style</code> > <code class="highlighter-rouge">Code Templates</code> and import the <code class="highlighter-rouge">Eclipse-Accumulo-Template.xml</code>. Make sure to check the “Automatically add comments” box. This template adds the ASF header and so on for new code.</li>
- </ul>
- </li>
-</ol>
-
<h2 id="helpful-links">Helpful Links</h2>
<ul>
@@ -334,7 +248,7 @@ developers use <a href="https://www.jetbrains.com/idea/">IntelliJ</a> or <a href
<li><strong>Releases</strong> - <a href="/contributor/making-release">Making a release</a>, <a href="/contributor/verifying-release">Verifying a release</a></li>
</ul>
-<p>For more details, see the <a href="/contributors-guide/">contributor guide</a>.</p>
+<p>For more information, see the <a href="/contributors-guide/">contributor guide</a>.</p>
</div>
diff --git a/redirects.json b/redirects.json
index d26b373..6e10199 100644
--- a/redirects.json
+++ b/redirects.json
@@ -1 +1 @@
-{"/release_notes/1.5.1.html":"https://accumulo.apache.org/release/accumulo-1.5.1/","/release_notes/1.6.0.html":"https://accumulo.apache.org/release/accumulo-1.6.0/","/release_notes/1.6.1.html":"https://accumulo.apache.org/release/accumulo-1.6.1/","/release_notes/1.6.2.html":"https://accumulo.apache.org/release/accumulo-1.6.2/","/release_notes/1.7.0.html":"https://accumulo.apache.org/release/accumulo-1.7.0/","/release_notes/1.5.3.html":"https://accumulo.apache.org/release/accumulo-1.5.3/" [...]
\ No newline at end of file
+{"/release_notes/1.5.1.html":"https://accumulo.apache.org/release/accumulo-1.5.1/","/release_notes/1.6.0.html":"https://accumulo.apache.org/release/accumulo-1.6.0/","/release_notes/1.6.1.html":"https://accumulo.apache.org/release/accumulo-1.6.1/","/release_notes/1.6.2.html":"https://accumulo.apache.org/release/accumulo-1.6.2/","/release_notes/1.7.0.html":"https://accumulo.apache.org/release/accumulo-1.7.0/","/release_notes/1.5.3.html":"https://accumulo.apache.org/release/accumulo-1.5.3/" [...]
\ No newline at end of file