Thanks for the list, Jason.  I scanned through them and except HDFS-5356, all jiras were currently targeted for 2.4.0. I changed the target version of HDFS-5356 to 2.4.0, so now all are targeted for 2.4.0.

Assuming "2.3.0" label is clean and doesn't need any mass/batch update, I think we can go over these jiras and re-target for 2.3.0, if one needs to be fixed in 2.3.0. 


On Friday, January 24, 2014 10:07 AM, Jason Lowe <[EMAIL PROTECTED]> wrote:
I just committed the addendum patch for HADOOP-9652 which should resolve
the performance issue.

Speaking of critical issues to fix for 2.3, I do wonder what to do with
all the Blocker/Criticals targeted for 2.4 (the old branch-2 HEAD
release) which apparently is now going to be 2.3 (the new branch-2 HEAD
release).  We should either get these resolved before the 2.3 release or
decide which ones aren't really blockers or that critical for 2.3 and
target them for a future release (e.g.: 2.4). According to my
calculations, there's currently 24 JIRAs that need to be scrubbed

On 01/23/2014 06:53 PM, Sangjin Lee wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB