Agreed on confusion regardless what we pick. But not sure I see what the value is in sticking to 0.21? Hadoop is also releasing a "development 0.21" release and people will think these two things are tied together, though they are not.
I'm a big +1 on 0.90 for the next release. For the development release, we could call it 0.80 or 0.89. I agree we're not 1.0 yet but feel strongly that we're nearing it and the next release is getting us most of the way there. Once we stabilize it out in the world and add whatever big features we think are left, I'm confident we can get to 1.0 soon after. We're already fairly stable from an API perspective and I don't see any big changes in the pipeline that would prevent backwards compatibility. So in moving towards 1.0, I'd like to get our version numbers up to point to that fact, thus my vote for 0.90. IMO 0.30 says "we're not tied to hadoop anymore" and "we're bigger than 0.20" but not much else. 0.90 says we're approaching a 1.0 and HBase is becoming a legitimate piece of software you can trust your 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, May 20, 2010 10:54 AM > To: dev@hbase.apache.org > Subject: Re: Version number of next release > > On Thu, May 20, 2010 at 10:48 AM, Andrew Purtell > <apurt...@apache.org>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.21 (being billed as an unstable release at least for 0.21.0) > and > > generally not quite understand why our version number is the same if > we have > > no tie to the Hadoop version. So, I am generally -1 on calling this > next > > HBase release 0.21.0. > > > > I think there is going to be some level of confusion no matter what > and > > calling our next as-proposed unstable release series 0.21 makes sense > to me > > at least. > > > > > I agree - I should have included that in this email, but wanted to > divorce > the two discussions (naive of me to think that could happen ;-) ) > > I think for the development series, we are going to be discouraging new > users from downloading and trying it unless they're fine working > through > some problems. So a bit of confusion on a dev release series is no big > deal. > The "big" release, though, should be clearly separated. > > -Todd > > -- > Todd Lipcon > Software Engineer, Cloudera
