This is an automated email from the ASF dual-hosted git repository.
yao pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c13ea2ec32 [SPARK-48963][SPARK-34553] Add instructions for
JIRA_ACCESS_TOKEN and GITHUB_OAUTH_KEY in release guide (#537)
c13ea2ec32 is described below
commit c13ea2ec324b2cb5000d2fbcb5635762c87d3ccb
Author: Kent Yao <[email protected]>
AuthorDate: Tue Jul 23 13:49:19 2024 +0800
[SPARK-48963][SPARK-34553] Add instructions for JIRA_ACCESS_TOKEN and
GITHUB_OAUTH_KEY in release guide (#537)
* [SPARK-48963] Add JIRA_ACCESS_TOKEN instructions in release guide
* Update release-process.md
Co-authored-by: Liang-Chi Hsieh <[email protected]>
* Update release-process.md
Co-authored-by: Liang-Chi Hsieh <[email protected]>
* Update site/release-process.html
* Update site/release-process.html
---------
Co-authored-by: Liang-Chi Hsieh <[email protected]>
---
release-process.md | 8 +++++---
site/release-process.html | 8 +++++---
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/release-process.md b/release-process.md
index 81f7042d3d..46724c2ae5 100644
--- a/release-process.md
+++ b/release-process.md
@@ -401,16 +401,18 @@ $ export RELEASE_TAG=v1.1.1
$ export PREVIOUS_RELEASE_TAG=v1.1.0
# Generate initial contributors list, likely with warnings
$ ./generate-contributors.py
-# set JIRA_USERNAME, JIRA_PASSWORD, and GITHUB_API_TOKEN
+# Set GITHUB_OAUTH_KEY.
+$ export GITHUB_OAUTH_KEY=blabla
+# Set either JIRA_ACCESS_TOKEN (for 4.0.0 and later) or JIRA_USERNAME /
JIRA_PASSWORD.
+$ export JIRA_ACCESS_TOKEN=blabla
$ export JIRA_USERNAME=blabla
$ export JIRA_PASSWORD=blabla
-$ export GITHUB_API_TOKEN=blabla
# Translate names generated in the previous step, reading from
known_translations if necessary
$ ./translate-contributors.py
```
Additionally, if you wish to give more specific credit for developers of
larger patches, you may
-use the the following commands to identify large patches. Extra care must be
taken to make sure
+use the following commands to identify large patches. Extra care must be taken
to make sure
commits from previous releases are not counted since git cannot easily
associate commits that
were back ported into different branches.
diff --git a/site/release-process.html b/site/release-process.html
index 40acc2410f..bb1b02c741 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -541,16 +541,18 @@ $ export RELEASE_TAG=v1.1.1
$ export PREVIOUS_RELEASE_TAG=v1.1.0
# Generate initial contributors list, likely with warnings
$ ./generate-contributors.py
-# set JIRA_USERNAME, JIRA_PASSWORD, and GITHUB_API_TOKEN
+# Set GITHUB_OAUTH_KEY.
+$ export GITHUB_OAUTH_KEY=blabla
+# Set either JIRA_ACCESS_TOKEN (for 4.0.0 and later) or JIRA_USERNAME /
JIRA_PASSWORD.
+$ export JIRA_ACCESS_TOKEN=blabla
$ export JIRA_USERNAME=blabla
$ export JIRA_PASSWORD=blabla
-$ export GITHUB_API_TOKEN=blabla
# Translate names generated in the previous step, reading from
known_translations if necessary
$ ./translate-contributors.py
</code></pre></div></div>
<p>Additionally, if you wish to give more specific credit for developers of
larger patches, you may
-use the the following commands to identify large patches. Extra care must be
taken to make sure
+use the following commands to identify large patches. Extra care must be taken
to make sure
commits from previous releases are not counted since git cannot easily
associate commits that
were back ported into different branches.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
