This is an automated email from the ASF dual-hosted git repository.
zabetak pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/calcite-site.git
The following commit(s) were added to refs/heads/master by this push:
new 5e87f70 Site: Remove '(for Calcite committers)' suffix from headers
in section dedicated to committers
5e87f70 is described below
commit 5e87f70a654b9234580a73fd1224b56d3c72265b
Author: Stamatis Zampetakis <[email protected]>
AuthorDate: Fri Jul 3 11:12:02 2020 +0200
Site: Remove '(for Calcite committers)' suffix from headers in section
dedicated to committers
---
docs/howto.html | 40 ++++++++++++++++++++--------------------
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/docs/howto.html b/docs/howto.html
index ac8e78f..5dacee1 100644
--- a/docs/howto.html
+++ b/docs/howto.html
@@ -118,26 +118,26 @@ adapters.</p>
</ul>
</li>
<li><a href="#advanced-topics-for-committers"
id="markdown-toc-advanced-topics-for-committers">Advanced topics for
committers</a> <ul>
- <li><a
href="#managing-calcite-repositories-through-github-for-calcite-committers"
id="markdown-toc-managing-calcite-repositories-through-github-for-calcite-committers">Managing
Calcite repositories through GitHub (for Calcite committers)</a></li>
- <li><a href="#merging-pull-requests-for-calcite-committers"
id="markdown-toc-merging-pull-requests-for-calcite-committers">Merging pull
requests (for Calcite committers)</a></li>
- <li><a href="#set-up-pgp-signing-keys-for-calcite-committers"
id="markdown-toc-set-up-pgp-signing-keys-for-calcite-committers">Set up PGP
signing keys (for Calcite committers)</a></li>
- <li><a
href="#set-up-nexus-repository-credentials-for-calcite-committers"
id="markdown-toc-set-up-nexus-repository-credentials-for-calcite-committers">Set
up Nexus repository credentials (for Calcite committers)</a></li>
- <li><a href="#making-a-snapshot-for-calcite-committers"
id="markdown-toc-making-a-snapshot-for-calcite-committers">Making a snapshot
(for Calcite committers)</a></li>
- <li><a href="#making-a-release-candidate-for-calcite-committers"
id="markdown-toc-making-a-release-candidate-for-calcite-committers">Making a
release candidate (for Calcite committers)</a> <ul>
+ <li><a href="#managing-calcite-repositories-through-github"
id="markdown-toc-managing-calcite-repositories-through-github">Managing Calcite
repositories through GitHub</a></li>
+ <li><a href="#merging-pull-requests"
id="markdown-toc-merging-pull-requests">Merging pull requests</a></li>
+ <li><a href="#set-up-pgp-signing-keys"
id="markdown-toc-set-up-pgp-signing-keys">Set up PGP signing keys</a></li>
+ <li><a href="#set-up-nexus-repository-credentials"
id="markdown-toc-set-up-nexus-repository-credentials">Set up Nexus repository
credentials</a></li>
+ <li><a href="#making-a-snapshot"
id="markdown-toc-making-a-snapshot">Making a snapshot</a></li>
+ <li><a href="#making-a-release-candidate"
id="markdown-toc-making-a-release-candidate">Making a release candidate</a>
<ul>
<li><a
href="#to-prepare-a-release-candidate-directly-in-your-environment"
id="markdown-toc-to-prepare-a-release-candidate-directly-in-your-environment">To
prepare a release candidate directly in your environment:</a> <ul>
<li><a href="#checking-the-artifacts"
id="markdown-toc-checking-the-artifacts">Checking the artifacts</a></li>
</ul>
</li>
</ul>
</li>
- <li><a
href="#cleaning-up-after-a-failed-release-attempt-for-calcite-committers"
id="markdown-toc-cleaning-up-after-a-failed-release-attempt-for-calcite-committers">Cleaning
up after a failed release attempt (for Calcite committers)</a></li>
+ <li><a href="#cleaning-up-after-a-failed-release-attempt"
id="markdown-toc-cleaning-up-after-a-failed-release-attempt">Cleaning up after
a failed release attempt</a></li>
<li><a href="#validate-a-release"
id="markdown-toc-validate-a-release">Validate a release</a></li>
- <li><a
href="#get-approval-for-a-release-via-apache-voting-process-for-calcite-committers"
id="markdown-toc-get-approval-for-a-release-via-apache-voting-process-for-calcite-committers">Get
approval for a release via Apache voting process (for Calcite
committers)</a></li>
- <li><a href="#publishing-a-release-for-calcite-committers"
id="markdown-toc-publishing-a-release-for-calcite-committers">Publishing a
release (for Calcite committers)</a> <ul>
+ <li><a href="#get-approval-for-a-release-via-apache-voting-process"
id="markdown-toc-get-approval-for-a-release-via-apache-voting-process">Get
approval for a release via Apache voting process</a></li>
+ <li><a href="#publishing-a-release"
id="markdown-toc-publishing-a-release">Publishing a release</a> <ul>
<li><a href="#publishing-directly-in-your-environment"
id="markdown-toc-publishing-directly-in-your-environment">Publishing directly
in your environment:</a></li>
</ul>
</li>
- <li><a href="#publish-the-web-site"
id="markdown-toc-publish-the-web-site">Publishing the web site (for Calcite
committers)</a></li>
+ <li><a href="#publish-the-web-site"
id="markdown-toc-publish-the-web-site">Publishing the web site</a></li>
</ul>
</li>
</ul>
@@ -576,7 +576,7 @@ need to be re-generated only every build, only when the
schema changes.</p>
<p>The following sections are of interest to Calcite committers and in
particular release managers.</p>
-<h2
id="managing-calcite-repositories-through-github-for-calcite-committers">Managing
Calcite repositories through GitHub (for Calcite committers)</h2>
+<h2 id="managing-calcite-repositories-through-github">Managing Calcite
repositories through GitHub</h2>
<p>Committers have write access to Calcite’s
<a href="https://gitbox.apache.org/repos/asf#calcite";>ASF git repositories</a>
hosting
@@ -604,7 +604,7 @@ protocol that you are using (HTTPS vs. SSH).</li>
<li>Accept the invitation and verify that you are a <a
href="https://github.com/orgs/apache/teams/calcite-committers/members";>member
of the team</a>.</li>
</ul>
-<h2 id="merging-pull-requests-for-calcite-committers">Merging pull requests
(for Calcite committers)</h2>
+<h2 id="merging-pull-requests">Merging pull requests</h2>
<p>These are instructions for a Calcite committer who has reviewed a pull
request
from a contributor, found it satisfactory, and is about to merge it to master.
@@ -643,7 +643,7 @@ which resolves the issue (in GitHub or GitBox), and also
thank the contributor
for their contribution.</li>
</ul>
-<h2 id="set-up-pgp-signing-keys-for-calcite-committers">Set up PGP signing
keys (for Calcite committers)</h2>
+<h2 id="set-up-pgp-signing-keys">Set up PGP signing keys</h2>
<p>Follow instructions <a
href="https://www.apache.org/dev/release-signing";>here</a> to
create a key pair. (On macOS, I did <code class="highlighter-rouge">brew
install gpg</code> and
@@ -656,7 +656,7 @@ file by following instructions in the <code
class="highlighter-rouge">KEYS</code
ball because that would be
<a
href="https://issues.apache.org/jira/browse/CALCITE-1746";>redundant</a>.)</p>
-<h2 id="set-up-nexus-repository-credentials-for-calcite-committers">Set up
Nexus repository credentials (for Calcite committers)</h2>
+<h2 id="set-up-nexus-repository-credentials">Set up Nexus repository
credentials</h2>
<p>Gradle provides multiple ways to <a
href="https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties";>configure
project properties</a>.
For instance, you could update <code
class="highlighter-rouge">$HOME/.gradle/gradle.properties</code>.</p>
@@ -677,7 +677,7 @@ For instance, you could update <code
class="highlighter-rouge">$HOME/.gradle/gra
<p>Note: if you want to uses <code class="highlighter-rouge">gpg-agent</code>,
you need to pass <code class="highlighter-rouge">useGpgCmd</code> property, and
specify the key id
via <code class="highlighter-rouge">signing.gnupg.keyName</code>.</p>
-<h2 id="making-a-snapshot-for-calcite-committers">Making a snapshot (for
Calcite committers)</h2>
+<h2 id="making-a-snapshot">Making a snapshot</h2>
<p>Before you start:</p>
@@ -691,7 +691,7 @@ git clean <span class="nt">-xn</span>
<span class="c"># Publish snapshot artifacts</span>
./gradlew clean publish <span class="nt">-Pasf</span></code></pre></figure>
-<h2 id="making-a-release-candidate-for-calcite-committers">Making a release
candidate (for Calcite committers)</h2>
+<h2 id="making-a-release-candidate">Making a release candidate</h2>
<p>Note: release artifacts (dist.apache.org and repository.apache.org) are
managed with
<a
href="https://github.com/vlsi/vlsi-release-plugins/tree/master/plugins/stage-vote-release-plugin";>stage-vote-release-plugin</a></p>
@@ -824,7 +824,7 @@
https://repository.apache.org/content/repositories/orgapachecalcite-1000
(or a similar URL)</li>
</ul>
-<h2
id="cleaning-up-after-a-failed-release-attempt-for-calcite-committers">Cleaning
up after a failed release attempt (for Calcite committers)</h2>
+<h2 id="cleaning-up-after-a-failed-release-attempt">Cleaning up after a failed
release attempt</h2>
<p>If something is not correct, you can fix it, commit it, and prepare the
next candidate.
The release candidate tags might be kept for a while.</p>
@@ -859,7 +859,7 @@ curl <span class="nt">-O</span>
https://dist.apache.org/repos/dist/release/calci
<span class="o">}</span>
checkHash apache-calcite-X.Y.Z-rcN</code></pre></figure>
-<h2
id="get-approval-for-a-release-via-apache-voting-process-for-calcite-committers">Get
approval for a release via Apache voting process (for Calcite committers)</h2>
+<h2 id="get-approval-for-a-release-via-apache-voting-process">Get approval for
a release via Apache voting process</h2>
<p>Release vote on dev list
Note: the draft mail is printed as the final step of <code
class="highlighter-rouge">prepareVote</code> task,
@@ -943,7 +943,7 @@ shortened URLs for the vote proposal and result emails.
Examples:
<a
href="https://s.apache.org/calcite-1.2-vote";>s.apache.org/calcite-1.2-vote</a>
and
<a
href="https://s.apache.org/calcite-1.2-result";>s.apache.org/calcite-1.2-result</a>.</p>
-<h2 id="publishing-a-release-for-calcite-committers">Publishing a release (for
Calcite committers)</h2>
+<h2 id="publishing-a-release">Publishing a release</h2>
<p>After a successful release vote, we need to push the release
out to mirrors, and other tasks.</p>
@@ -1006,7 +1006,7 @@ You can use
<a
href="https://mail-archives.apache.org/mod_mbox/www-announce/201906.mbox/%3CCA%2BEpF8tcJcZ41rVuwJODJmyRy-qAxZUQm9OxKsoDi07c2SKs_A%40mail.gmail.com%3E";>the
1.20.0 announcement</a>
as a template. Be sure to include a brief description of the project.</p>
-<h2 id="publish-the-web-site">Publishing the web site (for Calcite
committers)</h2>
+<h2 id="publish-the-web-site">Publishing the web site</h2>
<p>See instructions in
<a
href="https://github.com/apache/calcite/blob/master/site/README.md";>site/README.md</a>.</p>
