data in. The
> wave of development happening right now and the production use cases that
> will be propping up in the second half of this year confirm this.
>
> JG
>
> > -----Original Message-
> > From: Todd Lipcon [mailto:t...@cloudera.com]
> > Sent: Thursday, M
I mean, +1 on 0.66
On Thu, May 20, 2010 at 10:54 PM, Jean-Daniel Cryans
wrote:
> +1
>
> On Thu, May 20, 2010 at 10:50 PM, Stack wrote:
>> Lets not call it 0.21. I wanted to call it 0.66.0 so we could do a
>> logo for it: http://people.apache.org/~stack/66.jpg
>>
>> I'm good w/ 0.90.0 or 0.30.0.
+1
On Thu, May 20, 2010 at 10:50 PM, Stack wrote:
> Lets not call it 0.21. I wanted to call it 0.66.0 so we could do a
> logo for it: http://people.apache.org/~stack/66.jpg
>
> I'm good w/ 0.90.0 or 0.30.0.
>
> St.Ack
>
> On Thu, May 20, 2010 at 10:44 AM, Todd Lipcon wrote:
>> Hi HBasers,
>>
>>
Lets not call it 0.21. I wanted to call it 0.66.0 so we could do a
logo for it: http://people.apache.org/~stack/66.jpg
I'm good w/ 0.90.0 or 0.30.0.
St.Ack
On Thu, May 20, 2010 at 10:44 AM, Todd Lipcon wrote:
> Hi HBasers,
>
> Time for the second proposal of the day!
>
> I'd like to start a di
g right now and the production use cases that will be
propping up in the second half of this year confirm this.
JG
> -Original Message-
> From: Todd Lipcon [mailto:t...@cloudera.com]
> Sent: Thursday, May 20, 2010 10:54 AM
> To: dev@hbase.apache.org
> Subject: Re: Version num
On Thu, May 20, 2010 at 10:48 AM, Andrew Purtell wrote:
> > The current name for this release is 0.21. I think this is going to cause
> user confusion due to the previous "lockstep versioning" that HBase has had
> with regard to Hadoop. I think many people will assume they need to use
> Hadoop 0.2
> The current name for this release is 0.21. I think this is going to cause
> user confusion due to the previous "lockstep versioning" that HBase has had
> with regard to Hadoop. I think many people will assume they need to use
> Hadoop 0.21 (being billed as an unstable release at least for 0.21
Hi HBasers,
Time for the second proposal of the day!
I'd like to start a discussion around the version number of the upcoming
"durable HBase" release. The release I'm referring to is the one currently
being worked towards on trunk, and the one that FB and Cloudera plan to work
with for production
