This is an automated email from the ASF dual-hosted git repository.
alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/master by this push:
new db06810 [docs] add step to set the release date in Apache JIRA
db06810 is described below
commit db0681061a44fae7b6206994ceedc5367da63692
Author: Alexey Serbin <[email protected]>
AuthorDate: Fri Jun 12 00:24:41 2020 -0700
[docs] add step to set the release date in Apache JIRA
Updated RELEASING.adoc, adding a step to set the release date
in Apache JIRA after releasing a new version of Kudu.
Change-Id: I4ed238b9ff673a87bc4910bf40cfbbfaa0497e51
Reviewed-on: http://gerrit.cloudera.org:8080/16070
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke <[email protected]>
---
RELEASING.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/RELEASING.adoc b/RELEASING.adoc
index ddd45b1..e0e3f1f 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -399,3 +399,10 @@ Note: You can upload to the test PyPi by adding
`1.7.1`). If releasing a maintenance version, delete the previous maintenance
branch (e.g. if you released `1.2.1`, delete `1.2.0`). Also delete any
release candidates from the dev SVN.
+
+. Set the release date for the just released version in
+ link:https://issues.apache.org[Apache JIRA] or ask someone with permission
+ to do so. After logging in, in the left sidebar switch to the `Releases`
item.
+ Once at the `Releases` page, apply the `Unreleased` filter. In the row
+ corresponding to the new release, click at the ellipsis in the `Action`
+ column and select the `Release` item, setting the appropriate release date.
