This is an automated email from the ASF dual-hosted git repository.
ulyssesyou pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-kyuubi.git
The following commit(s) were added to refs/heads/master by this push:
new d8f70e9 [KYUUBI #1844] Add step for generating release notes
d8f70e9 is described below
commit d8f70e9727769376a4e0af9fa24af0249b9fc682
Author: yanghua <[email protected]>
AuthorDate: Tue Feb 8 09:22:42 2022 +0800
[KYUUBI #1844] Add step for generating release notes
<!--
Thanks for sending a pull request!
Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://kyuubi.readthedocs.io/en/latest/community/contributions.html
2. If the PR is related to an issue in
https://github.com/apache/incubator-kyuubi/issues, add '[KYUUBI #XXXX]' in your
PR title, e.g., '[KYUUBI #XXXX] Your PR title ...'.
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][KYUUBI #XXXX] Your PR title ...'.
-->
### _Why are the changes needed?_
<!--
Please clarify why the changes are needed. For instance,
1. If you add a feature, you can talk about the use case of it.
2. If you fix a bug, you can clarify why it is a bug.
-->
### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including
negative and positive cases if possible
- [ ] Add screenshots for manual tests if appropriate
- [ ] [Run
test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests)
locally before make a pull request
Closes #1864 from yanghua/KYUUBI-1844.
Closes #1844
47d09c39 [yanghua] Address review comments
b5a8bbc3 [yanghua] [KYUUBI #1844] Add step for generating release notes
Authored-by: yanghua <[email protected]>
Signed-off-by: ulysses-you <[email protected]>
---
docs/community/release.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/docs/community/release.md b/docs/community/release.md
index 06738db..e2a1ab0 100644
--- a/docs/community/release.md
+++ b/docs/community/release.md
@@ -184,6 +184,8 @@ git commit -am "[RELEASE] Bump ${RELEASE_VERSION}"
The tag pattern is `v${RELEASE_VERSION}-rc${RELEASE_RC_NO}`, e.g.
`v1.3.0-incubating-rc0`
+> NOTE: After all the voting passed, be sure to create a final tag with the
pattern: `v${RELEASE_VERSION}`
+
4. Package the release binaries & sources, and upload them to the Apache
staging SVN repo. Publish jars to the Apache
staging Maven repo.
@@ -193,6 +195,14 @@ build/release/release.sh publish
To make your release available in the staging repository, you must close the
staging repo in the [Apache
Nexus](https://repository.apache.org/#stagingRepositories). Until you close,
you can re-run deploying to staging multiple times. But once closed, it will
create a new staging repo. So ensure you close this, so that the next RC (if
need be) is on a new repo. Once everything is good, close the staging
repository on Apache Nexus.
+5. Generate a pre-release note from GitHub for the subsequent voting.
+
+Goto the [release page](https://github.com/apache/incubator-kyuubi/releases)
and click the "Draft a new release" button, then it would jump to a new page to
prepare the release.
+
+Filling in all the necessary information required by the form. And in the
bottom of the form, choose the "This is a pre-release" checkbox. Finally, click
the "Publish release" button to finish the step.
+
+> Note: the pre-release note is used for voting purposes. It would be marked
with a **Pre-release** tag. After all the voting works(dev and general) are
finished, do not forget to inverse the "This is a pre-release" checkbox. The
pre-release version comes from vx.y.z-incubating-rcN tags, and the final
version should come from vx.y.z-incubating tags.
+
## Vote on the release candidate
The release voting takes place on the Apache Kyuubi (Incubating) developers
list (the (P)PMC is voting).
