parquet-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ga...@apache.org
Subject [parquet-site] branch asf-site updated: PARQUET-1687: Fix missing re-generate
Date Tue, 12 Nov 2019 16:27:44 GMT
This is an automated email from the ASF dual-hosted git repository.

gabor pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/parquet-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new ccb5731  PARQUET-1687: Fix missing re-generate
ccb5731 is described below

commit ccb5731e02f50637bc61e1d7d2ed5fdb28a51732
Author: Gabor Szadovszky <gabor.szadovszky@cloudera.com>
AuthorDate: Tue Nov 12 17:24:01 2019 +0100

    PARQUET-1687: Fix missing re-generate
    
    In the previous commit the static files were not re-generated so the
    site did not updated properly.
---
 output/config                                  | 18 +++++++++++
 output/documentation/how-to-release/index.html | 44 +++++++++++++-------------
 2 files changed, 40 insertions(+), 22 deletions(-)

diff --git a/output/config b/output/config
new file mode 100644
index 0000000..ab9e09f
--- /dev/null
+++ b/output/config
@@ -0,0 +1,18 @@
+/* Generated by Opal 0.10.6 */
+(function(Opal) {
+  var $a, $b, TMP_1, self = Opal.top, $scope = Opal, nil = Opal.nil, $breaker = Opal.breaker,
$slice = Opal.slice, $hash2 = Opal.hash2;
+
+  Opal.add_stubs(['$set', '$configure', '$activate']);
+  self.$set("markdown_engine", "redcarpet");
+  self.$set("markdown", $hash2(["layout_engine", "tables", "autolink", "smartypants", "fenced_code_blocks",
"with_toc_data"], {"layout_engine": "erb", "tables": true, "autolink": true, "smartypants":
true, "fenced_code_blocks": true, "with_toc_data": true}));
+  self.$set("build_dir", "output");
+  self.$set("css_dir", "assets/css");
+  self.$set("js_dir", "assets/js");
+  self.$set("images_dir", "assets/img");
+  ($a = ($b = self).$configure, $a.$$p = (TMP_1 = function(){var self = TMP_1.$$s || this;
+
+  return self.$activate("relative_assets")}, TMP_1.$$s = self, TMP_1.$$arity = 0, TMP_1),
$a).call($b, "build");
+  self.$activate("directory_indexes");
+  self.$activate("syntax");
+  return self.$activate("livereload");
+})(Opal);
diff --git a/output/documentation/how-to-release/index.html b/output/documentation/how-to-release/index.html
index 23953b2..12f503d 100644
--- a/output/documentation/how-to-release/index.html
+++ b/output/documentation/how-to-release/index.html
@@ -133,7 +133,7 @@
 <h3 id="setup">Setup</h3>
 
 <p>You will need:
-* PGP code signing keys, published in KEYS
+* PGP code signing keys, published in <a href="https://www.apache.org/dist/parquet/KEYS">KEYS</a>
 * Permission to stage artifacts in Nexus</p>
 
 <p>Make sure you have permission to deploy Parquet artifacts to Nexus by pushing a
snapshot:</p>
@@ -154,14 +154,14 @@
 
 <ul>
 <li>Go to the release notes for the release in JIRA</li>
-<li>Copy the HTML and convert it to markdown with an <a href="https://domchristie.github.io/to-markdown/">online
converter</a></li>
+<li>Copy the HTML and convert it to markdown with an <a href="https://domchristie.github.io/turndown/">online
converter</a></li>
 <li>Add the content to CHANGES.md and update formatting</li>
 <li>Commit the update to CHANGES.md</li>
 </ul></li>
 </ol>
 
 <h4 id="1-run-the-prepare-script">1. Run the prepare script</h4>
-<div class="highlight"><pre class="highlight plaintext"><code>sh dev/prepare-release.sh
&lt;version&gt;
+<div class="highlight"><pre class="highlight plaintext"><code>dev/prepare-release.sh
&lt;version&gt; &lt;rc-number&gt;
 </code></pre></div>
 <p>This runs maven&rsquo;s release prepare with a consistent tag name. After this
step, the release tag will exist in the git repository.</p>
 
@@ -186,7 +186,7 @@ find ./ -type f -name 'pom.xml' -exec git checkout {} \;
 </ol>
 
 <h4 id="4-run-the-source-tarball-script">4. Run the source tarball script</h4>
-<div class="highlight"><pre class="highlight plaintext"><code>sh dev/source-release.sh
&lt;version&gt; &lt;rc-number&gt;
+<div class="highlight"><pre class="highlight plaintext"><code>dev/source-release.sh
&lt;version&gt; &lt;rc-number&gt;
 </code></pre></div>
 <p>This script builds the source tarball from the release tag&rsquo;s SHA1, signs
it, and uploads the necessary files with SVN.</p>
 
@@ -203,24 +203,23 @@ find ./ -type f -name 'pom.xml' -exec git checkout {} \;
 I propose the following RC to be released as official Apache Parquet &lt;VERSION&gt;
