Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9AD21101AC for ; Wed, 25 Feb 2015 01:24:28 +0000 (UTC) Received: (qmail 6584 invoked by uid 500); 25 Feb 2015 01:24:28 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 6540 invoked by uid 500); 25 Feb 2015 01:24:28 -0000 Mailing-List: contact user-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.apache.org Delivered-To: mailing list user@helix.apache.org Received: (qmail 6519 invoked by uid 99); 25 Feb 2015 01:24:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2015 01:24:28 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=491f55ad9=zzhang@linkedin.com designates 69.28.149.80 as permitted sender) Received: from [69.28.149.80] (HELO esv4-mav04.corp.linkedin.com) (69.28.149.80) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2015 01:24:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1424827464; x=1456363464; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=h11yN3KpjG8djckTykMrFNYzJ2DrZghtCZTw2yHcGR8=; b=n3K8K1/HDxtXGtTBJcCxlUQVGnoiQpJjUTzjep4LsLe3W7at867w+ID3 2uEgC1dvTJr6BAUclI24IZN9MWVNzn3PyPj6vcH+84jEIY6fA3fOHSzvb HO8vPZvBLthPOFUTIto1CRrIv72gX51xeKbI+IqWMv0M8e8nkkEdmdPYV w=; X-IronPort-AV: E=Sophos;i="5.09,642,1418112000"; d="scan'208,217";a="180401778" Received: from ESV4-MB02.linkedin.biz ([fe80::8093:3d15:3c8e:a479]) by esv4-cas02.linkedin.biz ([172.18.46.142]) with mapi id 14.03.0195.001; Tue, 24 Feb 2015 17:23:03 -0800 From: Zhen Zhang To: "user@helix.apache.org" , "dev@helix.apache.org" Subject: RE: 0.7.2 release Thread-Topic: 0.7.2 release Thread-Index: AQHQS8BN8tc48KbDz0SjOftpeDv00pz38OQAgAkbJID//30oaoAAlHgA//995Jc= Date: Wed, 25 Feb 2015 01:23:02 +0000 Message-ID: <23CA11DC8830BA44A37C6B44B14D013CB9D18ACC@ESV4-MB02.linkedin.biz> References: <23CA11DC8830BA44A37C6B44B14D013CB9D18A94@ESV4-MB02.linkedin.biz>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.46.251] Content-Type: multipart/alternative; boundary="_000_23CA11DC8830BA44A37C6B44B14D013CB9D18ACCESV4MB02linkedi_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_23CA11DC8830BA44A37C6B44B14D013CB9D18ACCESV4MB02linkedi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I can cherry pick all the fixes. ________________________________ From: kishore g [g.kishore@gmail.com] Sent: Tuesday, February 24, 2015 5:08 PM To: dev@helix.apache.org Cc: user@helix.apache.org Subject: Re: 0.7.2 release how do we know the things that we have pushed to 0.6.x but not to 0.7? On Tue, Feb 24, 2015 at 4:48 PM, Zhen Zhang > wrote: +1 As far as I can think of, here are a few things we need to complete before = releasing 0.7.2 - merge fixes that have been done on 0.6.x but haven't been ported to maste= r yet - fix 1 test failure - fix any other critical bugs we have in 0.7 - Jason ________________________________ From: Greg Brandt [brandt.greg@gmail.com] Sent: Tuesday, February 24, 2015 4:05 PM To: user@helix.apache.org Cc: dev@helix.apache.org Subject: Re: 0.7.2 release Bump. What needs to be done for this? -Greg On Feb 18, 2015 9:02 PM, "kishore g" >> wrote: +1 The recent bug we found is critical and would love to see that in the relea= se. Thanks Kishore G On Feb 18, 2015 1:17 PM, "Greg Brandt" = >> wrote: Hey guys, Would it be possible to get an 0.7.2 release? I have a use case that uses helix-ipc, for which there were a few critical patches after 0.7.1 release. Thanks, -Greg --_000_23CA11DC8830BA44A37C6B44B14D013CB9D18ACCESV4MB02linkedi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I can cherry pick all the fixes.

From: kishore g [g.kishore@gmail.com]
Sent: Tuesday, February 24, 2015 5:08 PM
To: dev@helix.apache.org
Cc: user@helix.apache.org
Subject: Re: 0.7.2 release

how do we know the things that we have pushed to 0.6.x but= not to 0.7?



On Tue, Feb 24, 2015 at 4:48 PM, Zhen Zhang <zzhang= @linkedin.com.invalid> wrote:
+1

As far as I can think of, here are a few things we need to complete before = releasing 0.7.2
- merge fixes that have been done on 0.6.x but haven't been ported to maste= r yet
- fix 1 test failure
- fix any other critical bugs we have in 0.7

- Jason

________________________________
From: Greg Brandt [brandt.greg@gmail.com]
Sent: Tuesday, February 24, 2015 4:05 PM
To: user@helix.a= pache.org
Cc: dev@helix.apa= che.org
Subject: Re: 0.7.2 release


Bump.

What needs to be done for this?

-Greg

On Feb 18, 2015 9:02 PM, "kishore g&q= uot; <g.kishore= @gmail.com<mailto:g.kishore@gmail.com>> wrote:

+1
The recent bug we found is critical and would love to see that in the relea= se.

Thanks
Kishore G
On Feb 18, 2015 1:17 PM, "Greg Brandt" <brandt.greg@gmail.co= m<mailto:= brandt.greg@gmail.com>> wrote:
Hey guys,

Would it be possible to get an 0.7.2 release?

I have a use case that uses helix-ipc, for which there were a few critical<= br> patches after 0.7.1 release.

Thanks,
-Greg

--_000_23CA11DC8830BA44A37C6B44B14D013CB9D18ACCESV4MB02linkedi_--