You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@parquet.apache.org by ga...@apache.org on 2019/10/29 16:25:29 UTC
[parquet-site] 06/12: Update Apache Parquet site for 1.9.0 release
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
commit 878975aaf7fda05f538f0f7898756387034d2de0
Author: Ryan Blue <bl...@apache.org>
AuthorDate: Mon Oct 24 20:27:34 2016 +0000
Update Apache Parquet site for 1.9.0 release
git-svn-id: https://svn.apache.org/repos/asf/parquet/site@1766441 13f79535-47bb-0310-9956-ffa450edef68
---
Gemfile.lock | 5 +-
publish/documentation/how-to-release/index.html | 56 ++++++++++++++++-
publish/downloads/index.html | 8 +--
source/documentation/how-to-release.html.md | 82 ++++++++++++++++++++++++-
source/downloads.html.md | 8 +--
5 files changed, 148 insertions(+), 11 deletions(-)
diff --git a/Gemfile.lock b/Gemfile.lock
index 741838b..599b793 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -22,7 +22,7 @@ GEM
em-websocket (0.5.0)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.5.3)
- eventmachine (1.0.3)
+ eventmachine (1.2.0.1)
execjs (1.4.0)
multi_json (~> 1.0)
ffi (1.9.3)
@@ -109,3 +109,6 @@ DEPENDENCIES
middleman-syntax (= 1.2.1)
rake (= 10.3.1)
redcarpet!
+
+BUNDLED WITH
+ 1.13.6
diff --git a/publish/documentation/how-to-release/index.html b/publish/documentation/how-to-release/index.html
index 394e3d0..62efa0b 100644
--- a/publish/documentation/how-to-release/index.html
+++ b/publish/documentation/how-to-release/index.html
@@ -148,10 +148,14 @@
</ol>
<h4 id="1.-run-the-prepare-script">1. Run the prepare script</h4>
-<pre class="highlight text">sh dev/release-prepare.sh <version>
+<pre class="highlight text">sh dev/prepare-release.sh <version>
</pre>
<p>This runs maven’s release prepare with a consistent tag name. After this step, the release tag will exist in the git repository.</p>
+<p>If this step fails, you can roll back the changes by running these commands.</p>
+<pre class="highlight text">find ./ -type f -name '*.releaseBackup' -exec rm {} \;
+find ./ -type f -name 'pom.xml' -exec git checkout {} \;
+</pre>
<h4 id="2.-run-release:perform-to-stage-binaries">2. Run release:perform to stage binaries</h4>
<pre class="highlight text">mvn release:perform
</pre>
@@ -210,6 +214,56 @@ Please vote by <72 HOUR FROM NOW>
[ ] -1 Do not release this because...
</pre>
+<h3 id="publishing-after-the-vote-passes">Publishing after the vote passes</h3>
+
+<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="2.-copy-the-release-artifacts-in-svn-into-releases">2. Copy the release artifacts in SVN into releases</h4>
+
+<p>First, check out the candidates and releases locations in SVN:</p>
+<pre class="highlight text">mkdir parquet
+cd parquet
+svn co https://dist.apache.org/repos/dist/dev/parquet candidates
+svn co https://dist.apache.org/repos/dist/release/parquet releases
+</pre>
+<p>Next, copy the directory for the release candidate the passed from candidates to releases and rename it; remove the “-rcN” part of the directory name.</p>
+<pre class="highlight text">cp -r candidates/apache-parquet-<VERSION>-rcN/ releases/apache-parquet-<VERSION>
+</pre>
+<p>Then add and commit the release artifacts:</p>
+<pre class="highlight text">cd releases
+svn add apache-parquet-<version>
+svn ci -m "Parquet: Add release <VERSION>"
+</pre>
+<h4 id="3.-send-an-announce-e-mail-to-announce@apache.org-and-the-dev-list">3. Send an ANNOUNCE e-mail to <a href="mailto:announce@apache.org">announce@apache.org</a> and the dev list</h4>
+<pre class="highlight text">[ANNOUNCE] Apache Parquet release <VERSION>
+</pre><pre class="highlight text">I'm please to announce the release of Parquet <VERSION>!
+
+Parquet is a general-purpose columnar file format for nested data. It uses
+space-efficient encodings and a compressed and splittable structure for
+processing frameworks like Hadoop.
+
+Changes are listed at: <CHANGES-URL>
+
+This release can be downloaded from: https://www.apache.org/dyn/closer.cgi/parquet/
+
+Java artifacts are available from Maven Central.
+
+Thanks to everyone for contributing!
+</pre>
+<h4 id="4.-update-parquet.apache.org">4. Update parquet.apache.org</h4>
+
+<p>Instructions for updating the site are on the <a href="http://parquet.apache.org/contribute/">contribution page</a>.</p>
+
+<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>
+<pre class="highlight text">git tag -d apache-parquet-<VERSION> # delete locally
+git push apache :apache-parquet-<VERSION> # delete in the Apache repo
+</pre>
+<p>Then, use the release process above to build another RC for the release version.</p>
+
</div>
<div class="container">
<hr>
diff --git a/publish/downloads/index.html b/publish/downloads/index.html
index 3acf0ce..48a076a 100644
--- a/publish/downloads/index.html
+++ b/publish/downloads/index.html
@@ -127,9 +127,9 @@
<pre class="highlight text"><dependencies>
...
<dependency>
- <groupId>com.twitter</groupId>
- <artifactId>parquet</artifactId>
- <version>2.1.0</version> <!-- or latest version -->
+ <groupId>org.apache.parquet</groupId>
+ <artifactId>parquet-avro</artifactId>
+ <version>1.9.0</version> <!-- or latest version -->
</dependency>
...
</dependencies>
@@ -137,7 +137,7 @@
<h3 id="older-releases">Older Releases</h3>
<p>Older releases can be found on GitHub:
-<a href="https://github.com/Parquet/parquet-mr/releases">https://github.com/Parquet/parquet-mr/releases</a></p>
+<a href="https://github.com/apache/parquet-mr/releases">https://github.com/Parquet/parquet-mr/releases</a></p>
</div>
<div class="container">
diff --git a/source/documentation/how-to-release.html.md b/source/documentation/how-to-release.html.md
index 144d7ca..142173e 100644
--- a/source/documentation/how-to-release.html.md
+++ b/source/documentation/how-to-release.html.md
@@ -36,11 +36,18 @@ Before you start the release process:
#### 1. Run the prepare script
```
-sh dev/release-prepare.sh <version>
+sh dev/prepare-release.sh <version>
```
This runs maven's release prepare with a consistent tag name. After this step, the release tag will exist in the git repository.
+If this step fails, you can roll back the changes by running these commands.
+
+```
+find ./ -type f -name '*.releaseBackup' -exec rm {} \;
+find ./ -type f -name 'pom.xml' -exec git checkout {} \;
+```
+
#### 2. Run release:perform to stage binaries
```
@@ -111,3 +118,76 @@ Please vote by <72 HOUR FROM NOW>
[nexus]: https://repository.apache.org/
[staging]: https://repository.apache.org/content/groups/staging/org/apache/parquet/
+
+### Publishing after the vote passes
+
+After a release candidate passes a vote, the candidate needs to be published as the final release.
+
+#### 1. Release the binary repository in Nexus
+
+
+#### 2. Copy the release artifacts in SVN into releases
+
+First, check out the candidates and releases locations in SVN:
+
+```
+mkdir parquet
+cd parquet
+svn co https://dist.apache.org/repos/dist/dev/parquet candidates
+svn co https://dist.apache.org/repos/dist/release/parquet releases
+```
+
+Next, copy the directory for the release candidate the passed from candidates to releases and rename it; remove the "-rcN" part of the directory name.
+
+```
+cp -r candidates/apache-parquet-<VERSION>-rcN/ releases/apache-parquet-<VERSION>
+```
+
+Then add and commit the release artifacts:
+
+```
+cd releases
+svn add apache-parquet-<version>
+svn ci -m "Parquet: Add release <VERSION>"
+```
+
+
+#### 3. Send an ANNOUNCE e-mail to announce@apache.org and the dev list
+
+```
+[ANNOUNCE] Apache Parquet release <VERSION>
+```
+```
+I'm please to announce the release of Parquet <VERSION>!
+
+Parquet is a general-purpose columnar file format for nested data. It uses
+space-efficient encodings and a compressed and splittable structure for
+processing frameworks like Hadoop.
+
+Changes are listed at: <CHANGES-URL>
+
+This release can be downloaded from: https://www.apache.org/dyn/closer.cgi/parquet/
+
+Java artifacts are available from Maven Central.
+
+Thanks to everyone for contributing!
+```
+
+#### 4. Update parquet.apache.org
+
+Instructions for updating the site are on the [contribution page][parquet-site-docs].
+
+[parquet-site-docs]: http://parquet.apache.org/contribute/
+
+
+### What to do if a vote fails
+
+If a vote fails, you need to remove the release tag that was created by the `dev/prepare-release.sh` script:
+
+```
+git tag -d apache-parquet-<VERSION> # delete locally
+git push apache :apache-parquet-<VERSION> # delete in the Apache repo
+```
+
+Then, use the release process above to build another RC for the release version.
+
diff --git a/source/downloads.html.md b/source/downloads.html.md
index d06a05b..e758293 100644
--- a/source/downloads.html.md
+++ b/source/downloads.html.md
@@ -10,9 +10,9 @@ Add the following dependency section to your pom.xml:
<dependencies>
...
<dependency>
- <groupId>com.twitter</groupId>
- <artifactId>parquet</artifactId>
- <version>2.1.0</version> <!-- or latest version -->
+ <groupId>org.apache.parquet</groupId>
+ <artifactId>parquet-avro</artifactId>
+ <version>1.9.0</version> <!-- or latest version -->
</dependency>
...
</dependencies>
@@ -20,4 +20,4 @@ Add the following dependency section to your pom.xml:
### Older Releases
Older releases can be found on GitHub:
-[https://github.com/Parquet/parquet-mr/releases](https://github.com/Parquet/parquet-mr/releases)
+[https://github.com/Parquet/parquet-mr/releases](https://github.com/apache/parquet-mr/releases)