release.
 
 The commit id is &lt;SHA1&gt;
-* This corresponds to the tag: apache-parquet-&lt;VERSION&gt;
-* https://github.com/apache/parquet-format/tree/&lt;SHA1&gt;
-* https://git-wip-us.apache.org/repos/asf/projects/repo?p=parquet-mr.git&amp;a=commit&amp;h=&lt;SHA1&gt;
+* This corresponds to the tag: apache-parquet-&lt;VERSION&gt;-rc&lt;NUM&gt;
+* https://github.com/apache/parquet-mr/tree/&lt;SHA1&gt;
 
 The release tarball, signature, and checksums are here:
 * https://dist.apache.org/repos/dist/dev/parquet/&lt;PATH&gt;
 
 You can find the KEYS file here:
-* https://dist.apache.org/repos/dist/dev/parquet/KEYS
+* https://apache.org/dist/parquet/KEYS
 
 Binary artifacts are staged in Nexus here:
-* https://repository.apache.org/content/groups/staging/org/apache/parquet/parquet/
+* https://repository.apache.org/content/groups/staging/org/apache/parquet/
 
 This release includes important changes that I should have summarized here, but I'm lazy.
 
 Please download, verify, and test.
 
-Please vote by &lt;72 HOUR FROM NOW&gt;
+Please vote in the next 72 hours.
 
 [ ] +1 Release this as Apache Parquet &lt;VERSION&gt;
 [ ] +0
@@ -231,9 +230,18 @@ Please vote by &lt;72 HOUR FROM NOW&gt;
 
 <p>After a release candidate passes a vote, the candidate needs to be published as
the final release.</p>
 
-<h4 id="1-release-the-binary-repository-in-nexus">1. Release the binary repository
in Nexus</h4>
+<h4 id="1-tag-final-release-and-set-development-version">1. Tag final release and set
development version</h4>
+<div class="highlight"><pre class="highlight plaintext"><code>dev/finalize-release
&lt;release-version&gt; &lt;rc-num&gt; &lt;new-development-version-without-SNAPSHOT-suffix&gt;
+</code></pre></div>
+<p>This will add the final release tag to the RC tag and sets the new development version
in the pom files.
+If everything is fine push the changes and the new tag to github:
+<code>
+git push --follow-tags
+</code></p>
+
+<h4 id="2-release-the-binary-repository-in-nexus">2. Release the binary repository
in Nexus</h4>
 
-<h4 id="2-copy-the-release-artifacts-in-svn-into-releases">2. Copy the release artifacts
in SVN into releases</h4>
+<h4 id="3-copy-the-release-artifacts-in-svn-into-releases">3. Copy the release artifacts
in SVN into releases</h4>
 
 <p>First, check out the candidates and releases locations in SVN:</p>
 <div class="highlight"><pre class="highlight plaintext"><code>mkdir parquet
@@ -249,12 +257,12 @@ svn co https://dist.apache.org/repos/dist/release/parquet releases
 svn add apache-parquet-&lt;version&gt;
 svn ci -m "Parquet: Add release &lt;VERSION&gt;"
 </code></pre></div>
-<h4 id="3-update-parquet-apache-org">3. Update parquet.apache.org</h4>
+<h4 id="4-update-parquet-apache-org">4. Update parquet.apache.org</h4>
 
 <p>Update the downloads page on parquet.apache.org.
 Instructions for updating the site are on the <a href="http://parquet.apache.org/contribute/">contribution
page</a>.</p>
 
-<h4 id="4-send-an-announce-e-mail-to-announce-apache-org-and-the-dev-list">4. Send
an ANNOUNCE e-mail to <a href="mailto:announce@apache.org">announce@apache.org</a>
and the dev list</h4>
+<h4 id="5-send-an-announce-e-mail-to-announce-apache-org-and-the-dev-list">5. Send
an ANNOUNCE e-mail to <a href="mailto:announce@apache.org">announce@apache.org</a>
and the dev list</h4>
 <div class="highlight"><pre class="highlight plaintext"><code>[ANNOUNCE]
Apache Parquet release &lt;VERSION&gt;
 </code></pre></div><div class="highlight"><pre class="highlight
plaintext"><code>I'm please to announce the release of Parquet &lt;VERSION&gt;!
 
@@ -270,14 +278,6 @@ Java artifacts are available from Maven Central.
 
 Thanks to everyone for contributing!
 </code></pre></div>
-<h3 id="what-to-do-if-a-vote-fails">What to do if a vote fails</h3>
-
-<p>If a vote fails, you need to remove the release tag that was created by the <code>dev/prepare-release.sh</code>
script:</p>
-<div class="highlight"><pre class="highlight plaintext"><code>git tag -d
apache-parquet-&lt;VERSION&gt; # delete locally
-git push apache :apache-parquet-&lt;VERSION&gt; # delete in the Apache repo
-</code></pre></div>
-<p>Then, use the release process above to build another RC for the release version.</p>
-
 	  </div>
       <div class="container">
     <hr>


Mime
View raw message