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

fokko 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 af2630c  MINOR: Change link to `parquet-java` (#89)
af2630c is described below

commit af2630c9ff076ffc47d70876beb3acd205debb7c
Author: Fokko Driesprong <[email protected]>
AuthorDate: Tue Nov 26 16:35:34 2024 +0100

    MINOR: Change link to `parquet-java` (#89)
    
    * MINOR: Change link to `parquet-java`
    
    * Improve steps
---
 content/en/docs/Contribution Guidelines/releasing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/Contribution Guidelines/releasing.md 
b/content/en/docs/Contribution Guidelines/releasing.md
index c4a72f2..eb5e3ff 100644
--- a/content/en/docs/Contribution Guidelines/releasing.md      
+++ b/content/en/docs/Contribution Guidelines/releasing.md      
@@ -27,7 +27,7 @@ If you have problems, read the [publishing Maven artifacts 
documentation](https:
 
 Parquet uses the maven-release-plugin to tag a release and push binary 
artifacts to staging in Nexus. Once maven completes the release, the official 
source tarball is built from the tag.
 
-Before you start the release process:
+#### 0\. Before you start the release process
 
 1. Verify that the release is finished (no planned Issues/PRs are pending [on 
the milestone](https://github.com/apache/parquet-java/milestones)) 
 1. Build and test the project 
@@ -94,7 +94,7 @@ Here is a template you can use. Make sure everything applies 
to your release.
 
     The commit id is <SHA1>
     * This corresponds to the tag: apache-parquet-<VERSION>-rc<NUM>
-    * https://github.com/apache/parquet-mr/tree/<SHA1>
+    * https://github.com/apache/parquet-java/tree/<SHA1>
 
     The release tarball, signature, and checksums are here:
     * https://dist.apache.org/repos/dist/dev/parquet/<PATH>

Reply via email to