It would be really nice to avoid committing large changes to 96 henceforth before we have the RC5. Otherwise it would never stabilize at this rate.
On Wed, Oct 9, 2013 at 10:45 AM, Enis Söztutar <[email protected]> wrote: > I just committed https://issues.apache.org/jira/browse/HBASE-9730 for > this. > Time for another RC, what do you think? > > You know what they say, sixth time is the charm. > Enis > > > On Tue, Oct 8, 2013 at 2:43 PM, Enis Söztutar <[email protected]> wrote: > > > HEADS UP: > > I think we may have to sink this one. Our tests ITBLL and ITLAV with CM > > fails consistently, and we suspect a problem with HBASE-9612 (although > not > > confirmed yet) > > > > More details are coming soon after more digging into logs. > > Enis > > > > > > On Mon, Oct 7, 2013 at 1:46 PM, Stack <[email protected]> wrote: > > > >> On Mon, Oct 7, 2013 at 10:05 AM, Steve Loughran <[email protected] > >> >wrote: > >> > >> > go > >> > > >> > well, those are the .gz files, not the JARs, I'll have to download and > >> > check... > >> > > >> > > >> Give me list of jars you want a sha for and I'll run them for you > against > >> the build RC (and publish it) > >> > >> > >> > >> > BTW, there's a new Hadoop RC out in staging: 2.2.0 > >> > > >> > > >> > The RC is available at: > >> > http://people.apache.org/~acmurthy/hadoop-2.2.0-rc0 > >> > The RC tag in svn is here: > >> > http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.2.0-rc0 > >> > >> > >> Yeah. Hopefully our RC works against it (I didn't try it). > >> > >> St.Ack > >> > > > > > -- 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.
