This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/production by this push:
     new 9e5403c  add release post for 1.17.1 (#177)
9e5403c is described below

commit 9e5403c921f41a2a1713da0a6acf378d9dd118c5
Author: Gang Wu <[email protected]>
AuthorDate: Mon May 18 15:46:45 2026 +0800

    add release post for 1.17.1 (#177)
---
 content/en/blog/parquet-java/1.17.1.md             | 44 ++++++++++++++++++++++
 .../en/docs/Contribution Guidelines/releasing.md   |  2 +-
 2 files changed, 45 insertions(+), 1 deletion(-)

diff --git a/content/en/blog/parquet-java/1.17.1.md 
b/content/en/blog/parquet-java/1.17.1.md
new file mode 100644
index 0000000..995dfa0
--- /dev/null
+++ b/content/en/blog/parquet-java/1.17.1.md
@@ -0,0 +1,44 @@
+---
+title: "1.17.1"
+date: 2026-05-12
+description: >
+---
+
+The [latest version of parquet-java is 
1.17.1](https://dist.apache.org/repos/dist/release/parquet/apache-parquet-1.17.1/apache-parquet-1.17.1.tar.gz).
+
+For the changes, please check out the [Release on 
Github](https://github.com/apache/parquet-java/releases/tag/apache-parquet-1.17.1).
+
+To [check the validity](https://www.apache.org/info/verification.html) of this 
release, use its:
+
+*   [Release manager OpenPGP key](https://downloads.apache.org/iceberg/KEYS)
+*   [OpenPGP 
signature](https://dist.apache.org/repos/dist/release/parquet/apache-parquet-1.17.1/apache-parquet-1.17.1.tar.gz.asc)
+*   
[SHA-512](https://dist.apache.org/repos/dist/release/parquet/apache-parquet-1.17.1/apache-parquet-1.17.1.tar.gz.sha512)
+
+The [latest version of parquet-java on the previous minor branch is 
1.16.0](https://dist.apache.org/repos/dist/release/parquet/apache-parquet-1.16.0/apache-parquet-1.16.0.tar.gz).
+
+To [check the validity](https://www.apache.org/info/verification.html) of this 
release, use its:
+
+*   [Release manager OpenPGP key](https://downloads.apache.org/iceberg/KEYS)
+*   [OpenPGP 
signature](https://dist.apache.org/repos/dist/release/parquet/apache-parquet-1.16.0/apache-parquet-1.16.0.tar.gz.asc)
+*   
[SHA-512](https://dist.apache.org/repos/dist/release/parquet/apache-parquet-1.16.0/apache-parquet-1.16.0.tar.gz.sha512)
+
+### Downloading from the Maven central repository
+
+The Parquet team publishes its [releases to Maven 
Central](https://search.maven.org/search?q=g:org.apache.parquet).
+
+Add the following dependency section to your pom.xml:
+```
+    <dependencies>
+    ...
+       <dependency>
+          <groupId>org.apache.parquet</groupId>
+          <artifactId>parquet-avro</artifactId>
+          <version>1.17.1</version> <!-- or latest version -->
+       </dependency>
+    ...
+    </dependencies>
+```
+
+### Older Releases
+
+Older releases can be found in the Archives of the Apache Software Foundation: 
[https://archive.apache.org/dist/parquet/](https://archive.apache.org/dist/parquet/)
diff --git a/content/en/docs/Contribution Guidelines/releasing.md 
b/content/en/docs/Contribution Guidelines/releasing.md
index 5b2b36c..ea4945a 100644
--- a/content/en/docs/Contribution Guidelines/releasing.md      
+++ b/content/en/docs/Contribution Guidelines/releasing.md      
@@ -81,7 +81,7 @@ The last message from the script is the release commit’s SHA1 
hash and URL for
 
 Creating the 
[pre-release](https://github.com/apache/parquet-java/releases/new) will give 
the users the changelog to see if they need to validate certain functionality. 
First select the newly created `rc` (ex: `apache-parquet-1.15.0-rc0`) tag, and 
then the previous release (ex. `apache-parquet-1.14.1`). Hit the `Generate 
release notes` button to auto generate the notes. You can curate the notes a 
bit by removing unrelated changes (whitespace, test-only changes) and sorting 
them to make t [...]
 
-#### 5\. Send a VOTE e-mail to 
[[email protected]](mailto:[email protected])
+#### 6\. Send a VOTE e-mail to 
[[email protected]](mailto:[email protected])
 
 Here is a template you can use. Make sure everything applies to your release.
 

Reply via email to