hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: Development release next week
Date Mon, 21 Jun 2010 19:33:19 GMT
+1 Sounds good to me.  Excising the commit might be a little tough
given other stuff went in on top of it to fix up issues found.

On Sun, Jun 20, 2010 at 11:16 PM, Todd Lipcon <todd@cloudera.com> wrote:
> I tried to do some cluster testing of trunk this afternoon/tonight and ran
> into several issues that blocked my ability to get up and running.
> Particularly, HBASE-2758, plus the inability to disable a table (forget the
> JIRA number, but it's up there)
> So, unless I hear any big -1s, I think it's best to revert the recent master
> changes for this dev release branch this week. There's still plenty of new
> stuff for users to try out, and I think the new master stuff is a bit too
> unstable yet for users to try. Let's do another dev release in a couple
> weeks once the new master stuff is more fully baked, and use this one to
> suss out bugs in all the other new stuff.
> Again, a reminder that we don't plan to support this branch post-release -
> it's just a preview for  users, so I don't think doing a release without the
> new master stuff is going to take steam out of continued fixup of these bugs
> in trunk proper.
> Sound good by everyone?
> -Todd
> On Fri, Jun 18, 2010 at 4:57 PM, Todd Lipcon <todd@cloudera.com> wrote:
>> Hey everyone,
>> As mentioned before, I'm hoping to have a development release we can talk
>> up at the Hadoop Summit at the end of this month.
>> To that end, I'm planning on branching trunk on Monday to try to go through
>> some short stabilization testing for a dev release at the end of the week.
>> I'm happy to do this as an internal branch at Cloudera, and just do a
>> release for CDH, or I can do a branch on the Apache SVN and an official
>> Apache release. Does anyone prefer one way or the other? Hopefully I will
>> branch from the state of trunk on Monday, but if that proves to be too
>> unstable I may rewind a week or two before the recent master changes, and
>> then cherry-pick some other fixes on top.
>> Note: this release is intended as a "technology preview" - we can get some
>> users trying out trunk on real clusters early so that we'll have an easier
>> time releasing when we think we're actually done. I plan on including a list
>> of known bugs and deficiencies - there's no chance we'll close out all the
>> blockers or finish the master rewrite, but I think the release will still be
>> valuable.
>> Any thoughts on this?
>> Thanks
>> -Todd
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
> --
> Todd Lipcon
> Software Engineer, Cloudera

View raw message