hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Gray <jg...@facebook.com>
Subject RE: Development release next week
Date Sat, 19 Jun 2010 01:10:38 GMT
So then is the plan to branch and then cherry-pick fixes until the first release of it?

Following the release, would we continue to cherry-pick bug fixes and possibly have a second
dev release?

I'm thinking cutting a branch soon and cherry-picking fixes between now and the summit might
make sense.  But then we should not separately support that release (as in, if bugs are found
that are no longer relevant or are implemented differently at the tip of trunk, we don't fix
them in the branch, only in trunk).  I think there's a decent chance of this because of some
remaining largish changes going in.

A follow-up dev release would still be possible but should be a re-cut off a fresher trunk
with more goodness in it rather than a patched version of the first dev release.


> -----Original Message-----
> From: Todd Lipcon [mailto:todd@cloudera.com]
> Sent: Friday, June 18, 2010 4:58 PM
> To: dev
> Subject: Development release next week
> 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

View raw message