[kudu] 02/08: [docs] a small update on RELEASING.adoc

[al...@apache.org]

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

alexey pushed a commit to branch branch-1.11.x
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit 266589c5b6eab1bd9020bc364fda211a2a046798
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Thu Oct 10 10:36:31 2019 -0700

    [docs] a small update on RELEASING.adoc
    
    Minor clarification on the username to use for logging in at
    gerrit.cloudera.org to update gerrit mirroring configuration.  Also,
    fixed formatting of the numbered sub-list and added an item to verify
    that gerrit has been restarted successfully.
    
    Change-Id: I3046e24b63b1d70a0e5f4d5d28b5335a26255137
    Reviewed-on: http://gerrit.cloudera.org:8080/14411
    Tested-by: Kudu Jenkins
    Reviewed-by: Adar Dembo <ad...@cloudera.com>
    (cherry picked from commit 6f49b2dc076603d83d4ce2abaab47eab960b47bd)
    Reviewed-on: http://gerrit.cloudera.org:8080/14448
    Reviewed-by: Alexey Serbin <as...@cloudera.com>
---
 RELEASING.adoc | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/RELEASING.adoc b/RELEASING.adoc
index 6f19b46..a09a409 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -67,17 +67,19 @@ in `master`.
   have to perform this step because SSH access is behind a firewall. The steps
   are as follows:
   1. Ensure your public SSH key is in `~gerrit/.ssh/authorized_keys` on gerrit.cloudera.org
-  2. From behind the firewall, `ssh gerrit.cloudera.org` to log in.
-  3. Change to the gerrit user, `sudo su gerrit`
-  4. Back up the existing replication configuration file by executing
+  2. From behind the firewall, `ssh gerrit@gerrit.cloudera.org` to log in.
+  3. Back up the existing replication configuration file by executing
      `cp ~/etc/replication.config ~/etc/replication.config.bak.`date '+%Y%m%d.%H%M%S'``
-  5. Edit `etc/replication.config` to add a line for the new branch, such as `branch-1.x.y`
-  6. Send email to the dev lists for Kudu and Impala (dev@kudu.apache.org and
+  4. Edit `etc/replication.config` to add a line for the new branch, such as `branch-1.x.y`
+  5. Send email to the dev lists for Kudu and Impala (dev@kudu.apache.org and
      dev@impala.apache.org) indicating that you are going to restart Gerrit
      (link:https://s.apache.org/2Wj7[example]). It is best to do the restart at
      some time of day when you don't expect many people to be using the system,
      since Gerrit can take a few minutes to restart.
-  7: Restart Gerrit, `~/bin/gerrit.sh restart`
+  6. Restart Gerrit: `~/bin/gerrit.sh restart`
+  7. Make sure Gerrit has been successfully restarted: after a few minutes,
+     try to open the link:https://gerrit.cloudera.org/#/admin/projects[project list]
+     page in your favorite browser.
 
 . As needed, patches can be cherry-picked to the new branch.