Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6C59E200B49 for ; Wed, 3 Aug 2016 10:35:27 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6AE59160A86; Wed, 3 Aug 2016 08:35:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8B49B160A64 for ; Wed, 3 Aug 2016 10:35:26 +0200 (CEST) Received: (qmail 7941 invoked by uid 500); 3 Aug 2016 08:35:25 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 7928 invoked by uid 99); 3 Aug 2016 08:35:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2016 08:35:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 12B7B189D57 for ; Wed, 3 Aug 2016 08:35:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.448 X-Spam-Level: * X-Spam-Status: No, score=1.448 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id h9wuNjB5tdgg for ; Wed, 3 Aug 2016 08:35:23 +0000 (UTC) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 529955F24E for ; Wed, 3 Aug 2016 08:35:22 +0000 (UTC) Received: by mail-io0-f173.google.com with SMTP id 38so236863409iol.0 for ; Wed, 03 Aug 2016 01:35:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=hJpWsY7f9N0ajinIVkODzCYUXYlCG9dnPN9KaRHdRV0=; b=spdqmJwLlaqZhJ2S11Tcc9uAhnDMa8g3hfNBsEOhyPsaYyu4DYht8PUpz3DJFJW6Cw yj3bYkr1n0UMW8smRy2Y+GJdT3IeHSv4PecHo2A2/I4WwqpGMJ2YsVnUE4mm4cPoxR5p 4Fxzs5kpFLp4NHQh6SfO2yLLCNQgiVBOlb5WxjyL3Dhziuwrk8lM7PrT1IfCUxp3KvFd AlRMfQXemD7jPjbBiosv9NkIbk6PI+5JUnLGXyQnQouP+IyWnXPBzD5iZ2SLPUd1CEGz gwF+vBZy8jvX+O1PsnjJRlHvw/oYdeoanY0uQCdjZxsv6MWM6dSFTscdLXoUa3AlFDOP hCyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=hJpWsY7f9N0ajinIVkODzCYUXYlCG9dnPN9KaRHdRV0=; b=YFvZGMDgMEq3+qeMSex4OvfW8OvX4cv4x9Y1+2eV9/UbQHYCALT7NUSLs34YccxJfk vqLPjFlbdt/34PaOhlUuPM8OASHbb6dwjHnLJqQIbyGj2RV8PZeNKxKy9yusNjbPAd2o JrK5NbAVP0Rel//Hz0ifWQK2x33uYxB4uVTVaVNiuYsNni961t6yh8dR1S38BAF2p5lm PeGqbkiAq8rtcjPlFlPfkOnYyO1MpgHdQSI+4FGRIVTEsHds6fn1LzLN+YpdvyqnSnYE n0oX73dmaTR8Yyfsly/FYRPelPbZSTYr7U1OpQQaNHbRPgC6KIZ8F/GWI9ldWo18tfRX sJ+g== X-Gm-Message-State: AEkooutTtgN97T/icjYiNR08pMhBwIgfwkv1PCWU1n5mzxLbChLJ0cCi0Ce6APfIDtXQuZ5eeZ9zzc+KGtaOVw== X-Received: by 10.107.16.228 with SMTP id 97mr75476834ioq.98.1470213320944; Wed, 03 Aug 2016 01:35:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.77.216 with HTTP; Wed, 3 Aug 2016 01:35:20 -0700 (PDT) In-Reply-To: References: <699156096.3559007.1469350166402.JavaMail.yahoo@mail.yahoo.com> <57A0BC02.3000100@gmail.com> <57A12ADE.2040709@gmail.com> From: Ankit Singhal Date: Wed, 3 Aug 2016 14:05:20 +0530 Message-ID: Subject: Re: new 4.8.0 RC? To: dev@phoenix.apache.org Content-Type: multipart/alternative; boundary=001a113edaaebd38f2053926b6eb archived-at: Wed, 03 Aug 2016 08:35:27 -0000 --001a113edaaebd38f2053926b6eb Content-Type: text/plain; charset=UTF-8 Yeah. Let's cut RC from 4.x only as there is not much difference except PHOENIX-3138, PHOENIX-3128,PHOENIX-3120. Which I think are fine for 4.8.0 too I'm running some tests for RC so no more commit please. On Wed, Aug 3, 2016 at 5:42 AM, James Taylor wrote: > I only pushed my changes to 4.x, so please let me know if I need to push > them to 4.8 branches, Ankit. > > Would be great to get an RC up today (IST time) for folks to test out > tomorrow (US time). > > Thanks, > James > > On Tue, Aug 2, 2016 at 4:21 PM, Josh Elser wrote: > > > Either works for me. The two changes I'm committing today have just gone > > to 8 branches instead of 4. > > > > Ankit, do you have a preference as RM what to do? > > > > > > James Taylor wrote: > > > >> We should, but I don't think anything has been committed against the 4.x > >> branches that doesn't belong in the release. Maybe we should just delete > >> the 4.8 branches and recreate them once the RC is up? > >> > >> On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser > wrote: > >> > >> Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I > >>> just noticed that we have the same Maven versions on both the 4.8 and > 4.x > >>> branch sets. > >>> > >>> > >>> Ankit Singhal wrote: > >>> > >>> Following 4 branches have been created and are now available for > commits > >>>> targeted for 4.8.0 only. > >>>> > >>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98) > >>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0) > >>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1) > >>>> 4.8-HBase-1.2 (from master) > >>>> > >>>> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in > master > >>>> and > >>>> 4.x branches now. > >>>> > >>>> Regards, > >>>> Ankit Singhal > >>>> > >>>> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal< > ankitsinghal59@gmail.com > >>>> > > >>>> wrote: > >>>> > >>>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y > >>>> > >>>>> branches so that new features and bugs target for future > releases(4.9+) > >>>>> can > >>>>> be committed in 4.x branches and master. > >>>>> > >>>>> Whatever is targeted for 4.8.0 needs to be committed in all 8 > >>>>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8 > >>>>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y > >>>>> branches. > >>>>> > >>>>> I'll create the following new branches tomorrow morning IST, > >>>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98) > >>>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0) > >>>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1) > >>>>> 4.8-HBase-1.2 (from master) > >>>>> > >>>>> Let's discuss if someone has any concerns. > >>>>> > >>>>> Regards, > >>>>> Ankit Singhal > >>>>> > >>>>> On Sun, Jul 24, 2016 at 2:19 PM, wrote: > >>>>> > >>>>> Also, can we branch 4.8-x in git?That way bigger changes can still go > >>>>> > >>>>>> into the 4.x branches, while bugs are fixed in 4.8-x branches. > >>>>>> -- Lars > >>>>>> > >>>>>> From: James Taylor > >>>>>> To: "dev@phoenix.apache.org" > >>>>>> Sent: Thursday, July 21, 2016 7:16 PM > >>>>>> Subject: new 4.8.0 RC? > >>>>>> > >>>>>> How about a cutting a new RC now that the licensing work is > complete, > >>>>>> Ankit? Looks like we can simplify the voting too by just having a > >>>>>> single > >>>>>> vote across all versions by just include all the information in one > >>>>>> VOTE > >>>>>> thread. > >>>>>> > >>>>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a > few > >>>>>> other fixes come in which IMHO are all ok to include in the new RC. > >>>>>> > >>>>>> Thanks, > >>>>>> James > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >> > --001a113edaaebd38f2053926b6eb--