(opendal) branch manjusaka/update-release-docs created (now e0a84adeb7)

[ma...@apache.org]

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

manjusaka pushed a change to branch manjusaka/update-release-docs
in repository https://gitbox.apache.org/repos/asf/opendal.git


      at e0a84adeb7 chore(website): Add extra artifacts check process in release document

This branch includes the following new commits:

     new e0a84adeb7 chore(website): Add extra artifacts check process in release document

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(opendal) 01/01: chore(website): Add extra artifacts check process in release document

[ma...@apache.org]

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

manjusaka pushed a commit to branch manjusaka/update-release-docs
in repository https://gitbox.apache.org/repos/asf/opendal.git

commit e0a84adeb70b6b402a4cd8448e333aaae28ed88d
Author: Manjusaka <me...@manjusaka.me>
AuthorDate: Sun Jan 21 22:43:21 2024 +0800

    chore(website): Add extra artifacts check process in release document
    
    Signed-off-by: Manjusaka <me...@manjusaka.me>
---
 website/community/committers/release.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/website/community/committers/release.md b/website/community/committers/release.md
index 4dd1e9d38a..87bef230a8 100644
--- a/website/community/committers/release.md
+++ b/website/community/committers/release.md
@@ -165,6 +165,16 @@ Pushing a Git tag to GitHub repo will trigger a GitHub Actions workflow that cre
 
 :::
 
+### Check the GitHub action status
+
+After pushing the tag, we need to check the GitHub action status to make sure the release candidate is created successfully.
+
+- Python: [Bindings Python CI](https://github.com/apache/opendal/actions/workflows/bindings_python.yml)
+- Java: [Bindings Java CI](https://github.com/apache/opendal/actions/workflows/bindings_java.yml) and [Bindings Java Release](https://github.com/apache/opendal/actions/workflows/release_java.yml)
+- Node.js: [Bindings Node.js CI](https://github.com/apache/opendal/actions/workflows/bindings_nodejs.yml)
+
+In the most cases, it would be greate to rerun the failed workflow directly when you find some failures. But if a new code patch is needed to fix the failure, you should create a new release candidate tag, increase the rc number and push it to GitHub.
+
 ## ASF Side
 
 If any step in the ASF Release process fails and requires code changes,
@@ -426,6 +436,18 @@ If the vote failed, click "Drop" to drop the staging Maven artifacts.
 
 :::
 
+### Check the language binding artifacts
+
+We need to check the language binding artifacts in the language package repo to make sure they are released successfully.
+
+- Python: <https://pypi.org/project/opendal/>
+- Java: <https://repository.apache.org/#nexus-search;quick~opendal>
+- Node.js: <https://www.npmjs.com/package/opendal>
+
+For Java binding, if we can not find the latest version of artifacts in the repo, we need to check the `orgapacheopendal-${maven_artifact_number}` artifact status in staging repo. 
+
+For non-Java bindings, if we can not find the latest version of artifacts in the repo, we need to check the GitHub action status.
+
 ### Create a GitHub Release
 
 - Click [here](https://github.com/apache/opendal/releases/new) to create a new release.