From commits-return-1692-archive-asf-public=cust-asf.ponee.io@parquet.apache.org Tue Oct 29 16:25:25 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id D8E8F180677 for ; Tue, 29 Oct 2019 17:25:24 +0100 (CET) Received: (qmail 40831 invoked by uid 500); 29 Oct 2019 16:25:24 -0000 Mailing-List: contact commits-help@parquet.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@parquet.apache.org Delivered-To: mailing list commits@parquet.apache.org Received: (qmail 40661 invoked by uid 99); 29 Oct 2019 16:25:23 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2019 16:25:23 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id A7EEC805E6; Tue, 29 Oct 2019 16:25:23 +0000 (UTC) Date: Tue, 29 Oct 2019 16:25:29 +0000 To: "commits@parquet.apache.org" Subject: [parquet-site] 06/12: Update Apache Parquet site for 1.9.0 release MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit From: gabor@apache.org In-Reply-To: <157236632326.26921.2787600615922550367@gitbox.apache.org> References: <157236632326.26921.2787600615922550367@gitbox.apache.org> X-Git-Host: gitbox.apache.org X-Git-Repo: parquet-site X-Git-Refname: refs/heads/asf-site X-Git-Reftype: branch X-Git-Rev: 878975aaf7fda05f538f0f7898756387034d2de0 X-Git-NotificationType: diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated Message-Id: <20191029162523.A7EEC805E6@gitbox.apache.org> 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 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 @@

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

mvn release:perform
 
@@ -210,6 +214,56 @@ Please vote by <72 HOUR FROM NOW> [ ] -1 Do not release this because...
+

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.

+ +

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/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 @@
<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 @@
 

Older Releases

Older releases can be found on GitHub: -https://github.com/Parquet/parquet-mr/releases

+https://github.com/Parquet/parquet-mr/releases

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 +sh dev/prepare-release.sh ``` 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--rcN/ releases/apache-parquet- +``` + +Then add and commit the release artifacts: + +``` +cd releases +svn add apache-parquet- +svn ci -m "Parquet: Add release " +``` + + +#### 3. Send an ANNOUNCE e-mail to announce@apache.org and the dev list + +``` +[ANNOUNCE] Apache Parquet release +``` +``` +I'm please to announce the release of Parquet ! + +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: + +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- # delete locally +git push apache :apache-parquet- # 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: ... - com.twitter - parquet - 2.1.0 + org.apache.parquet + parquet-avro + 1.9.0 ... @@ -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)