Repository: yetus Updated Branches: refs/heads/asf-site 4c59616c1 -> 4a356e40f
http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/documentation/in-progress/precommit-patchnames/index.html ---------------------------------------------------------------------- diff --git a/documentation/in-progress/precommit-patchnames/index.html b/documentation/in-progress/precommit-patchnames/index.html index 92a1138..9d03030 100644 --- a/documentation/in-progress/precommit-patchnames/index.html +++ b/documentation/in-progress/precommit-patchnames/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/documentation/in-progress/precommit-qbt/index.html ---------------------------------------------------------------------- diff --git a/documentation/in-progress/precommit-qbt/index.html b/documentation/in-progress/precommit-qbt/index.html index b8be172..1d3bf67 100644 --- a/documentation/in-progress/precommit-qbt/index.html +++ b/documentation/in-progress/precommit-qbt/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> @@ -136,12 +135,12 @@ scheduled build as part of your overall development strategy.</p> <code>--console-report-file</code> option to send the summary email to a file. This can then be used with systems like Jenkin’s email-ext plug-in to send the output as an emailed report:</p> -<pre class="highlight plaintext"><code>${FILE,path="<report-file-path>"} -</code></pre> +<div class="highlight"><pre class="highlight plaintext"><code>${FILE,path="<report-file-path>"} +</code></pre></div> <p>For something a bit more structured, there is also the <code>--html-report-file</code> option. Using this output, again with Jenkins’ email-ext plug-in, it is possible to build some very nice looking output that is easily customized:</p> -<pre class="highlight html"><code><span class="nt"><html></span> +<div class="highlight"><pre class="highlight html"><code><span class="nt"><html></span> <span class="nt"><head></span> <span class="nt"><style></span> <span class="nt">table</span> <span class="p">{</span> @@ -159,7 +158,7 @@ possible to build some very nice looking output that is easily customized:</p> <span class="nt"><p></p></span> ${FILE,path="<span class="nt"><report-file-path></span>"} <span class="nt"></body></html></span> -</code></pre> +</code></pre></div> <p>If your mailing lists do not allow HTML-formatted email, then the <code>--brief-report-file</code> provides a solution. This option creates a very plain, reduced content text file suitable for email. It contains just the barebones information needed to get http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/documentation/in-progress/precommit-smart-apply-patch/index.html ---------------------------------------------------------------------- diff --git a/documentation/in-progress/precommit-smart-apply-patch/index.html b/documentation/in-progress/precommit-smart-apply-patch/index.html index 42e26e5..d35539e 100644 --- a/documentation/in-progress/precommit-smart-apply-patch/index.html +++ b/documentation/in-progress/precommit-smart-apply-patch/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> @@ -128,16 +127,16 @@ <h1 id="usage">Usage</h1> <p>Its simplest form is used when a patch is stored in a local file:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>smart-apply-patch patch -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>smart-apply-patch patch +</code></pre></div> <p>This will cause the command to run through various ways to verify and then apply the patch to the current repo, including deducing a patch level.</p> <p>Perhaps you just want to see if the patch even applies without changing your local repo. The <code>--dry-run</code> option will just test for applicability:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>smart-apply-patch --dry-run patch -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>smart-apply-patch <span class="nt">--dry-run</span> patch +</code></pre></div> <p>For committers of projects, there is a special mode:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>smart-apply-patch --committer patch -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>smart-apply-patch <span class="nt">--committer</span> patch +</code></pre></div> <p>that in addition to applying the patch will also attempt to:</p> <ul> http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/documentation/in-progress/precommit-testformats/index.html ---------------------------------------------------------------------- diff --git a/documentation/in-progress/precommit-testformats/index.html b/documentation/in-progress/precommit-testformats/index.html index ea8092d..0586f24 100644 --- a/documentation/in-progress/precommit-testformats/index.html +++ b/documentation/in-progress/precommit-testformats/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> @@ -124,8 +123,8 @@ <h1 id="test-format-support">Test Format Support</h1> <p>test-patch has the ability to support multiple test formats. Test formats have some extra hooks to process the output of test tools and write the results to some tables. Every test format plug-in must have one line in order to be recognized:</p> -<pre class="highlight shell"><code>add_test_format <pluginname> -</code></pre> +<div class="highlight"><pre class="highlight shell"><code>add_test_format <pluginname> +</code></pre></div> <p>Test format plugins can provide following two methods, which will be called by test-patch if defined.</p> <ul> http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/documentation/in-progress/releasedocmaker/index.html ---------------------------------------------------------------------- diff --git a/documentation/in-progress/releasedocmaker/index.html b/documentation/in-progress/releasedocmaker/index.html index 3ba9762..9a3cb2b 100644 --- a/documentation/in-progress/releasedocmaker/index.html +++ b/documentation/in-progress/releasedocmaker/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> @@ -162,8 +161,8 @@ <h1 id="basic-usage">Basic Usage</h1> <p>Minimally, the name of the JIRA project and a version registered in JIRA must be provided:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project <span class="o">(</span>project<span class="o">)</span> --version <span class="o">(</span>version<span class="o">)</span> -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> <span class="o">(</span>project<span class="o">)</span> <span class="nt">--version</span> <span class="o">(</span>version<span class="o">)</span> +</code></pre></div> <p>This will query Apache JIRA, generating two files in a directory named after the given version in an extended markdown format which can be processed by both mvn site and GitHub.</p> <ul> @@ -179,44 +178,52 @@ <p>If your JIRA project supports the release note field, this will contain any JIRA mentioned in the CHANGELOG that is either an incompatible change or has a release note associated with it. If your JIRA project does not support the release notes field, this will be the description field.</p> <p>For example, to build the release documentation for HBase v1.2.0:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.2.0 -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.2.0 +</code></pre></div> <p>By default, release notes are expected to be in plain text. However, you can write them in markdown if you include a header at the top of your release note:</p> -<pre class="highlight xml"><code><span class="c"><!-- markdown --></span> +<div class="highlight"><pre class="highlight xml"><code><span class="c"><!-- markdown --></span> remaining text -</code></pre> +</code></pre></div> +<h1 id="authentication">Authentication</h1> + +<p>releasedocmaker supports very simple Basic authentication. This is accomplished by adding two environment variables to your shell environment:</p> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">RDM_JIRA_USERNAME</span><span class="o">=</span><span class="s1">'jirausername'</span> +<span class="nv">RDM_JIRA_PASSWORD</span><span class="o">=</span><span class="s1">'jirapassword'</span> +</code></pre></div> +<p>These values will be added to all requests destined for the JIRA server.</p> + <h1 id="changing-the-header">Changing the Header</h1> <p>By default, it will use a header that matches the project name. But that is kind of ugly and the case may be wrong. Luckily, the title can be changed:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.2.0 --projecttitle <span class="s2">"Apache HBase"</span> -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.2.0 <span class="nt">--projecttitle</span> <span class="s2">"Apache HBase"</span> +</code></pre></div> <p>Now instead of <q>HBASE</q>, it will use <q>Apache HBase</q> for some titles and headers.</p> <h1 id="versioned-files-and-directories">Versioned Files and Directories</h1> <p>It is sometimes useful to create the CHANGELOG and RELEASENOTES with versions attached. <code>releasedocmaker</code> supports both independently.</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.2.0 --fileversions -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.2.0 <span class="nt">--fileversions</span> +</code></pre></div> <p>This command line will now create CHANGELOG.1.2.0.md and RELEASENOTES.1.2.0.md files.</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.2.0 --dirversions -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.2.0 <span class="nt">--dirversions</span> +</code></pre></div> <p>This command line will now create a directory called 1.2.0 and inside will be the CHANGELOG.md and RELEASENOTES.md files.</p> <p>Using both at the same time…</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.2.0 --fileversions --dirversions -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.2.0 <span class="nt">--fileversions</span> <span class="nt">--dirversions</span> +</code></pre></div> <p>… results in 1.2.0/CHANGELOG.1.2.0.md and 1.2.0/RELEASENOTES.1.2.0.md files.</p> <h1 id="multiple-versions">Multiple Versions</h1> <p>Using either <code>--dirversions</code> or <code>--fileversions</code> or both simultaneously, <code>releasedocmaker</code> can also generate multiple versions at once</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.0.0 --version 1.2.0 --dirversions -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.0.0 <span class="nt">--version</span> 1.2.0 <span class="nt">--dirversions</span> +</code></pre></div> <p>This will create the files for versions 1.0.0 and versions 1.2.0 in their own directories.</p> <p>But what if the version numbers are not known? releasedocmaker can also generate version data based upon ranges:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.0.0 --version 1.2.0 --range --fileversions -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.0.0 <span class="nt">--version</span> 1.2.0 <span class="nt">--range</span> <span class="nt">--fileversions</span> +</code></pre></div> <p>In this form, releasedocmaker will query JIRA, discover all versions that alphabetically appear to be between 1.0.0 and 1.2.0, inclusive, and generate all of the relative release documents. This is especially useful when bootstrapping an existing project.</p> <h1 id="unreleased-dates">Unreleased Dates</h1> @@ -224,8 +231,8 @@ remaining text <p>For released versions, releasedocmaker will pull the date of the release from JIRA. However, for unreleased versions it marks the release as <q>Unreleased</q>. This can be inconvenient when actually building a release and wanting to include it inside the source package.</p> <p>The –usetoday option can be used to signify that instead of using Unreleased, releasedocmaker should use today’s date.</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.0.0 --usetoday -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.0.0 <span class="nt">--usetoday</span> +</code></pre></div> <p>After using this option and release, don’t forget to change JIRA’s release date to match!</p> <h1 id="sorted-output">Sorted Output</h1> @@ -235,23 +242,23 @@ remaining text <h2 id="resolution-date-base-sort">Resolution Date-base Sort</h2> <p>By default, releasedocmaker will sort the output based upon the resolution date of the issue starting with older resolutions. This is the same as giving these options:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project falcon --version 0.6 --sorttype resolutiondate --sortorder older -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> falcon <span class="nt">--version</span> 0.6 <span class="nt">--sorttype</span> resolutiondate <span class="nt">--sortorder</span> older +</code></pre></div> <p>The order can be reversed so that newer issues appear on top by providing the ‘newer’ flag:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project falcon --version 0.6 --sorttype resolutiondate --sortorder newer -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> falcon <span class="nt">--version</span> 0.6 <span class="nt">--sorttype</span> resolutiondate <span class="nt">--sortorder</span> newer +</code></pre></div> <p>In the case of multiple projects given on the command line, the projects will be interspersed.</p> <h2 id="issue-number-based-sort">Issue Number-based Sort</h2> <p>An alternative to the date-based sort is to sort based upon the issue id. This may be accomplished via:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project falcon --version 0.6 --sorttype issueid --sortorder asc -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> falcon <span class="nt">--version</span> 0.6 <span class="nt">--sorttype</span> issueid <span class="nt">--sortorder</span> asc +</code></pre></div> <p>This will now sort by the issue id, listing them in lowest to highest (or ascending) order.</p> <p>The order may be reversed to list them in highest to lowest (or descending) order by providing the appropriate flag:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project falcon --version 0.6 --sorttype issueid --sortorder desc -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> falcon <span class="nt">--version</span> 0.6 <span class="nt">--sorttype</span> issueid <span class="nt">--sortorder</span> desc +</code></pre></div> <p>In the case of multiple projects given on the command line, the projects will be grouped and then sorted by issue id.</p> <h1 id="backward-incompatible-changes">Backward Incompatible Changes</h1> @@ -259,18 +266,18 @@ remaining text <p>To check if an issue is backward-incompatible the releasedocmaker script first checks the <q>Hadoop Flags</q> field in the issue. If this field is found to be blank then it searches for the ‘backward-incompatible’ label. You can override the default value for this label by using –incompatiblelabel option e.g.</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project falcon --version 0.6 --incompatiblelabel not-compatible -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> falcon <span class="nt">--version</span> 0.6 <span class="nt">--incompatiblelabel</span> not-compatible +</code></pre></div> <p>or equivalently using the shorter -X option</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project falcon --version 0.6 -X not-compatible -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> falcon <span class="nt">--version</span> 0.6 <span class="nt">-X</span> not-compatible +</code></pre></div> <h1 id="lint-mode">Lint Mode</h1> <p>In order to ensure proper formatting while using mvn site, releasedocmaker puts in periods (.) for fields that are empty or unassigned. This can be unsightly and not proper for any given project. There are also other things, such as missing release notes for incompatible changes, that are less than desirable.</p> <p>In order to help release managers from having to scan through potentially large documents, releasedocmaker features a lint mode, triggered via –lint:</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker --project HBASE --version 1.0.0 --lint -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">--project</span> HBASE <span class="nt">--version</span> 1.0.0 <span class="nt">--lint</span> +</code></pre></div> <p>This will do the normal JIRA querying, looking for items it considers problematic. It will print the information to the screen and then exit with either success or failure, depending upon if any issues were discovered.</p> <h1 id="index-mode">Index Mode</h1> @@ -286,8 +293,8 @@ For example directories with names like 0.6, 1.2.2, 1.2alpha etc. will all be li <h1 id="release-version">Release Version</h1> <p>You can find the version of the releasedocmaker that you are using by giving the -V option. This may be helpful in finding documentation for the version you are using.</p> -<pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker -V -</code></pre> +<div class="highlight"><pre class="highlight shell"><code><span class="nv">$ </span>releasedocmaker <span class="nt">-V</span> +</code></pre></div> </div> <div class="container"> <hr> http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/downloads/index.html ---------------------------------------------------------------------- diff --git a/downloads/index.html b/downloads/index.html index 6ef1d93..6d7c2d6 100644 --- a/downloads/index.html +++ b/downloads/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> @@ -134,6 +133,14 @@ third-party repositories (e.g. Maven Central).</p> <h2 id="releases">Releases</h2> <ul> +<li>0.8.0 + +<ul> +<li><a href="/documentation/0.8.0/RELEASENOTES">Release Notes</a></li> +<li><a href="/documentation/0.8.0/CHANGELOG">CHANGELOG</a></li> +<li>Source : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.8.0/yetus-0.8.0-src.tar.gz";>yetus-0.8.0-src.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.8.0/yetus-0.8.0-src.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.8.0/yetus-0.8.0-src.tar.gz.mds";>hashes</a>)</li> +<li>Binaries : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.8.0/yetus-0.8.0-bin.tar.gz";>yetus-0.8.0-bin.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.8.0/yetus-0.8.0-bin.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.8.0/yetus-0.8.0-bin.tar.gz.mds";>hashes</a>)</li> +</ul></li> <li>0.7.0 <ul> @@ -150,28 +157,12 @@ third-party repositories (e.g. Maven Central).</p> <li>Source : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.6.0/yetus-0.6.0-src.tar.gz";>yetus-0.6.0-src.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.6.0/yetus-0.6.0-src.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.6.0/yetus-0.6.0-src.tar.gz.mds";>hashes</a>)</li> <li>Binaries : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.6.0/yetus-0.6.0-bin.tar.gz";>yetus-0.6.0-bin.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.6.0/yetus-0.6.0-bin.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.6.0/yetus-0.6.0-bin.tar.gz.mds";>hashes</a>)</li> </ul></li> -<li>0.5.0 - -<ul> -<li><a href="/documentation/0.5.0/RELEASENOTES">Release Notes</a></li> -<li><a href="/documentation/0.5.0/CHANGELOG">CHANGELOG</a></li> -<li>Source : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.5.0/yetus-0.5.0-src.tar.gz";>yetus-0.5.0-src.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.5.0/yetus-0.5.0-src.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.5.0/yetus-0.5.0-src.tar.gz.mds";>hashes</a>)</li> -<li>Binaries : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.5.0/yetus-0.5.0-bin.tar.gz";>yetus-0.5.0-bin.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.5.0/yetus-0.5.0-bin.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.5.0/yetus-0.5.0-bin.tar.gz.mds";>hashes</a>)</li> -</ul></li> -<li>0.4.0 - -<ul> -<li><a href="/documentation/0.4.0/RELEASENOTES">Release Notes</a></li> -<li><a href="/documentation/0.4.0/CHANGELOG">CHANGELOG</a></li> -<li>Source : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.4.0/yetus-0.4.0-src.tar.gz";>yetus-0.4.0-src.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.4.0/yetus-0.4.0-src.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.4.0/yetus-0.4.0-src.tar.gz.mds";>hashes</a>)</li> -<li>Binaries : <a href="https://www.apache.org/dyn/closer.lua?path=/yetus/0.4.0/yetus-0.4.0-bin.tar.gz";>yetus-0.4.0-bin.tar.gz</a> (<a href="https://www.apache.org/dist/yetus/0.4.0/yetus-0.4.0-bin.tar.gz.asc";>signature</a>, <a href="https://www.apache.org/dist/yetus/0.4.0/yetus-0.4.0-bin.tar.gz.mds";>hashes</a>)</li> -</ul></li> </ul> <p>The latest version of Apache Yetus is also available via Homebrew on Mac OS X:</p> -<pre class="highlight shell"><code>brew tap apache/yetus https://github.com/apache/yetus -brew install yetus -</code></pre> +<div class="highlight"><pre class="highlight shell"><code>brew tap apache/yetus https://github.com/apache/yetus +brew <span class="nb">install </span>yetus +</code></pre></div> <p>This will install many of the dependencies needed for the precommit functionality as well.</p> </div> http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/index.html ---------------------------------------------------------------------- diff --git a/index.html b/index.html index 6306757..16c7c62 100644 --- a/index.html +++ b/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul> http://git-wip-us.apache.org/repos/asf/yetus/blob/4a356e40/mailinglists/index.html ---------------------------------------------------------------------- diff --git a/mailinglists/index.html b/mailinglists/index.html index 4550df7..96ccd37 100644 --- a/mailinglists/index.html +++ b/mailinglists/index.html @@ -53,10 +53,9 @@ <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation <span class="caret"></span></a> <ul class="dropdown-menu" role="menu"> - <li><a href="/documentation/0.4.0/">Docs for v0.4.0</a></li> - <li><a href="/documentation/0.5.0/">Docs for v0.5.0</a></li> <li><a href="/documentation/0.6.0/">Docs for v0.6.0</a></li> <li><a href="/documentation/0.7.0/">Docs for v0.7.0</a></li> + <li><a href="/documentation/0.8.0/">Docs for v0.8.0</a></li> <li><a href="/documentation/in-progress/">In Progress Docs for Contributors</a> </li> </ul>
