Release 1.13.0

content/en/blog/parquet-mr/1.13.0.md

@@ -0,0 +1,41 @@
+---
+title: "1.13.0"
+date: 2023-04-06
+description: >
+---
+The [latest version of parquet-mr is 1.13.0](https://downloads.apache.org/parquet/apache-parquet-1.13.0/apache-parquet-1.13.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/parquet/KEYS)
+*   [OpenPGP signature](https://downloads.apache.org/parquet/apache-parquet-1.13.0/apache-parquet-1.13.0.tar.gz.asc)
+*   [SHA-512](https://downloads.apache.org/parquet/apache-parquet-1.13.0/apache-parquet-1.13.0.tar.gz.sha512)
+
+The [latest version of parquet-mr on the previous minor branch is 1.12.3](https://downloads.apache.org/parquet/apache-parquet-1.12.3/apache-parquet-1.12.3.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/parquet/KEYS)
+*   [OpenPGP signature](https://downloads.apache.org/parquet/apache-parquet-1.12.3/apache-parquet-1.12.3.tar.gz.asc)
+*   [SHA-512](https://downloads.apache.org/parquet/apache-parquet-1.12.3/apache-parquet-1.12.3.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.13.0</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/)

content/en/docs/Contribution Guidelines/releasing.md

@@ -23,13 +23,15 @@ Parquet uses the maven-release-plugin to tag a release and push binary artifacts
 
 Before you start the release process:
 
-1.  Verify that the release is finished (no planned JIRAs are pending)
-2.  Build and test the project
-3.  Update the change log
+1.  Verify that the release is finished (no planned JIRAs are pending and all patches are cherry-picked to the release branch) 
+2.  Resolve all associated JIRAs with correct target version and create the next unreleased version in the JIRA project
+3.  Build and test the project
+4.  Create a new branch for the release if this is a new minor version. For example, if the new minor version is 1.13.0, create a new branch `parquet-1.13.x`
+5.  Update the change log
     *   Go to the release notes for the release in JIRA
     *   Copy the HTML and convert it to markdown with an [online converter](https://domchristie.github.io/turndown/)
     *   Add the content to CHANGES.md and update formatting
-    *   Commit the update to CHANGES.md
+    *   Commit the update to CHANGES.md and make sure it is committed to both release and master branches
 
 #### 1\. Run the prepare script
 
@@ -120,6 +122,13 @@ This will add the final release tag to the RC tag and sets the new development v
 
 #### 2\. Release the binary repository in Nexus
 
+Releasing a binary repository publishes the binaries to [public](https://repository.apache.org/content/groups/public/org/apache/parquet/).
+
+1.  Go to [Nexus](https://repository.apache.org/).
+2.  In the menu on the left, choose “Staging Repositories”.
+3.  Select the Parquet repository.
+4.  At the top, click Release and follow the instructions. For the comment use “Apache Parquet \[Format\] ”.
+
 #### 3\. Copy the release artifacts in SVN into releases
 
 First, check out the candidates and releases locations in SVN: