Given that this can potentially be the base release for 96, should we wait for HBASE-8165 (protobuf upgrade to 2.5) to go in? Hadoop 2.1.0-beta release vote is currently ongoing.
On Thu, Aug 15, 2013 at 2:25 PM, Stack <[email protected]> wrote: > Here is our first 0.95.2 release candidate. Should we put this out as 0.95. > 2? > > Since 0.95.2 is a "Development" Series release [1], so lets keep the vote > period short. Please vote by this Monday, August 19th. The release has to > just basically "work". > > The release artifacts may be downloaded from: > > http://people.apache.org/~stack/hbase-0.95.2RC0/ > > ~340 issues have been closed since we put out 0.95.1 [2]. > > All feedback is welcome. We'd be interested in getting comments on > everything from the packaging, layout, through documentation, UI, and of > course, > any bugs found. I deployed to maven [3] and would particularly like > to hear from downstream projects on whether our maven packaging is > palatable. > > This is the last in the 0.95 series of development releases. You can think > of this > release as a 0.96.0-beta. No more features will come in on the 0.95 > branch. Only > fixes and polish are allowed from here on out. I intend to branch 0.96 > from 0.95 > branch next week and put up a 0.96.0RC0 soon after. > > Thanks, > St.Ack > > 1. http://hbase.apache.org/book.html#hbase.versioning > 2. > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%220.95.2%22%20AND%20project%20%3D%20HBASE%20ORDER%20BY%20issuetype%20DESC%2C%20priority%20DESC > 3. > https://repository.apache.org/content/repositories/releases/org/apache/hbase/hbase/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
