You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@calcite.apache.org by za...@apache.org on 2021/09/24 15:30:16 UTC
[calcite-site] branch master updated (a86687c -> 0527097)
This is an automated email from the ASF dual-hosted git repository.
zabetak pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/calcite-site.git.
from a86687c Site: HTTP to HTTPS redirection is not working
new 7415fbd [CALCITE-4656] Broken CI links on develop web page
new 9dd60c5 Site: Remove contributors name from commit summary
new 34278e0 Site: Add upcoming talk about Morel and update past talks section
new 0527097 Site: Remove vote email from release instructions, and minor improvements
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
community/index.html | 11 ++++--
develop/index.html | 16 ++++-----
docs/howto.html | 100 +++++++++++----------------------------------------
3 files changed, 37 insertions(+), 90 deletions(-)
[calcite-site] 02/04: Site: Remove contributors name from commit
summary
Posted by za...@apache.org.
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
commit 9dd60c59bb8eed5b6b80e99f173046c6c8e51ff6
Author: Stamatis Zampetakis <za...@gmail.com>
AuthorDate: Fri Sep 24 16:29:04 2021 +0200
Site: Remove contributors name from commit summary
See discussion in dev@ list[1].
[1] https://lists.apache.org/thread.html/r0e198225f7912fa3d6eb910b9c271b2856cf156e87caadca5bf4cd8e%40%3Cdev.calcite.apache.org%3E
---
develop/index.html | 5 ++---
docs/howto.html | 3 ---
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/develop/index.html b/develop/index.html
index 9169e2b..506d564 100644
--- a/develop/index.html
+++ b/develop/index.html
@@ -186,7 +186,7 @@ the contributor(s) involved in the discussion should:</p>
<p>Commit your change to your branch, and use a comment that starts with
the JIRA case number, like this:</p>
-<figure class="highlight"><pre><code class="language-text" data-lang="text">[CALCITE-345] AssertionError in RexToLixTranslator comparing to date literal (FirstName LastName)</code></pre></figure>
+<figure class="highlight"><pre><code class="language-text" data-lang="text">[CALCITE-345] AssertionError in RexToLixTranslator comparing to date literal</code></pre></figure>
<p>If your change had multiple commits, use <code class="highlighter-rouge">git rebase -i master</code> to
squash them into a single commit, and to bring your code up to date
@@ -201,6 +201,7 @@ description of the change.</li>
<li>The message is often, but not always, the same as the JIRA subject.
If the JIRA subject is not clear, change it (perhaps move the original
subject to the description of the JIRA case, if it clarifies).</li>
+ <li>Leave a single space character after the JIRA id.</li>
<li>Start with a capital letter.</li>
<li>Do not finish with a period.</li>
<li>Use imperative mood (“Add a handler …”) rather than past tense
@@ -211,8 +212,6 @@ the implementation (“Add handler for FileNotFound”).</li>
<li>If you are fixing a bug, it is sufficient to describe the bug
(“NullPointerException if user is unknown”) and people will correctly
surmise that the purpose of your change is to fix the bug.</li>
- <li>If you are not a committer, add your name in parentheses at the end
- of the message.</li>
</ul>
<p>Then push your commit(s) to GitHub, and create a pull request from
diff --git a/docs/howto.html b/docs/howto.html
index 3ac5e22..b044c0a 100644
--- a/docs/howto.html
+++ b/docs/howto.html
@@ -693,9 +693,6 @@ If there are conflicts it is better to ask the contributor to take this step,
otherwise it is preferred to do this manually since it saves time and also
avoids unnecessary notification messages to many people on GitHub.</p>
-<p>If the contributor is not a committer, add their name in parentheses at the end
-of the first line of the commit message.</p>
-
<p>If the merge is performed via command line (not through the GitHub web
interface), make sure the message contains a line “Close apache/calcite#YYY”,
where YYY is the GitHub pull request identifier.</p>
[calcite-site] 04/04: Site: Remove vote email from release
instructions, and minor improvements
Posted by za...@apache.org.
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
commit 05270974c19ea79c80e6c302a1e8a4d7b7b4c5ae
Author: Stamatis Zampetakis <za...@gmail.com>
AuthorDate: Fri Sep 24 17:28:23 2021 +0200
Site: Remove vote email from release instructions, and minor improvements
A draft email with the same content is printed by Gradle `prepareVote`
task so we can remove it from the site to avoid maintaining both
versions.
---
docs/howto.html | 97 +++++++++++++--------------------------------------------
1 file changed, 21 insertions(+), 76 deletions(-)
diff --git a/docs/howto.html b/docs/howto.html
index b044c0a..c93c0b8 100644
--- a/docs/howto.html
+++ b/docs/howto.html
@@ -121,19 +121,15 @@ adapters.</p>
<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>
+ <li><a href="#starting-the-release-candidate-build" id="markdown-toc-starting-the-release-candidate-build">Starting the release candidate build</a></li>
+ <li><a href="#troubleshooting" id="markdown-toc-troubleshooting">Troubleshooting</a></li>
+ <li><a href="#checking-the-artifacts" id="markdown-toc-checking-the-artifacts">Checking the artifacts</a></li>
</ul>
</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="#validating-a-release" id="markdown-toc-validating-a-release">Validating a release</a></li>
<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="#publishing-a-release" id="markdown-toc-publishing-a-release">Publishing a release</a></li>
<li><a href="#publish-the-web-site" id="markdown-toc-publish-the-web-site">Publishing the web site</a></li>
</ul>
</li>
@@ -853,7 +849,7 @@ That would perform the same steps, however it would push changes to the mock Nex
<p>If any of the steps fail, fix the problem, and
start again from the top.</p>
-<h3 id="to-prepare-a-release-candidate-directly-in-your-environment">To prepare a release candidate directly in your environment:</h3>
+<h4 id="starting-the-release-candidate-build">Starting the release candidate build</h4>
<p>Pick a release candidate index and ensure it does not interfere with previous candidates for the version.</p>
@@ -864,12 +860,13 @@ start again from the top.</p>
git clean <span class="nt">-xn</span>
<span class="c"># Dry run the release candidate (push to asf-like-environment)</span>
-./gradlew prepareVote <span class="nt">-Prc</span><span class="o">=</span>1
+./gradlew prepareVote <span class="nt">-Prc</span><span class="o">=</span>0
<span class="c"># Push release candidate to ASF servers</span>
-./gradlew prepareVote <span class="nt">-Prc</span><span class="o">=</span>1 <span class="nt">-Pasf</span></code></pre></figure>
+./gradlew prepareVote <span class="nt">-Prc</span><span class="o">=</span>0 <span class="nt">-Pasf</span></code></pre></figure>
+
+<h4 id="troubleshooting">Troubleshooting</h4>
-<p>prepareVote troubleshooting:</p>
<ul>
<li><code class="highlighter-rouge">net.rubygrapefruit.platform.NativeException: Could not start 'svnmucc'</code>: Make sure you have <code class="highlighter-rouge">svnmucc</code> command
installed in your machine.</li>
@@ -931,7 +928,7 @@ https://repository.apache.org/content/repositories/orgapachecalcite-1000
<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>
-<h2 id="validate-a-release">Validate a release</h2>
+<h2 id="validating-a-release">Validating a release</h2>
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="c"># Check that the signing key (e.g. DDB6E9812AD3FAE3) is pushed</span>
gpg <span class="nt">--recv-keys</span> key
@@ -963,53 +960,9 @@ checkHash apache-calcite-X.Y.Z-rcN</code></pre></figure>
<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,
-and you can find the draft in <code class="highlighter-rouge">/build/prepareVote/mail.txt</code></p>
-
-<figure class="highlight"><pre><code class="language-text" data-lang="text">To: dev@calcite.apache.org
-Subject: [VOTE] Release apache-calcite-X.Y.Z (release candidate N)
-
-Hi all,
-
-I have created a build for Apache Calcite X.Y.Z, release candidate N.
-
-Thanks to everyone who has contributed to this release.
-<Further details about release.> You can read the release notes here:
-https://github.com/apache/calcite/blob/XXXX/site/_docs/history.md
-
-The commit to be voted upon:
-https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=NNNNNN
-
-Its hash is XXXX.
-
-The artifacts to be voted on are located here:
-https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-X.Y.Z-rcN/
-
-The hashes of the artifacts are as follows:
-src.tar.gz.sha512 XXXX
-
-A staged Maven repository is available for review at:
-https://repository.apache.org/content/repositories/orgapachecalcite-NNNN
-
-Release artifacts are signed with the following key:
-https://people.apache.org/keys/committer/jhyde.asc
-
-Please vote on releasing this package as Apache Calcite X.Y.Z.
-
-The vote is open for the next 72 hours and passes if a majority of
-at least three +1 PMC votes are cast.
-
-[ ] +1 Release this package as Apache Calcite X.Y.Z
-[ ] 0 I don't feel strongly about it, but I'm okay with the release
-[ ] -1 Do not release this package because...
-
-
-Here is my vote:
-
-+1 (binding)
-
-Julian</code></pre></figure>
+<p>Start a vote by sending an email to the dev list. The Gradle <code class="highlighter-rouge">prepareVote</code> task
+prints a draft mail at the end, if it completes successfully. You can find the
+draft in <code class="highlighter-rouge">/build/prepareVote/mail.txt</code>.</p>
<p>After vote finishes, send out the result:</p>
@@ -1029,7 +982,7 @@ N non-binding +1s:
No 0s or -1s.
-Therefore I am delighted to announce that the proposal to release
+Therefore, I am delighted to announce that the proposal to release
Apache Calcite X.Y.Z has passed.
Thanks everyone. We’ll now roll the release out to the mirrors.
@@ -1037,7 +990,6 @@ Thanks everyone. We’ll now roll the release out to the mirrors.
There was some feedback during voting. I shall open a separate
thread to discuss.
-
Julian</code></pre></figure>
<p>Use the <a href="https://s.apache.org">Apache URL shortener</a> to generate
@@ -1055,13 +1007,11 @@ This is based on the time when you expect to announce the release.
This is usually a day after the vote closes.
Remember that UTC date changes at 4 pm Pacific time.</p>
-<h3 id="publishing-directly-in-your-environment">Publishing directly in your environment:</h3>
-
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><span class="c"># Dry run publishing the release (push to asf-like-environment)</span>
-./gradlew publishDist <span class="nt">-Prc</span><span class="o">=</span>1
+./gradlew publishDist <span class="nt">-Prc</span><span class="o">=</span>0
<span class="c"># Publish the release to ASF servers</span>
-./gradlew publishDist <span class="nt">-Prc</span><span class="o">=</span>1 <span class="nt">-Pasf</span></code></pre></figure>
+./gradlew publishDist <span class="nt">-Prc</span><span class="o">=</span>0 <span class="nt">-Pasf</span></code></pre></figure>
<p>Svnpubsub will publish to the
<a href="https://dist.apache.org/repos/dist/release/calcite">release repo</a> and propagate to the
@@ -1080,17 +1030,12 @@ svn ci</code></pre></figure>
Make sure to add the version number and date of the latest release at the site linked to in the email.</p>
<p>Update the site with the release note, the release announcement, and the javadoc of the new version.
-The javadoc can be generated only from a final version (not a SNAPSHOT) so checkout the most recent
-tag and start working there (<code class="highlighter-rouge">git checkout calcite-X.Y.Z</code>). Add a release announcement by copying
+Add a release announcement by copying
<a href="https://github.com/apache/calcite/blob/master/site/_posts/2016-10-12-release-1.10.0.md">site/_posts/2016-10-12-release-1.10.0.md</a>.
Generate the javadoc, and <a href="http://localhost:4000/news/">preview</a> the site by following the
-instructions in <a href="https://github.com/apache/calcite/blob/master/site/README.md">site/README.md</a>. Check that the announcement,
+instructions in <a href="https://github.com/apache/calcite/blob/master/site/README.md">site/README.md</a>. Ensure the announcement,
javadoc, and release note appear correctly and then publish the site following the instructions
-in the same file. Now checkout again the release branch (<code class="highlighter-rouge">git checkout branch-X.Y</code>) and commit
-the release announcement.</p>
-
-<p>Merge the release branch back into <code class="highlighter-rouge">master</code> (e.g., <code class="highlighter-rouge">git merge --ff-only branch-X.Y</code>) and align
-the <code class="highlighter-rouge">master</code> with the <code class="highlighter-rouge">site</code> branch (e.g., <code class="highlighter-rouge">git merge --ff-only site</code>).</p>
+in the same file.</p>
<p>In JIRA, search for
<a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20and%20fixVersion%20%3D%201.5.0%20and%20status%20%3D%20Resolved%20and%20resolution%20%3D%20Fixed">all issues resolved in this release</a>,
@@ -1108,7 +1053,7 @@ address. 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>
-<p>Increase the <code class="highlighter-rouge">calcite.version</code> value in <code class="highlighter-rouge">/gradle.properties</code> and commit & push
+<p>Increase the <code class="highlighter-rouge">calcite.version</code> value in <code class="highlighter-rouge">/gradle.properties</code>, commit and push
the change with the message “Prepare for next development iteration”
(see <a href="https://github.com/apache/calcite/commit/ed1470a3ea53a78c667354a5ec066425364eca73">ed1470a</a> as a reference)</p>
[calcite-site] 01/04: [CALCITE-4656] Broken CI links on develop web
page
Posted by za...@apache.org.
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
commit 7415fbd5de04e1012dec068b3b9daff487f8c1cb
Author: Stamatis Zampetakis <za...@gmail.com>
AuthorDate: Fri Sep 24 16:23:52 2021 +0200
[CALCITE-4656] Broken CI links on develop web page
---
develop/index.html | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/develop/index.html b/develop/index.html
index 2e05f59..9169e2b 100644
--- a/develop/index.html
+++ b/develop/index.html
@@ -225,7 +225,7 @@ reasons:</p>
<ol>
<li>you identified a problem after the submission of the pull request;</li>
<li>the reviewer requested further changes;</li>
- <li>the Travis CI build failed and the failure is not caused by your changes.</li>
+ <li>the CI build failed, and the failure is not caused by your changes.</li>
</ol>
<p>In order to update the pull request, you need to commit the changes in your
@@ -242,7 +242,7 @@ parameter and its alternatives. You may choose to force push your changes under
require the use of the <code class="highlighter-rouge">--force</code> option.</li>
</ul>
-<p>In the special case, that the Travis CI build failed and the failure is not
+<p>In the special case, that the CI build failed, and the failure is not
caused by your changes create an empty commit (<code class="highlighter-rouge">git commit --allow-empty</code>) and
push it.</p>
@@ -376,9 +376,10 @@ then it is the same as <code class="highlighter-rouge"><T extends @NonNull Nu
<h2 id="continuous-integration-testing">Continuous Integration Testing</h2>
-<p>Calcite has a collection of Jenkins jobs on ASF-hosted infrastructure.
-They are all organized in a single view and available at
-<a href="https://builds.apache.org/view/A-D/view/Calcite/">https://builds.apache.org/view/A-D/view/Calcite/</a>.</p>
+<p>Calcite exploits <a href="https://github.com/apache/calcite/actions?query=branch%3Amaster">GitHub actions</a>
+and <a href="https://app.travis-ci.com/github/apache/calcite">Travis</a> for continuous integration testing.
+In the past, there were also Jenkins jobs on the <a href="https://builds.apache.org/">ASF-hosted</a>
+infrastructure, but they are not maintained anymore.</p>
<h2 id="getting-started">Getting started</h2>
[calcite-site] 03/04: Site: Add upcoming talk about Morel and
update past talks section
Posted by za...@apache.org.
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
commit 34278e0ac2cc3c1ca5bb41189c845f51567ee244
Author: Stamatis Zampetakis <za...@gmail.com>
AuthorDate: Fri Sep 24 16:41:01 2021 +0200
Site: Add upcoming talk about Morel and update past talks section
---
community/index.html | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/community/index.html b/community/index.html
index 36d71fd..9a0cd94 100644
--- a/community/index.html
+++ b/community/index.html
@@ -61,13 +61,14 @@
<ul id="markdown-toc">
<li><a href="#upcoming-talks" id="markdown-toc-upcoming-talks">Upcoming talks</a> <ul>
- <li><a href="#building-modern-sql-query-optimizers-with-apache-calcite-vladimir-ozerov" id="markdown-toc-building-modern-sql-query-optimizers-with-apache-calcite-vladimir-ozerov">Building modern SQL query optimizers with Apache Calcite (Vladimir Ozerov)</a></li>
+ <li><a href="#morel-a-functional-query-language-julian-hyde" id="markdown-toc-morel-a-functional-query-language-julian-hyde">Morel, a functional query language (Julian Hyde)</a></li>
</ul>
</li>
<li><a href="#project-members" id="markdown-toc-project-members">Project Members</a></li>
<li><a href="#mailing-lists" id="markdown-toc-mailing-lists">Mailing Lists</a></li>
<li><a href="#help" id="markdown-toc-help">Help</a></li>
<li><a href="#talks" id="markdown-toc-talks">Talks</a> <ul>
+ <li><a href="#building-modern-sql-query-optimizers-with-apache-calcite" id="markdown-toc-building-modern-sql-query-optimizers-with-apache-calcite">Building modern SQL query optimizers with Apache Calcite</a></li>
<li><a href="#apache-calcite-tutorial" id="markdown-toc-apache-calcite-tutorial">Apache Calcite Tutorial</a></li>
<li><a href="#an-introduction-to-query-processing--apache-calcite" id="markdown-toc-an-introduction-to-query-processing--apache-calcite">An introduction to query processing & Apache Calcite</a></li>
<li><a href="#calcite-streaming-for-event-time-semantics" id="markdown-toc-calcite-streaming-for-event-time-semantics">Calcite streaming for event-time semantics</a></li>
@@ -88,9 +89,9 @@
<h1 id="upcoming-talks">Upcoming talks</h1>
-<h2 id="building-modern-sql-query-optimizers-with-apache-calcite-vladimir-ozerov">Building modern SQL query optimizers with Apache Calcite (Vladimir Ozerov)</h2>
+<h2 id="morel-a-functional-query-language-julian-hyde">Morel, a functional query language (Julian Hyde)</h2>
-<p>At <a href="https://www.apachecon.com/acah2021/tracks/bigdatasql.html">ApacheCon 2021</a>, September 22, 2021.</p>
+<p>At <a href="https://thestrangeloop.com/2021/morel-a-functional-query-language.html">Strange Loop 2021</a>, St. Louis, Missouri, September 30, 2021.</p>
<h1 id="project-members">Project Members</h1>
@@ -489,6 +490,10 @@ The code is available on <a href="https://github.com/apache/calcite/tree/master"
<p>Watch some presentations and read through some slide decks about
Calcite, or attend one of the <a href="#upcoming-talks">upcoming talks</a>.</p>
+<h2 id="building-modern-sql-query-optimizers-with-apache-calcite">Building modern SQL query optimizers with Apache Calcite</h2>
+
+<p>At <a href="https://www.apachecon.com/acah2021/tracks/bigdatasql.html">ApacheCon 2021</a>, September 22, 2021.</p>
+
<h2 id="apache-calcite-tutorial">Apache Calcite Tutorial</h2>
<p>At <a href="https://boss-workshop.github.io/boss-2021/">BOSS 2021</a>, Copenhagen, Denmark, August 16, 2021;