You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by kt...@apache.org on 2018/03/16 18:26:09 UTC
[accumulo-website] branch asf-site updated: Jekyll build from
master:8734edf
This is an automated email from the ASF dual-hosted git repository.
kturner 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 46d0f17 Jekyll build from master:8734edf
46d0f17 is described below
commit 46d0f1763f1912151a0d9068df49e0c20378c8e6
Author: Keith Turner <kt...@apache.org>
AuthorDate: Fri Mar 16 14:25:00 2018 -0400
Jekyll build from master:8734edf
proposal for github issues (#59)
---
.../2018/03/08/moving-to-github-issues.html | 81 +++------
contact-us/index.html | 5 +-
contributor/making-release.html | 10 +-
feed.xml | 189 ++++-----------------
how-to-contribute/index.html | 81 +++++++--
index.html | 14 +-
news/index.html | 13 +-
tour/index.html | 2 +-
8 files changed, 158 insertions(+), 237 deletions(-)
diff --git a/tour/index.html b/blog/2018/03/08/moving-to-github-issues.html
similarity index 79%
copy from tour/index.html
copy to blog/2018/03/08/moving-to-github-issues.html
index 2e36887..701ed6f 100644
--- a/tour/index.html
+++ b/blog/2018/03/08/moving-to-github-issues.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>Accumulo Tour</title>
+<title>Migrating to GitHub Issues</title>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script>
@@ -146,63 +146,34 @@
</div>
<div id="content">
- <article class="post">
-
- <header class="post-header">
- <h1 class="post-title">Accumulo Tour</h1>
- </header>
-
- <div class="post-content">
-
-<p>Welcome to the Accumulo tour! The tour offers a hands on introduction to the Accumulo Java API, broken down into
-independent steps and exercises. The exercises give you a chance to apply what you have learned by writing code on your
-own. The answers to an exercise are typically provided in the next step. The tour starts with a
-<a href="/tour/getting-started/">Getting Started</a> page that will help you get set up.</p>
-
-<p>When on a tour page, the left and right keys on the keyboard can be used to navigate. If you have any questions
-or suggestions while going through the tour, please send an email to our <a href="/contact-us/#mailing-lists">mailing list</a>
-or <a href="https://issues.apache.org/jira/projects/ACCUMULO">create an issue</a>.</p>
-
-<ol>
- <li>
- <p><a href="/tour/getting-started/">Getting Started</a></p>
- </li>
- <li>
- <p><a href="/tour/basic-read-write/">Writing and Reading</a></p>
- </li>
- <li>
- <p><a href="/tour/data-model/">Data Model</a></p>
- </li>
- <li>
- <p><a href="/tour/data-model-code/">Data Model Code</a></p>
- </li>
- <li>
- <p><a href="/tour/authorizations/">Authorizations</a></p>
- </li>
- <li>
- <p><a href="/tour/authorizations-code/">Authorizations Code</a></p>
- </li>
- <li>
- <p><a href="/tour/ranges-splits/">Ranges and Splits</a></p>
- </li>
- <li>
- <p><a href="/tour/batch-scanner/">Batch Scanner</a></p>
- </li>
- <li>
- <p><a href="/tour/batch-scanner-code/">Batch Scanner Code</a></p>
- </li>
- <li>
- <p><a href="/tour/conditional-writer/">Conditional Writer</a></p>
- </li>
- <li>
- <p><a href="/tour/conditional-writer-code/">Conditional Writer Code</a></p>
- </li>
-</ol>
+ <h1 class="title">Migrating to GitHub Issues</h1>
+
+ <p>
+
+<b>Date: </b> 08 Mar 2018<br>
+
+</p>
+
+<p>Apache Accumulo is migrating from <a href="https://issues.apache.org/jira/browse/ACCUMULO">JIRA</a> to <a href="https://github.com/apache/accumulo/issues">GitHub issues</a>. The migration is starting with an initial plan, but it may change as the community uses it. For a description of the initial operating plan see the <a href="/how-to-contribute/#issues">issues section of How to Contribute</a> and the <a href="/contributor/making-release#triage-issues">triaging issues section of Ma [...]
+
+<h2 id="motivation">Motivation</h2>
+
+<p>Doing routine activities in less time is one motivation for the migration. Below are some examples.</p>
+
+<ul>
+ <li>For GitHub a pull request is an issue. Therefore, creating an issue before a pull request is optional. Before the migration, an issue needed to be created in JIRA before creating a pull request. This was cumbersome for small changes.</li>
+ <li>When browsing commits in GitHub, issue numbers can be clicked.</li>
+ <li>Discussions on pull request can easily reference issues with simple markdown syntax.</li>
+ <li>Commits can close issues if the commit message contains “fixes #xyz”</li>
+</ul>
+
+<h2 id="migration">Migration</h2>
+
+<p>There is no plan to migrate all existing issues in JIRA. The plan is to only migrate issues that someone is interested in or are actively being worked. Migration is done by linking the JIRA and GitHub issues to each other and then closing the JIRA issue. No new issues should be opened in JIRA. JIRA will eventually be transitioned to a read only state.</p>
- </div>
-</article>
+<p><strong>View all posts in the <a href="/news">news archive</a></strong></p>
</div>
diff --git a/contact-us/index.html b/contact-us/index.html
index 93548ff..7ec6840 100644
--- a/contact-us/index.html
+++ b/contact-us/index.html
@@ -152,8 +152,7 @@
<h2 id="issues">Issues</h2>
-<p>Accumulo uses <a href="https://issues.apache.org/jira/browse/ACCUMULO">JIRA</a> to track bugs and new features. Before creating an issue, you will need to create
-an <a href="https://issues.apache.org/jira/secure/Signup!default.jspa">Apache JIRA account</a>.</p>
+<p>Accumulo uses GitHub issues to track bugs and new features. Visit <a href="/how-to-contribute">How to contribute</a> for more information.</p>
<h2 id="mailing-lists">Mailing Lists</h2>
@@ -195,7 +194,7 @@ follow discussions as they happen.</p>
</tr>
<tr>
<td><strong>notifications</strong></td>
- <td>Automated notifications (JIRA, etc.)</td>
+ <td>Automated notifications (GitHub, etc.)</td>
<td><a class="btn btn-primary btn-xs" href="https://lists.apache.org/list.html?notifications@accumulo.apache.org"><span class="glyphicon glyphicon-search"></span> Archive</a></td>
<td><a class="btn btn-success btn-xs" href="mailto:notifications-subscribe@accumulo.apache.org"><span class="glyphicon glyphicon-plus"></span> Subscribe</a> <a class="btn btn-danger btn-xs" href="mailto:notifications-unsubscribe@accumulo.apache.org"><span class="glyphicon glyphicon-remove"></span> Unsubscribe</a></td>
<td> </td>
diff --git a/contributor/making-release.html b/contributor/making-release.html
index 2efc8b1..154efa5 100644
--- a/contributor/making-release.html
+++ b/contributor/making-release.html
@@ -166,6 +166,14 @@ the maven-release-plugin and staging the release candidate).</li>
<p>Given all of this, it’s recommended that you only attempt making a release from a GNU/Linux machine.</p>
+<h2 id="triage-issues">Triage issues.</h2>
+
+<p>Before creating a release candidate, all open issues with a fix version of the
+release candidate should be triaged. During the transition from JIRA to GitHub
+issues, anyone doing triage will need to search for open issues in both
+locations. Searching in both locations is only necessary for branches that
+have not released since the transition started.</p>
+
<h2 id="create-the-candidate">Create the candidate</h2>
<p><strong>TL;DR</strong></p>
@@ -261,7 +269,7 @@ automatically.</p>
<ul>
<li>Update downloads page</li>
- <li>Create a post in <code class="highlighter-rouge">_posts/release/</code> containing release notes (ensure notes contain link to JIRA changes for that version)</li>
+ <li>Create a post in <code class="highlighter-rouge">_posts/release/</code> containing release notes</li>
<li>Remove previous bug-fix release (if applicable)</li>
<li>Update doap_Accumulo.rdf</li>
</ul>
diff --git a/feed.xml b/feed.xml
index 946df64..0140e64 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,12 +6,41 @@
</description>
<link>https://accumulo.apache.org/</link>
<atom:link href="https://accumulo.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Wed, 14 Mar 2018 16:58:24 -0400</pubDate>
- <lastBuildDate>Wed, 14 Mar 2018 16:58:24 -0400</lastBuildDate>
+ <pubDate>Fri, 16 Mar 2018 14:24:47 -0400</pubDate>
+ <lastBuildDate>Fri, 16 Mar 2018 14:24:47 -0400</lastBuildDate>
<generator>Jekyll v3.6.2</generator>
<item>
+ <title>Migrating to GitHub Issues</title>
+ <description><p>Apache Accumulo is migrating from <a href="https://issues.apache.org/jira/browse/ACCUMULO">JIRA</a> to <a href="https://github.com/apache/accumulo/issues">GitHub issues</a>. The migration is starting with an initial plan, but it may change as the community uses it. For a description of the initial operating plan see the <a href="/how-to-contribute/#issues">issues section of How to Contribute</a& [...]
+
+<h2 id="motivation">Motivation</h2>
+
+<p>Doing routine activities in less time is one motivation for the migration. Below are some examples.</p>
+
+<ul>
+ <li>For GitHub a pull request is an issue. Therefore, creating an issue before a pull request is optional. Before the migration, an issue needed to be created in JIRA before creating a pull request. This was cumbersome for small changes.</li>
+ <li>When browsing commits in GitHub, issue numbers can be clicked.</li>
+ <li>Discussions on pull request can easily reference issues with simple markdown syntax.</li>
+ <li>Commits can close issues if the commit message contains “fixes #xyz”</li>
+</ul>
+
+<h2 id="migration">Migration</h2>
+
+<p>There is no plan to migrate all existing issues in JIRA. The plan is to only migrate issues that someone is interested in or are actively being worked. Migration is done by linking the JIRA and GitHub issues to each other and then closing the JIRA issue. No new issues should be opened in JIRA. JIRA will eventually be transitioned to a read only state.</p>
+
+</description>
+ <pubDate>Thu, 08 Mar 2018 00:00:00 -0500</pubDate>
+ <link>https://accumulo.apache.org/blog/2018/03/08/moving-to-github-issues.html</link>
+ <guid isPermaLink="true">https://accumulo.apache.org/blog/2018/03/08/moving-to-github-issues.html</guid>
+
+
+ <category>blog</category>
+
+ </item>
+
+ <item>
<title>Take the Accumulo Tour!</title>
<description><p>Apache Accumulo now has a <a href="/tour/">hands-on tour</a> that introduces users to key Accumulo concepts
by completing a series of programming exercises. Don’t worry! Solutions are provided if
@@ -1179,161 +1208,5 @@ standards, testing updates, maintaining dependency packages, and more.</p>
</item>
- <item>
- <title>Simpler scripts and configuration coming in Accumulo 2.0.0</title>
- <description><p>For the upcoming 2.0.0 release, Accumulo’s scripts and configuration <a href="https://issues.apache.org/jira/browse/ACCUMULO-4490">were refactored</a>
-to make Accumulo easier to use. While Accumulo’s documentation (i.e. the user
-manual and <a href="https://github.com/apache/accumulo/blob/master/INSTALL.md">INSTALL.md</a>) were updated with any changes that were made, this blog post provides
-a summary of the changes.</p>
-
-<h3 id="fewer-scripts">Fewer scripts</h3>
-
-<p>Before 2.0.0, the <code class="highlighter-rouge">bin/</code> directory of Accumulo’s binary tarball contained about 20 scripts:</p>
-
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">ls </span>accumulo-1.8.0/bin/
-accumulo build_native_library.sh generate_monitor_certificate.sh start-here.sh stop-server.sh
-accumulo_watcher.sh check-slaves LogForwarder.sh start-server.sh tdown.sh
-bootstrap_config.sh config-server.sh start-all.sh stop-all.sh tool.sh
-bootstrap_hdfs.sh config.sh start-daemon.sh stop-here.sh tup.sh
-</code></pre></div></div>
-
-<p>The number of scripts made it difficult to know which scripts to use. If you added the <code class="highlighter-rouge">bin/</code> directory to your
-<code class="highlighter-rouge">PATH</code>, it could add unnecessary commands to your PATH or cause commands to be overridden due generic names
-(like ‘start-all.sh’). The number of scripts were reduced by removing scripts that are no longer used and combining
-scripts with similar functionality.</p>
-
-<p>Starting with 2.0.0, Accumulo will only have 4 scripts in its <code class="highlighter-rouge">bin/</code> directory:</p>
-
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">ls </span>accumulo-2.0.0/bin/
-accumulo accumulo-cluster accumulo-service accumulo-util
-</code></pre></div></div>
-
-<p>Below are some notes on this change:</p>
-
-<ul>
- <li>The ‘accumulo’ script was mostly left alone except for improved usage.</li>
- <li>The ‘accumulo-service’ script was created to manage Accumulo processes as services</li>
- <li>The ‘accumulo-cluster’ command was created to manage Accumulo on cluster and replaces ‘start-all.sh’ and ‘stop-all.sh’.</li>
- <li>The ‘accumulo-util’ command combines many utility scripts such as ‘build_native_library.sh’, ‘tool.sh’, etc into one script.</li>
-</ul>
-
-<h3 id="less-configuration">Less configuration</h3>
-
-<p>Before 2.0.0, Accumulo’s <code class="highlighter-rouge">conf/</code> directory looked like the following (after creating initial config files
-using ‘bootstrap_config.sh’):</p>
-
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">ls </span>accumulo-1.8.0/conf/
-accumulo-env.sh auditLog.xml generic_logger.properties masters slaves
-accumulo-metrics.xml client.conf generic_logger.xml monitor templates
-accumulo.policy.example examples hadoop-metrics2-accumulo.properties monitor_logger.properties tracers
-accumulo-site.xml gc log4j.properties monitor_logger.xml
-</code></pre></div></div>
-
-<p>While all of these files have a purpose, many are only used in rare situations. For Accumulo 2.0, the ‘conf/’
-directory now only contains a minimum set of configuration files needed to run Accumulo.</p>
-
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span><span class="nb">ls </span>accumulo-2.0.0/conf/
-accumulo-env.sh accumulo-site.xml client.conf log4j-monitor.properties log4j.properties log4j-service.properties templates
-</code></pre></div></div>
-
-<p>The Accumulo tarball does contain host files (i.e ‘tservers’, ‘monitor’, etc) by default as these files are only required by
-the ‘accumulo-cluster’ command. However, the script has a command to generate them.</p>
-
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span>./bin/accumulo-cluster create-config
-</code></pre></div></div>
-
-<p>Any less common configuration files can still be found in <code class="highlighter-rouge">conf/templates</code>.</p>
-
-<h3 id="better-usage">Better usage</h3>
-
-<p>Before 2.0.0, the ‘accumulo’ command had a limited usage:</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ ./accumulo-1.8.0/bin/accumulo
-accumulo admin | check-server-config | classpath | create-token | gc | help | info | init | jar &lt;jar&gt; [&lt;main class&gt;] args |
- login-info | master | minicluster | monitor | proxy | rfile-info | shell | tracer | tserver | version | zookeeper | &lt;accumulo class&gt; args
-</code></pre></div></div>
-
-<p>For 2.0.0, all ‘accumulo’ commands were given a short description and organized into the groups. Below is
-the full usage. It should be noted that usage is limited until the ‘accumulo-env.sh’ configuration file is
-created in <code class="highlighter-rouge">conf/</code> by the <code class="highlighter-rouge">accumulo create-config</code> command.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ ./accumulo-2.0.0/bin/accumulo help
-
-Usage: accumulo &lt;command&gt; [-h] (&lt;argument&gt; ...)
-
- -h Prints usage for specified command
-
-Core Commands:
- init Initializes Accumulo
- shell Runs Accumulo shell
- classpath Prints Accumulo classpath
- version Prints Accumulo version
- admin Executes administrative commands
- info Prints Accumulo cluster info
- help Prints usage
- &lt;main class&gt; args Runs Java &lt;main class&gt; located on Accumulo classpath
-
-Process Commands:
- gc Starts Accumulo garbage collector
- master Starts Accumulo master
- monitor Starts Accumulo monitor
- minicluster Starts Accumulo minicluster
- proxy Starts Accumulo proxy
- tserver Starts Accumulo tablet server
- tracer Starts Accumulo tracer
- zookeeper Starts Apache Zookeeper instance
-
-Advanced Commands:
- check-server-config Checks server config
- create-token Creates authentication token
- login-info Prints Accumulo login info
- rfile-info Prints rfile info
-</code></pre></div></div>
-
-<p>The new ‘accumulo-service’ and ‘accumulo-cluster’ commands also have informative usage.</p>
-
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ ./accumulo-2.0.0/bin/accumulo-service
-
-Usage: accumulo-service &lt;service&gt; &lt;command&gt;
-
-Services:
- gc Accumulo garbage collector
- monitor Accumulo monitor
- master Accumulo master
- tserver Accumulo tserver
- tracer Accumulo tracer
-
-Commands:
- start Starts service
- stop Stops service
- kill Kills service
-
-$ ./accumulo-2.0.0/bin/accumulo-cluster
-
-Usage: accumulo-cluster &lt;command&gt; (&lt;argument&gt; ...)
-
-Commands:
- create-config Creates cluster config
- start Starts Accumulo cluster
- stop Stops Accumulo cluster
- start-non-tservers Starts all services except tservers
- start-tservers Starts all tservers on cluster
- stop-tservers Stops all tservers on cluster
- start-here Starts all services on this node
- stop-here Stops all services on this node
-</code></pre></div></div>
-
-<p><em>This post was updated on March 24, 2017 to reflect changes to Accumulo 2.0</em></p>
-
-</description>
- <pubDate>Wed, 16 Nov 2016 00:00:00 -0500</pubDate>
- <link>https://accumulo.apache.org/blog/2016/11/16/simpler-scripts-and-config.html</link>
- <guid isPermaLink="true">https://accumulo.apache.org/blog/2016/11/16/simpler-scripts-and-config.html</guid>
-
-
- <category>blog</category>
-
- </item>
-
</channel>
</rss>
diff --git a/how-to-contribute/index.html b/how-to-contribute/index.html
index a1d2b36..55c77ca 100644
--- a/how-to-contribute/index.html
+++ b/how-to-contribute/index.html
@@ -165,9 +165,68 @@ the community before being merged by a committer.</p>
<h2 id="issues">Issues</h2>
-<p>Any contribution should have a corresponding issue. Accumulo uses <a href="https://issues.apache.org/jira/browse/ACCUMULO">JIRA</a> for issue tracking. Before creating an issue,
-you will need to create an <a href="https://issues.apache.org/jira/secure/Signup!default.jspa">Apache JIRA account</a>. If you need help finding an issue to work on, check out
-the <a href="https://s.apache.org/newbie_accumulo_tickets">open issues labeled for newbies</a> or <a href="/contact-us/">contact us</a>.</p>
+<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.</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>For pull request and issues, the following labels are used in the core
+repository. Consider an issue with labels <code class="highlighter-rouge">v1.9.3</code>, <code class="highlighter-rouge">v2.0.2</code>, and <code class="highlighter-rouge">bug</code>. If
+the issue is open, then its a bug that someone plans to fix in 1.9.3 and 2.0.2.
+If closed, then it was fixed in those versions.</p>
+
+<table>
+ <thead>
+ <tr>
+ <th>Label</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>blocker</td>
+ <td>Indicates a release blocker that must be fixed in labeled versions.</td>
+ </tr>
+ <tr>
+ <td>bug</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>duplicate</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>enhancement</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>vX.Y.Z</td>
+ <td>Fix version. The prefix <code class="highlighter-rouge">v</code> was chosen so that these labels sort last in the drop down list.</td>
+ </tr>
+ </tbody>
+</table>
+
+<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="repositories">Repositories</h2>
@@ -186,32 +245,32 @@ viewed by clicking on <code class="highlighter-rouge">contribute</code> in the L
<tbody>
<tr>
<td><a href="https://github.com/apache/accumulo">Accumulo</a></td>
- <td><a href="https://github.com/apache/accumulo/blob/master/CONTRIBUTING.md">contribute</a></td>
+ <td><a href="https://github.com/apache/accumulo/blob/master/CONTRIBUTING.md">Contribute</a> <a href="https://github.com/apache/accumulo/issues">Issues</a></td>
<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/blob/master/CONTRIBUTING.md">contribute</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/blob/master/CONTRIBUTING.md">contribute</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>
</tr>
<tr>
<td><a href="https://github.com/apache/accumulo-testing">Accumulo Testing</a></td>
- <td><a href="https://github.com/apache/accumulo-testing/blob/master/CONTRIBUTING.md">contribute</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>
</tr>
<tr>
<td><a href="https://github.com/apache/accumulo-docker">Accumulo Docker</a></td>
- <td><a href="https://github.com/apache/accumulo-docker/blob/master/CONTRIBUTING.md">contribute</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/blob/master/CONTRIBUTING.md">contribute</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>
</tr>
</tbody>
@@ -220,8 +279,8 @@ viewed by clicking on <code class="highlighter-rouge">contribute</code> in the L
<h2 id="contribution-workflow">Contribution workflow</h2>
<ol>
- <li>Create an <a href="https://issues.apache.org/jira/secure/Signup!default.jspa">Apache JIRA account</a> (for issue tracking) and <a href="https://github.com/join">GitHub account</a> (for pull requests).</li>
- <li>Find an <a href="https://s.apache.org/newbie_accumulo_tickets">issue</a> to work on or create one that describes the work that you want to do.</li>
+ <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><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
diff --git a/index.html b/index.html
index 218cb28..572cc0c 100644
--- a/index.html
+++ b/index.html
@@ -186,6 +186,13 @@
<div class="row latest-news-item">
<div class="col-sm-12" style="margin-bottom: 5px">
+ <span style="font-size: 12px; margin-right: 5px;">Mar 2018</span>
+ <a href="/blog/2018/03/08/moving-to-github-issues.html">Migrating to GitHub Issues</a>
+ </div>
+ </div>
+
+ <div class="row latest-news-item">
+ <div class="col-sm-12" style="margin-bottom: 5px">
<span style="font-size: 12px; margin-right: 5px;">Dec 2017</span>
<a href="/blog/2017/12/12/take-the-accumulo-tour.html">Take the Accumulo Tour!</a>
</div>
@@ -212,13 +219,6 @@
</div>
</div>
- <div class="row latest-news-item">
- <div class="col-sm-12" style="margin-bottom: 5px">
- <span style="font-size: 12px; margin-right: 5px;">Apr 2017</span>
- <a href="/release/accumulo-1.7.3/">Apache Accumulo 1.7.3</a>
- </div>
- </div>
-
<div id="news-archive-link">
<p>View all posts in the <a href="/news">news archive</a></p>
</div>
diff --git a/news/index.html b/news/index.html
index 064c2ea..08354b4 100644
--- a/news/index.html
+++ b/news/index.html
@@ -151,11 +151,22 @@
<div>
-<h3>2017</h3>
+<h3>2018</h3>
<div class="row" style="margin-top: 15px">
+ <div class="col-md-1">Mar 08</div>
+ <div class="col-md-10"><a href="/blog/2018/03/08/moving-to-github-issues.html">Migrating to GitHub Issues</a></div>
+ </div>
+
+
+
+
+ <hr />
+ <h3>2017</h3>
+
+ <div class="row" style="margin-top: 15px">
<div class="col-md-1">Dec 12</div>
<div class="col-md-10"><a href="/blog/2017/12/12/take-the-accumulo-tour.html">Take the Accumulo Tour!</a></div>
</div>
diff --git a/tour/index.html b/tour/index.html
index 2e36887..9810e20 100644
--- a/tour/index.html
+++ b/tour/index.html
@@ -161,7 +161,7 @@ own. The answers to an exercise are typically provided in the next step. The to
<p>When on a tour page, the left and right keys on the keyboard can be used to navigate. If you have any questions
or suggestions while going through the tour, please send an email to our <a href="/contact-us/#mailing-lists">mailing list</a>
-or <a href="https://issues.apache.org/jira/projects/ACCUMULO">create an issue</a>.</p>
+or <a href="https://github.com/apache/accumulo-website/issues">create an issue</a>.</p>
<ol>
<li>
--
To stop receiving notification emails like this one, please contact
kturner@apache.org.