[
https://issues.apache.org/jira/browse/HBASE-22395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837513#comment-16837513
]
Sean Busbey edited comment on HBASE-22395 at 5/10/19 6:33 PM:
--------------------------------------------------------------
current section from http://hbase.apache.org/book.html#hbase.rc.voting
{quote}
h3. Voting on Release Candidates
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, Release Policy
(https://github.com/rectang/asfrelease/blob/master/release.md ).
bq. 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 HBase, mail # dev - On recent discussion clarifying ASF release
policy for how we arrived at this process ( https://s.apache.org/2xxr ).
{quote}
I'm happy to review any proposed improvement here, naturally.
was (Author: busbey):
current section from http://hbase.apache.org/book.html#hbase.rc.voting
{quote}
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, Release Policy
(https://github.com/rectang/asfrelease/blob/master/release.md ).
bq. 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 HBase, mail # dev - On recent discussion clarifying ASF release
policy for how we arrived at this process ( https://s.apache.org/2xxr ).
{quote}
I'm happy to review any proposed improvement here, naturally.
> Document RC voting guidelines in ref guide
> ------------------------------------------
>
> Key: HBASE-22395
> URL: https://issues.apache.org/jira/browse/HBASE-22395
> Project: HBase
> Issue Type: Improvement
> Components: community, documentation
> Reporter: Artem Ervits
> Priority: Major
>
> Document all necessary and suggested steps to vote on a release.
>
> {quote}
> There are only a handful necessary checks a PMC member must do on every
> release, and all of them relate to packaging, LICENSE and NOTICE files, and
> license auditing, which can be accomplished by running the RAT tool, by
> attempting to compile from source (unit tests optional), and through manual
> inspection of LICENSE and NOTICE files in the source distribution and
> embedded in a sample of the binaries. This entire process should take you
> less than 15 minutes, from my experience. This is the baseline.
> Any individual PMCer may opt to do more than the baseline, but it is
> optional. Personally I would also read the compatibility report, and then
> run the unit test suite in the background and come back to it when finished
> to complete the voting task. In my opinion now that is the baseline tasks
> any HBase PMC voter should take. Beyond that, at least for my releases, you
> can read the vote email to find the additional functional and performance
> checks I might have done and factor that in to your voting confidence. You
> can also run them yourselves, but is totally optional.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
