You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kudu.apache.org by ad...@apache.org on 2019/11/02 05:22:03 UTC

[kudu] 01/02: [RELEASING.adoc] clarify on sending announcement email

This is an automated email from the ASF dual-hosted git repository.

adar pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit 93d836ad8a71e4a4ed7f4c1c4473fc831901ec6b
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Fri Nov 1 20:47:54 2019 -0700

    [RELEASING.adoc] clarify on sending announcement email
    
    Change-Id: If3823de44b68e380bdb06c5b2a7e445e18864ee3
    Reviewed-on: http://gerrit.cloudera.org:8080/14617
    Reviewed-by: Andrew Wong <aw...@cloudera.com>
    Tested-by: Kudu Jenkins
---
 RELEASING.adoc | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/RELEASING.adoc b/RELEASING.adoc
index 613f0c0..dc0d1ed 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -269,10 +269,16 @@ Note: You can upload to the test PyPi by adding
 . Once the review is finished and the commit is pushed, update the website following
   these link:https://github.com/apache/kudu/#deploying-changes-to-the-apache-kudu-web-site[instructions].
 
-. About 24 hours after the first step was completed, send an email to
+. About 24 hours after all artifacts have been published, send an email to
   user@kudu.apache.org, dev@kudu.apache.org, and announce@apache.org to
-  announce the release. The email should be similar to
-  link:https://s.apache.org/pduz[this].
+  announce the new release. The email should be similar to
+  link:https://s.apache.org/pduz[this]. The announcement email must be sent
+  from your apache.org address, otherwise apache.org mailer will not deliver
+  the message to the addressees of the announce@ group at least.  If using
+  gmail.com service for email correspondence, follow
+  link:https://support.google.com/mail/answer/22370?hl=en[this guide] to add
+  your apache.org address to be used as `From` address when sending email
+  messages.
 
 . About another 24 hours later, clean up the SVN. If releasing a new minor
   version, delete the oldest minor version branch in the release repo (e.g. if