Matt, this one is biting me on the *** in 0.20.205, but I'm not seeing how to set the target version, perhaps because it is fixed in 0.22.
https://issues.apache.org/jira/browse/HADOOP-6453 Seems like an easy low-risk fix that's been out there for a few years. What is the best way to flag this for review? Thanks, - Tim. ________________________________________ From: mfo...@hortonworks.com [mfo...@hortonworks.com] On Behalf Of Matt Foley [ma...@apache.org] Sent: Friday, November 04, 2011 5:56 PM To: common-dev@hadoop.apache.org Subject: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov. Hi all, I propose to make a 0.20.205.1 candidate soon, with the following sets of patches: - deficiencies in HBase support, pointed out by the HBase team and others - deficiencies in webhdfs support on secure clusters - a couple last-minute fixes submitted to branch-0.20-security-205 that were too late to be included in 205.0 If you would like other patches included, and you feel it is appropriate to have them in 205.1 rather than waiting for 206.0, please declare them by setting the "Target Versions" field in their Jiras, and they will receive due consideration, assuming that the proposed patch is actually contributed, tested, reviewed, approved, and committed to branch-0.20-security-205 by the freeze date :-) I would like to make the rc0 candidate next Friday, so I propose to declare 205.1 code freeze at noon, PST, Friday 11 Nov. If this is a problem for anyone, please let me know. Thank you, and best regards, --Matt (Release Manager) The information and any attached documents contained in this message may be confidential and/or legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender immediately by return e-mail and destroy all copies of the original message.
