On Thu, Mar 21, 2013 at 3:44 PM, Stack <[email protected]> wrote: > > I'm thinking that we should have a hbase-0.95*-bin.tar.gz and a > hbase-0.95-src.tar.gz. And release them together.
+1 When you untar the src over the bin you will get something you can build if > you wanted to (so pom.xml would be over in src). Any preferences? > I like better hbase-src be a superset of -bin. I should be able to download one package if I want runnable, buildable bits; untaring one archive over another strikes me as odd. I need to go through the lib dir and purge the transtiive includes we don't > need. Its a pain figuring what we do and do not need. Maybe maven can help you here, with the dependency:tree target. Useful making the evaluation are the fancy hbase-it tools that have been > coming in; I can run suite of tests w/ the runtime and see what breaks. > For hbase-it tests to work, it looks like junit needs to be included as a > runtime dependency. We ok w/ that? > As much as I like having a smoketest (and I think hbase-it is a nice candidate), it'll be a little messy. In addition to junit, hbase-it will bring in other hbase-*-test jars as runtime dependencies too. What shall we ship? A single hbase that defaults to hadoop1? Or we build > a hadoop2 too and ship a binary that includes hadoop2 also? > For 0.95, might as well support both. I'm concerned about test coverage, stability on hadoop2 and would hate to see that as a hard-blocker from releasing a 0.96 with all these fancy new features the community has been waiting (and waiting, and waiting) for. -n
