[ 
https://issues.apache.org/jira/browse/HBASE-22395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837522#comment-16837522
 ] 

Zach York commented on HBASE-22395:
-----------------------------------

I think we should add an example using the automated script recently added in 
HBASE-21963. I think what is there provides what needs to be tested, but lacks 
some details on how. This was a bit of a barrier to me and took me a while to 
get a process down when I started trying to vote (there wasn't a nice script at 
that point :) ).  Of course people can go above and beyond the baseline, but 
documenting examples of how to test the baseline lowers the bar to entry 
significantly.

> 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)

Reply via email to