hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: Next releases
Date Tue, 12 Nov 2013 19:54:44 GMT
On Mon, Nov 11, 2013 at 2:57 PM, Colin McCabe <cmccabe@alumni.cmu.edu>wrote:

> To be honest, I'm not aware of anything in 2.2.1 that shouldn't be
> there.  However, I have only been following the HDFS and common side
> of things so I may not have the full picture.  Arun, can you give a
> specific example of something you'd like to "blow away"?

I agree with Colin. If we've been backporting things into a patch release
(third version component) which don't belong, we should explicitly call out
those patches, so we can learn from our mistakes and have a discussion
about what belongs. Otherwise we'll just end up doing it again. Saying
"there were a few mistakes, so let's reset back a bunch of backport work"
seems like a baby-with-the-bathwater situation.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message