This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 971de02 Automatic Site Publish by Buildbot
971de02 is described below
commit 971de025bd7652dbf9f365c64bc29a1ffcb59e78
Author: buildbot <us...@infra.apache.org>
AuthorDate: Fri Sep 25 17:11:33 2020 +0000
Automatic Site Publish by Buildbot
---
output/contributor/making-release.html | 62 +++++++++++++++++++---------------
output/feed.xml | 4 +--
2 files changed, 36 insertions(+), 30 deletions(-)
diff --git a/output/contributor/making-release.html
b/output/contributor/making-release.html
index 4fc2566..dfafa1f 100644
--- a/output/contributor/making-release.html
+++ b/output/contributor/making-release.html
@@ -155,11 +155,13 @@
<p>There are number of things that are required before attempting to build a
release.</p>
<ol>
- <li>Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via
.gnupg/gpg-agent.conf) to ensure that the agent doesn’t require
re-authentication mid-build, as it will cause things to fail. For example, you
can add <code class="language-plaintext highlighter-rouge">default-cache-ttl
6000</code> to increase the timeout from the default of 10 minutes to over an
hour. If you do not have a GPG key, reference the very thorough <a
href="https://www.apache.org/dev/release-signing"; [...]
- <li>Ensure that you’re using the correct major release of Java (check
javadoc too).</li>
+ <li>Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via
.gnupg/gpg-agent.conf) to ensure that the agent doesn’t require
re-authentication mid-build, as it will cause things to fail. For example, you
can add <code class="language-plaintext highlighter-rouge">default-cache-ttl
6000</code> to increase the timeout from the default of 10 minutes to over an
hour. If you do not have a GPG key, reference the very thorough <a
href="https://infra.apache.org/release-signing";>A [...]
+ <li>Once you are able to sign a release, add your gpg key to the <a
href="https://downloads.apache.org/accumulo/KEYS";>KEYS file</a> (instructions
are at the top of the file). This will require updating the SVN repository
(more below).</li>
<li>Ensure that you’re building Apache Accumulo with a username that has the
same name as your Apache ID (this is due to
-the maven-release-plugin and staging the release candidate).</li>
+the maven-release-plugin and staging the release candidate). Your Apache ID
and password should be in a <server> section of ~/.m2/settings.xml as shown
[here][apache-mvn].
+To encrypt the password follow these [instructions][maven-enc].</server></li>
<li>Have a clean workspace before starting.</li>
+ <li>The build will require having the same version of <a
href="http://archive.apache.org/dist/thrift/";>Thrift binary</a> installed on
your machine.</li>
</ol>
<p>Given all of this, it’s recommended that you only attempt making a release
from a GNU/Linux machine.</p>
@@ -173,25 +175,24 @@ the maven-release-plugin and staging the release
candidate).</li>
<p><strong>TL;DR</strong></p>
<ul>
- <li><code class="language-plaintext highlighter-rouge">./assemble/build.sh
--create-release-candidate</code> to make the release candidate</li>
- <li><code class="language-plaintext highlighter-rouge">git tag $version
$version-rcN</code> to create an RC tag from the actual tag</li>
- <li><code class="language-plaintext highlighter-rouge">git tag -d
$version</code> make sure you don’t accidentally push a “release” tag</li>
- <li><code class="language-plaintext highlighter-rouge">git push origin
$version-rcN</code> push the RC tag</li>
- <li><code class="language-plaintext highlighter-rouge">git checkout -b
$version-rcN-branch</code> save off the branch from the Maven release
plugin</li>
- <li><strong>VOTE</strong></li>
+ <li><code class="language-plaintext highlighter-rouge">./assemble/build.sh
--create-release-candidate</code> to make the release candidate.</li>
+ <li>Verify the artifacts in <a
href="https://repository.apache.org/#stagingRepositories";>ASF Nexus</a> and if
valid, close the staging repo.</li>
+ <li>Enter the #### of the staging repo when the script prompts to generate
the VOTE email.</li>
+ <li><code class="language-plaintext highlighter-rouge">git push upstream
x.y.z-rc#</code> if your git <em>upstream</em> is different from
<em>origin</em></li>
+ <li><code class="language-plaintext highlighter-rouge">git push upstream
x.y.z-rc#-next</code> push new branches to the upstream git repo. (script
pushes to <em>origin</em>)</li>
+ <li>Remove any <em>Expected fingerprints</em> generated in the email that do
not match your gpg fingerprint.</li>
+ <li>Verify email links are valid and email <em>d...@accumulo.apache.org</em>
starting the VOTE.</li>
+ <li><strong><a href="#vote">VOTE</a></strong></li>
<li><em>If vote fails</em>, fix the original branch and start over.</li>
- <li><em>If vote passes</em>, <code class="language-plaintext
highlighter-rouge">git merge $version-rcN-branch</code> back into the original
branch you released from.</li>
- <li><code class="language-plaintext highlighter-rouge">git tag -s
$version-rcN $version</code> make a GPG-signed tag</li>
- <li><code class="language-plaintext highlighter-rouge">git push origin
$version</code> push the signed tag.</li>
+ <li><em>If vote passes</em>, <code class="language-plaintext
highlighter-rouge">git merge x.y.z-rc#-next</code> back into the original
branch you released from.</li>
+ <li>Go to the <a href="#post-release-tasks">Post release tasks</a></li>
</ul>
-<p><strong>Long-winded explanation</strong></p>
+<p><strong>Explanation of build script</strong></p>
-<p>You should use the provided script assemble/build.sh to create the release
candidate. This script is
+<p>You should run <code class="language-plaintext
highlighter-rouge">assemble/build.sh --create-release-candidate</code> to
create the release candidate. This script is
desirable as it activates all necessary maven profiles in addition to
verifying that certain preconditions
-are met, like RPM signing availability and the ability to sign files using
GPG. The –test option can
-be used as a dry run for creating a release candidate. The
–create-release-candidate option should be
-used to create the actual release candidate.</p>
+are met. If successful, it will also generate a release VOTE email.</p>
<p>When invoking build.sh with the –create-release-candidate option, the
majority of the work will be performed
by the maven-release-plugin, invoking <em>release:clean</em>,
<em>release:prepare</em>, and <em>release:perform</em>. These will
@@ -202,11 +203,9 @@ voting to occur on artifacts that cannot be directly
promoted. After the build.s
likely take at least 15 minutes, even on recent hardware), your current branch
will be on the “next” version
that you provided to the release plugin.</p>
-<p>One unwanted side-effect of this approach is that after creating this
branch, but <em>before invoking release:perform</em>,
-you must edit the release.properties to add the <em>-rcN</em> suffix to the
value of scm.tag. Otherwise, the release
-plugin will complain that it cannot find the branch for the release. With a
successful invocation of <em>mvn release:perform</em>,
-a staging repository will be made for you on the <a
href="https://repository.apache.org";>ASF Nexus server</a> which you can log
into with your ASF
-credentials.</p>
+<p>With a successful invocation of <em>mvn release:perform</em>, a staging
repository will be made for you on the
+<a href="https://repository.apache.org/#stagingRepositories";>ASF Nexus
server</a> which you can log into with your ASF credentials. The script will
prompt for the
+generated number at the end of the staging repository name, i.e. 1086 for
<code class="language-plaintext
highlighter-rouge">orgapacheaccumulo-1086</code>.</p>
<p>After you log into Nexus, click on <em>Staging Repositories</em> in the
<em>Build Promotion</em> toolbar on the left side of
the screen. Assuming your build went according to plan, you should have a new
staging repository made for
@@ -242,7 +241,7 @@ announcement.</p>
a process to get the release out to all of the mirrors.
In Nexus:</p>
<ul>
- <li>Release the 1.9.3-rc3 staging repository to Maven Central</li>
+ <li>For example, rc3 passes. Release the X.Y.Z-rc3 staging repository to
Maven Central</li>
<li>Drop old (rc1,rc2) staging repos</li>
</ul>
@@ -253,6 +252,16 @@ should also be signed with your GPG key. To ensure proper
retention on release (
requirements), This final tag <em>must</em> being with “rel/”. For example, a
release of 1.7.0 should have a corresponding
tag name of “rel/1.7.0”.</p>
+<p>Run the command in the email generated from the <code
class="language-plaintext highlighter-rouge">assemble/build.sh</code> script.
It will be something like:</p>
+<ul>
+ <li><code class="language-plaintext highlighter-rouge">git tag -f -m 'Apache
Accumulo 1.10.0' -s rel/1.10.0 4d261254</code></li>
+</ul>
+
+<p>Then push the signed tag. For example:</p>
+<ul>
+ <li><code class="language-plaintext highlighter-rouge">git push upstream
rel/1.10.0</code></li>
+</ul>
+
<h2 id="copy-artifacts-to-distapacheorg">Copy artifacts to dist.apache.org</h2>
<p>An SVN server is running at
https://dist.apache.org/repos/dist/release/accumulo. You need to upload the
release
@@ -357,12 +366,9 @@ if this is the latest release of Accumulo.</p>
<h2 id="references">References</h2>
-<p>Some good references that explain a few things:</p>
-
<ul>
- <li><a
href="https://mail-archives.apache.org/mod_mbox/accumulo-dev/201305.mbox/raw/%3CCAL5zq9bH8y0FyjXmmfXhWPj8axosn9dZ7%2Bu-R1DK4Y-WM1YoWg%40mail.gmail.com%3E";>Christopher
talks about making releases</a></li>
- <li><a
href="https://www.apache.org/dev/publishing-maven-artifacts";>Publishing Maven
Artifacts</a></li>
- <li><a href="https://www.apache.org/dev/release-publishing";>Publishing
Releases</a></li>
+ <li><a
href="https://infra.apache.org/publishing-maven-artifacts.html";>Publishing
Maven Artifacts</a></li>
+ <li><a href="https://infra.apache.org/release-publishing";>Publishing
Releases</a></li>
</ul>
diff --git a/output/feed.xml b/output/feed.xml
index 5cc475a..64e00ea 100644
--- a/output/feed.xml
+++ b/output/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, 15 Sep 2020 17:49:39 +0000</pubDate>
- <lastBuildDate>Tue, 15 Sep 2020 17:49:39 +0000</lastBuildDate>
+ <pubDate>Fri, 25 Sep 2020 17:11:27 +0000</pubDate>
+ <lastBuildDate>Fri, 25 Sep 2020 17:11:27 +0000</lastBuildDate>
<generator>Jekyll v4.1.1</generator>
