All ASF releases are in fact source releases, and the fact that we provide binaries is technically "convenience", from what I've been told. So, you can vote based on the source contents of the tarball -- if it compiles to something you feel is satisfactory for a release, you can vote +1 even if you had to recompile.
Given that we're now moving to multiple builds, it may make sense to have the release votes against source and also include a tarball for 1.0, 0.22, 0.23, etc. -Todd On Tue, Mar 13, 2012 at 8:33 PM, Ted Yu <[email protected]> wrote: > I assume we should use 'mvn -Dhadoop.profile=22' to build HBase jar for > deployment. > > Since it would be a different jar, I wonder whether the vote would count. > > Cheers > > On Tue, Mar 13, 2012 at 8:15 PM, Stack <[email protected]> wrote: > >> On Tue, Mar 13, 2012 at 8:03 PM, Ted Yu <[email protected]> wrote: >> > I wanted to validate this release. >> > But all the clusters I have access to run hadoop 0.22 >> > >> > Since the tar ball was built based on hadoop 1.0, I am not sure what to >> do >> > here. >> > >> >> Download the tar ball, replace the bundled hadoop under the lib dir >> with your hadoop 0.22 version and then run it on an hadoop 0.22 >> cluster? If its as good/bad as 0.92.x, you should be able to +1. See >> end of this section: http://hbase.apache.org/book.html#hadoop >> Thanks, >> St.Ack >> -- Todd Lipcon Software Engineer, Cloudera
