Another thing I’ll add - whilst a simple +1 vote is enough, it really helps the rest of us if we state *what* we reviewed that helped us come to the conclusion.
If everyone checked licensing, and no-one ran a build, we’d know we had some extra work to do before we’d all feel comfortable. Upayavira On Wed, Apr 1, 2015, at 06:39 PM, Upayavira wrote: > for those here that aren't familiar with Apache style release votes, > here is some background. > > When we vote on a release candidate, we are saying two things: that we > believe it to be valid from a licensing perspective, and that we think > the code is in a good technical state to be released. The former is more > important than the latter. > > If you are considering voting, please do. Please download the artefact, > and review it. Check license headers and licence attribution, and then > build the code and run it. Then vote! > > Strictly speaking, it is the vote of members of the Incubator PMC that > count. However, demonstrating that the community is behind the release > is also crucially important, so whoever you are, committer or not, > programmer or not, please download the artefact and review some of it. > > Thanks! > > Upayavira
