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 0ce460b [RELEASING.adoc] add memo on 3rd-party license policy
0ce460b is described below
commit 0ce460bc90a7f788e3d916bd717f1dbf42f3efe3
Author: Alexey Serbin <[email protected]>
AuthorDate: Fri Nov 1 11:50:37 2019 -0700
[RELEASING.adoc] add memo on 3rd-party license policy
Added memo on the ASF 3rd-party license policy, emphasizing Category X.
Change-Id: Ie264b320e03d06b83c32f78304f4cb55854207f7
Reviewed-on: http://gerrit.cloudera.org:8080/14615
Reviewed-by: Andrew Wong <[email protected]>
Reviewed-by: Greg Solovyev <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
---
RELEASING.adoc | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/RELEASING.adoc b/RELEASING.adoc
index 479b101..613f0c0 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -22,8 +22,11 @@
This document gives the steps required to perform a Kudu release, and is a
resource for Kudu release managers. Make sure to read and understand the
link:http://www.apache.org/legal/release-policy.html[ASF policy on software
-releases] prior to conducting the release management activity. To edit or
-update this document, edit `RELEASING.adoc` in `master`.
+releases] prior to conducting the release management activity. Pay attention to
+the link:https://www.apache.org/legal/resolved.html[3rd-party license policy],
+making sure the release doesn't include anything from the
+link:https://www.apache.org/legal/resolved.html#category-x[Category X].
+To edit or update this document, edit `RELEASING.adoc` in `master`.
== Stating Intent to Release
