On Feb 2, 2009, at 6:18 PM, Doug Judd wrote:
Comments inline ...
On Mon, Feb 2, 2009 at 4:23 PM, Konstantin Shvachko <s...@yahoo-
inc.com>wrote:
> > What do you recommend?
>
> In general. There may be people/organizations, which will not
compromise
> on the reduced functionality in favor of the stability, this is
> understandable.
> I would propose to create a separate (unofficial experimental)
branch,
> which
> would track changes like HADOOP-4379. The branch may later either
die when
> the
> main stream is fixed or be merged with the trunk if the changes
proved to
> be stable.
Sure, that sounds reasonable. One thing I would caution against is
spending
a lot of time doing incremental patchwork on something that needs a
ground-up overhaul. I would much rather wait a couple of months
longer and
get software that is based on a well thought out design that is
fundamentally sound. Ultimately that will be the fastest path to
stability.
Agree.
sanjay
