[hbase] branch branch-2 updated: HBASE-22379 Fixed Markdown in 'Voting on Release Candidates' section

[ja...@apache.org]

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

janh pushed a commit to branch branch-2
in repository https://gitbox.apache.org/repos/asf/hbase.git


The following commit(s) were added to refs/heads/branch-2 by this push:
     new 9bb57b8  HBASE-22379 Fixed Markdown in 'Voting on Release Candidates' section
9bb57b8 is described below

commit 9bb57b89c8f6f1fc26f50a9a27b3454b60b3e803
Author: Jan Hentschel <ja...@ultratendency.com>
AuthorDate: Wed May 8 10:50:52 2019 +0200

    HBASE-22379 Fixed Markdown in 'Voting on Release Candidates' section
---
 src/main/asciidoc/_chapters/developer.adoc | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/src/main/asciidoc/_chapters/developer.adoc b/src/main/asciidoc/_chapters/developer.adoc
index 32432ff..8a2c33e 100644
--- a/src/main/asciidoc/_chapters/developer.adoc
+++ b/src/main/asciidoc/_chapters/developer.adoc
@@ -861,14 +861,19 @@ It will put a snapshot up into the apache snapshot repository for you.
 
 Everyone is encouraged to try and vote on HBase release candidates.
 Only the votes of PMC members are binding.
-PMC members, please read this WIP doc on policy voting for a release candidate, link:https://github.com/rectang/asfrelease/blob/master/release.md[Release
-                Policy]. [quote]_Before casting +1 binding votes, individuals are required to
-                download the signed source code package onto their own hardware, compile it as
-                provided, and test the resulting executable on their own platform, along with also
-                validating cryptographic signatures and verifying that the package meets the
-                requirements of the ASF policy on releases._ Regards the latter, run +mvn apache-rat:check+ to verify all files are suitably licensed.
-See link:http://search-hadoop.com/m/DHED4dhFaU[HBase, mail # dev - On
-                recent discussion clarifying ASF release policy].
+PMC members, please read this WIP doc on policy voting for a release candidate, link:https://github.com/rectang/asfrelease/blob/master/release.md[Release Policy].
+
+[quote]
+____
+Before casting +1 binding votes, individuals are required to
+download the signed source code package onto their own hardware, compile it as
+provided, and test the resulting executable on their own platform, along with also
+validating cryptographic signatures and verifying that the package meets the
+requirements of the ASF policy on releases.
+____
+
+Regards the latter, run `mvn apache-rat:check` to verify all files are suitably licensed.
+See link:http://search-hadoop.com/m/DHED4dhFaU[HBase, mail # dev - On recent discussion clarifying ASF release policy]
 for how we arrived at this process.
 
 [[hbase.release.announcement]]