[
https://issues.apache.org/jira/browse/HBASE-22395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837497#comment-16837497
]
Andrew Purtell commented on HBASE-22395:
----------------------------------------
Also from the dev@ email that spawned this issue:
> I think the answer is simply that the PMC, as part of its responsibilities,
> should vote on all releases, irrespective of focus. This should be an
> expectation of PMC membership on the project. The Chair should kindly reach
> out and remind PMC members who are infrequently voting of this
> responsibility. This should be documented in our book in the section on PMC
> responsibility, and if that section doesn't exist, we should add one. What
> do you think?
> Document RC voting guidelines in ref guide
> ------------------------------------------
>
> Key: HBASE-22395
> URL: https://issues.apache.org/jira/browse/HBASE-22395
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Artem Ervits
> Priority: Major
>
> Document all necessary and suggested steps to vote on a release.
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
