Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3FEA29906 for ; Mon, 5 Mar 2012 21:46:45 +0000 (UTC) Received: (qmail 10382 invoked by uid 500); 5 Mar 2012 21:46:43 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 10332 invoked by uid 500); 5 Mar 2012 21:46:43 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 10322 invoked by uid 99); 5 Mar 2012 21:46:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2012 21:46:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.160.48] (HELO mail-pw0-f48.google.com) (209.85.160.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2012 21:46:38 +0000 Received: by pbcup7 with SMTP id up7so6165725pbc.35 for ; Mon, 05 Mar 2012 13:46:17 -0800 (PST) Received-SPF: pass (google.com: domain of acm@hortonworks.com designates 10.68.237.71 as permitted sender) client-ip=10.68.237.71; Authentication-Results: mr.google.com; spf=pass (google.com: domain of acm@hortonworks.com designates 10.68.237.71 as permitted sender) smtp.mail=acm@hortonworks.com Received: from mr.google.com ([10.68.237.71]) by 10.68.237.71 with SMTP id va7mr8094806pbc.100.1330983977757 (num_hops = 1); Mon, 05 Mar 2012 13:46:17 -0800 (PST) Received: by 10.68.237.71 with SMTP id va7mr7005214pbc.100.1330983977647; Mon, 05 Mar 2012 13:46:17 -0800 (PST) Received: from [10.10.10.144] (host1.hortonworks.com. [70.35.59.2]) by mx.google.com with ESMTPS id g9sm14339968pba.6.2012.03.05.13.46.15 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 05 Mar 2012 13:46:16 -0800 (PST) From: Arun C Murthy Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-83-489459183 Subject: Re: Some s3n improvements to the 1.0 branch? Also, is there a 1.1.0 planned? Date: Mon, 5 Mar 2012 13:46:17 -0800 In-Reply-To: To: common-dev@hadoop.apache.org References: , Message-Id: <517CD6E7-02B4-4895-B9A2-09C00A963B7D@hortonworks.com> X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQnkwGfv6TgbFAarnR01ngo527obonigEwuHO8fO7r9UuFBdCw/AyEbFRqpfiBcvAWrm4Vj2 X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-83-489459183 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Apologies for being pedantic: please set the target-version to 1.0.2. = The committer/RM set the fix-version after it's merged into the release = branch. thanks, Arun On Mar 5, 2012, at 12:45 PM, Jagane Sundar wrote: > Thanks, Eli. >=20 > I have uploaded a re-spin of the patch for HADOOP-5836 to the Jira. > My patch for HADOOP-8136 needs to have this patch for HADOOP-5836 = applied first. I will mark HADOOP-8136 with fixVersion 1.0.2. >=20 > Jagane > ________________________________________ > From: Eli Collins [eli@cloudera.com] > Sent: Monday, March 05, 2012 10:25 AM > To: common-dev@hadoop.apache.org > Subject: Re: Some s3n improvements to the 1.0 branch? Also, is there a = 1.1.0 planned? >=20 > Hey Jagane, >=20 > You can target your patches against branch-1.0, and then mark them > with fixVersion 1.0.2 if you'd like the RM to pull them in for the > next dot release. >=20 > Thanks, > Eli >=20 >=20 > On Mon, Mar 5, 2012 at 9:47 AM, Jagane Sundar = wrote: >> Hello All, >>=20 >> I would like to make some enhancements to the s3n driver in = branch-1.0. >>=20 >> Specifically, I would like to accomplish the following: >> 1. Backport HADOOP-5836 >> 2. Update the jets3t library from 0.6.1 to 0.8.1. This entails code = changes in the s3n driver to track API changes in jets3t version 0.8.1. = I filed a jira, HADOOP-8136, to track this. >>=20 >> The question I have is this - where does it make sense to put these = fixes in? Is there a Release 1.1.0 planned? Or is it merely a 1.0.[23] = type of change? >>=20 >> Thanks in advance, >> Jagane -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ --Apple-Mail-83-489459183--