Skip to content
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.

Commit

Permalink
SUBMARINE-689. Refine the how-to-release doc on fast checking out KEY…
Browse files Browse the repository at this point in the history
…S file

### What is this PR for?
Refine the how-to-release doc on fast checking out KEYS file

### What type of PR is it?
Documentation

### What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-689

### How should this be tested?
N/A

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: Zhankun Tang <ztang@apache.org>

Closes #467 from tangzhankun/SUBMARINE-689 and squashes the following commits:

b60ba96 [Zhankun Tang] SUBMARINE-689. Refine the how-to-release doc on fast checking out KEYS file.
  • Loading branch information
tangzhankun authored and jiwq committed Dec 1, 2020
1 parent 9b669b8 commit 78fe362
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions dev-support/cicd/HowToRelease.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ gpg --keyserver pgp.mit.edu --recv-key <the release manager's public key id like
gpg --sign-key <the release manager's public key id>
svn co --depth immediates https://dist.apache.org/repos/dist apache-dist
cd apache-dist
svn update --set-depth infinity release/submarine
svn update --set-depth immediates release/submarine
cd release/submarine
gpg --list-sigs <your name> >> KEYS
gpg --armor --export <your name> >> KEYS
Expand All @@ -35,7 +35,7 @@ Assuming we're releasing version X, use below advanced filter in [submarine issu
project in ("Apache Submarine") AND "Target Version" = 0.3.0 AND statusCategory != Done
```
Click "tools"-> "bulk update" to edit all issues:
1. Change the target version to X+1. Here it is `0.4.0`.
1. Change the target version to X+1. Here it is `0.4.0` (If it doesn't exist, ask for the PMC's help to access [administer-versions](https://issues.apache.org/jira/plugins/servlet/project-config/SUBMARINE/administer-versions?status=no-filter) to add the new version).
2. Add a comment to inform contributors. Like this. `Bulk update due to releasing 0.3.0. Please change it back if you think this is a blocker.`

Do a double-check to confirm that there are no issues found with the above filter. And send mail to the developer list informing that we should mark "Target version" to `0.4.0` when creating new JIRAs.
Expand Down

0 comments on commit 78fe362

Please sign in to comment.