Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9BF7E95CF for ; Mon, 8 Dec 2014 19:49:28 +0000 (UTC) Received: (qmail 84891 invoked by uid 500); 8 Dec 2014 19:49:26 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 84624 invoked by uid 500); 8 Dec 2014 19:49:26 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 84488 invoked by uid 99); 8 Dec 2014 19:49:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 19:49:25 +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 rarecactus@gmail.com designates 74.125.82.41 as permitted sender) Received: from [74.125.82.41] (HELO mail-wg0-f41.google.com) (74.125.82.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 19:49:00 +0000 Received: by mail-wg0-f41.google.com with SMTP id y19so7054466wgg.28 for ; Mon, 08 Dec 2014 11:48:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=7drQXqRXOo6Ldp4o094guIB22V818QVIz6P4OCA6ivw=; b=QzkiPnYP7MT/KEpIzZYPJ5X1JEmFPnkdpGvETF7gDVt9znS/SgdDe/HwsF7Pnib2HM ZSdMu1yMOG/sFIo98mrSxxM64PKaqjwPMH/EM/4VEAXn9Im2d7WTwXviuUAmK2YEhWfh AuF9SxZvcmTvRAhr1bLLe1mNNQkJHwh1Ntj+Y6PIqq6j7FbwRNgkTBma+Jv9EFrYwgAt /zl2AgGR6gxuWMJ+5AuhgKYPrWdDwd9oIi0yc2hDFbPTSXI0rhPz+DeVZFg54Dem0/cs U+VY/O8v2kVoKBYY/4Z8fZfIaP1J3ZkyE7SBr/ZepKwSJjALZwTuUCp7lM6N1hrnWOVu vDFw== MIME-Version: 1.0 X-Received: by 10.194.5.227 with SMTP id v3mr49119763wjv.63.1418068139697; Mon, 08 Dec 2014 11:48:59 -0800 (PST) Sender: rarecactus@gmail.com Received: by 10.194.68.231 with HTTP; Mon, 8 Dec 2014 11:48:59 -0800 (PST) In-Reply-To: References: <6150349314371432261@unknownmsgid> <4E0B02FE-AEFC-4EF8-8AA6-F66C111E8DDA@hortonworks.com> Date: Mon, 8 Dec 2014 11:48:59 -0800 X-Google-Sender-Auth: Ej6WbkFiGUpwV2wgRiJVplTFvu4 Message-ID: Subject: Re: Thinking ahead to hadoop-2.7 From: Colin McCabe To: "hdfs-dev@hadoop.apache.org" Cc: "mapreduce-dev@hadoop.apache.org" , "common-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Dec 5, 2014 at 11:15 AM, Karthik Kambatla wrote: > It would be nice to cut the branch for the next "feature" release (not just > Java 7) in the first week of January, so we can get the RC out by the end > of the month? > > Yesterday, this came up in an offline discussion on ATS. Given people can > run 2.6 on Java 7, is there merit to doing 2.7 with the exact same bits > targeting Java 7? I am okay with going through with it, as long as it > doesn't delay the next feature release. > > Thoughts? That's a good point. I think it's important to point out that most of our users are already on JDK7. We shouldn't think of this decision as adding support for something new, we should think about it as taking something away (JDK6 support). I think it's good that we are finally moving away from supporting JDK6, but I'm not completely sure that we need to devote a whole release to that. Are there a lot of open JDK7 issues that would require a release to straighten out? best, Colin > > On Wed, Dec 3, 2014 at 8:59 AM, Sangjin Lee wrote: > >> Late January sounds fine to me. I think we should be able to wrap it up >> much earlier than that (hopefully). >> >> Thanks, >> Sangjin >> >> On Tue, Dec 2, 2014 at 5:19 PM, Arun C Murthy wrote: >> >> > Sangjin/Karthik, >> > >> > How about planning on hadoop-2.8 by late Jan? Thoughts? >> > >> > thanks, >> > Arun >> > >> > On Dec 2, 2014, at 11:09 AM, Sangjin Lee wrote: >> > >> > > If 2.7 is being positioned as the JDK7-only release, then it would be >> > good >> > > to know how 2.8 lines up in terms of timing. Our interest is landing >> the >> > > shared cache feature (YARN-1492)... Thanks. >> > > >> > > Sangjin >> > > >> > > On Mon, Dec 1, 2014 at 2:55 PM, Karthik Kambatla >> > wrote: >> > > >> > >> Thanks for starting this thread, Arun. >> > >> >> > >> Your proposal seems reasonable to me. I suppose we would like new >> > features >> > >> and improvements to go into 2.8 then? If yes, what time frame are we >> > >> looking at for 2.8? Looking at YARN, it would be nice to get a release >> > with >> > >> shared-cache and a stable version of reservation work. I believe they >> > are >> > >> well under way and should be ready in a few weeks. >> > >> >> > >> Regarding 2.7 release specifics, do you plan to create a branch off of >> > >> current branch-2.6 and update all issues marked fixed for 2.7 to be >> > fixed >> > >> for 2.8? >> > >> >> > >> Thanks >> > >> Karthik >> > >> >> > >> On Mon, Dec 1, 2014 at 2:42 PM, Arun Murthy >> > wrote: >> > >> >> > >>> Folks, >> > >>> >> > >>> With hadoop-2.6 out it's time to think ahead. >> > >>> >> > >>> As we've discussed in the past, 2.6 was the last release which >> supports >> > >>> JDK6. >> > >>> >> > >>> I'm thinking it's best to try get 2.7 out in a few weeks (maybe by >> the >> > >>> holidays) with just the switch to JDK7 (HADOOP-10530) and possibly >> > >>> support for JDK-1.8 (as a runtime) via HADOOP-11090. >> > >>> >> > >>> This way we can start with the stable base of 2.6 and switch over to >> > >>> JDK7 to allow our downstream projects to use either for a short time >> > >>> (hadoop-2.6 or hadoop-2.7). >> > >>> >> > >>> I'll update the Roadmap wiki accordingly. >> > >>> >> > >>> Thoughts? >> > >>> >> > >>> thanks, >> > >>> Arun >> > >>> >> > >>> -- >> > >>> CONFIDENTIALITY NOTICE >> > >>> NOTICE: This message is intended for the use of the individual or >> > entity >> > >> to >> > >>> which it is addressed and may contain information that is >> confidential, >> > >>> privileged and exempt from disclosure under applicable law. If the >> > reader >> > >>> of this message is not the intended recipient, you are hereby >> notified >> > >> that >> > >>> any printing, copying, dissemination, distribution, disclosure or >> > >>> forwarding of this communication is strictly prohibited. If you have >> > >>> received this communication in error, please contact the sender >> > >> immediately >> > >>> and delete it from your system. Thank You. >> > >>> >> > >> >> > >> > -- >> > Arun C. Murthy >> > Hortonworks Inc. >> > http://hortonworks.com/hdp/ >> > >> > >> > >> > -- >> > CONFIDENTIALITY NOTICE >> > NOTICE: This message is intended for the use of the individual or entity >> to >> > which it is addressed and may contain information that is confidential, >> > privileged and exempt from disclosure under applicable law. If the reader >> > of this message is not the intended recipient, you are hereby notified >> that >> > any printing, copying, dissemination, distribution, disclosure or >> > forwarding of this communication is strictly prohibited. If you have >> > received this communication in error, please contact the sender >> immediately >> > and delete it from your system. Thank You. >> > >> > > > > -- > -- Karthik Kambatla, Software Engineer, Cloudera > -------------------------------------------- > Q: Why is this email five sentences or less? > A: http://five.sentenc.es