From dev-return-14203-apmail-sqoop-dev-archive=sqoop.apache.org@sqoop.apache.org Tue Oct 21 17:12:51 2014 Return-Path: X-Original-To: apmail-sqoop-dev-archive@www.apache.org Delivered-To: apmail-sqoop-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 313E017DDA for ; Tue, 21 Oct 2014 17:12:51 +0000 (UTC) Received: (qmail 38393 invoked by uid 500); 21 Oct 2014 17:12:51 -0000 Delivered-To: apmail-sqoop-dev-archive@sqoop.apache.org Received: (qmail 38360 invoked by uid 500); 21 Oct 2014 17:12:51 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 38348 invoked by uid 99); 21 Oct 2014 17:12:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2014 17:12:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jarcec@gmail.com designates 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2014 17:12:24 +0000 Received: by mail-pa0-f44.google.com with SMTP id et14so1808797pad.17 for ; Tue, 21 Oct 2014 10:11:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=urP5EB0F7tw88Mi/oGlIw3FfV7wyd1L4JT8PdOH5zxM=; b=vqW5hyuXXmVBLPFw/KWd1WhrZrKqnv9VhxmoTsiMvMQRwgwnPdg/qi5h3IsIKP9sCh d1ZQwZAikRIzFT8o+MlTX9NUGzjQq5FR+5KT00waOmxwZgPksu1rGpOZsX7jwlfitImo SIYh4siilngDM5GGBQVWo74JiCbRbQ8DM0zeALjYjQOr5wAwPn7ewELHNJti3GJ5KPwk jgxIQK1Kxywv9wzU0lyJHnPmJCE7/3qry7VP2UztuUQ8/ozsXdcplSsd9taX4jY7hUM4 RdVDFSNvBdorAKJU+NEBEoTQa5xzcbGyCQt/jaZKH8C6xd4ubkSoqYIKOwnW6ra06Nj5 fHsg== X-Received: by 10.66.187.173 with SMTP id ft13mr35875441pac.41.1413911497822; Tue, 21 Oct 2014 10:11:37 -0700 (PDT) Received: from [172.16.2.132] ([74.217.76.11]) by mx.google.com with ESMTPSA id uw6sm12521733pac.41.2014.10.21.10.11.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 10:11:36 -0700 (PDT) Sender: Jarek Jarcec Cecho Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: Sqoop 1.99.4 Release? From: Jarek Jarcec Cecho In-Reply-To: Date: Tue, 21 Oct 2014 10:11:35 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: dev@sqoop.apache.org X-Mailer: Apple Mail (2.1990.1) X-Virus-Checked: Checked by ClamAV on apache.org We=E2=80=99ve lastly released Sqoop 2 last year, so I think that it=E2=80=99= s definitely time for a new release. +1 on the release and +1 on Gwen to be the release manager. Jarcec > On Oct 21, 2014, at 9:35 AM, Gwen Shapira = wrote: >=20 > +1 for doing a new release. >=20 > I'll be happy to volunteer as a release manager. >=20 > On Tue, Oct 21, 2014 at 12:24 PM, Abraham Elmahrek = wrote: >> It seems a lot has changed in Sqoop2. For example, Sqoop2 has been >> refactored to be more generic ( >> https://issues.apache.org/jira/browse/SQOOP-1367), APIs have been = changed >> and have been stabilizing as a result. >>=20 >> Let's do a new Sqoop2 release? If so, we could follow the same = approach >> we've had for the previous releases: one committer will volunteer as = a >> release mentor and one community volunteer to be release manager. I'm = up >> for being release mentor! >>=20 >> -Abe