Return-Path: X-Original-To: apmail-giraph-dev-archive@www.apache.org Delivered-To: apmail-giraph-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 0A2A5DC21 for ; Sat, 27 Oct 2012 19:31:30 +0000 (UTC) Received: (qmail 27549 invoked by uid 500); 27 Oct 2012 19:31:29 -0000 Delivered-To: apmail-giraph-dev-archive@giraph.apache.org Received: (qmail 27499 invoked by uid 500); 27 Oct 2012 19:31:29 -0000 Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@giraph.apache.org Delivered-To: mailing list dev@giraph.apache.org Received: (qmail 27491 invoked by uid 99); 27 Oct 2012 19:31:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Oct 2012 19:31:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cdoronc@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Oct 2012 19:31:21 +0000 Received: by mail-ie0-f180.google.com with SMTP id e10so4907888iej.11 for ; Sat, 27 Oct 2012 12:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=l9RI3zRY8zghrd2hh7vNU8PIl70k4VMEFdJ769n6m5A=; b=vOkVUCC0USSgs1yohvjkXH69LFYqRi4OD1dBiz2P1Xo4cK6JH92/GKTW0oyr7hWwwu 2SXpjsmrKAxi2DyOwYZMVSYFtL/7RFpyreN0dw+fY9/WZDSInAd5Cx4wd/71wtY8CT/h oejLDHOS/thIqypbTgFNnTbxqMICm1ZzlYsoGWIJ9bg1yrqRZNQkZYubvzREakYUOic5 iNd1d3jKigzhiAUB8x4DuKTrropKU5CNmzWmZEZ8FZEglkjtfut7L2T8qLsIAZp+4b0X sqio1BYAlhWaNWqIBf3ztmie8vLHUcH1yvGflFiX6fQvvojVYHc4F6jH2unIhlnFxNNC MWKQ== MIME-Version: 1.0 Received: by 10.50.202.104 with SMTP id kh8mr5520700igc.21.1351366260484; Sat, 27 Oct 2012 12:31:00 -0700 (PDT) Received: by 10.50.129.99 with HTTP; Sat, 27 Oct 2012 12:31:00 -0700 (PDT) In-Reply-To: <508B2560.60802@apache.org> References: <508B2560.60802@apache.org> Date: Sat, 27 Oct 2012 21:31:00 +0200 Message-ID: Subject: Re: Giraph 0.2.0 From: Doron Cohen To: dev@giraph.apache.org Content-Type: multipart/alternative; boundary=f46d0447a27feaeac804cd0f7988 X-Virus-Checked: Checked by ClamAV on apache.org --f46d0447a27feaeac804cd0f7988 Content-Type: text/plain; charset=ISO-8859-1 Hi, any chance to include GIRAPH-42 (so sent-messages counter > 0)? Thanks, Doron On Sat, Oct 27, 2012 at 2:05 AM, Avery Ching wrote: > I agree with this. No showstoppers. The next version will have a ton of > improvements though. Would be really nice to have GIRAPH-388 in though as > it has a large performance impact. > > Avery > > > On 10/26/12 2:48 PM, Roman Shaposhnik wrote: > >> On Thu, Oct 25, 2012 at 9:22 PM, Eli Reisman >> wrote: >> >>> I can say from the list you have, GIRAPH-260 and GIRAPH-263 are not >>> blockers as far as I can see. Some of the other JIRA issues on the list >>> might be easily resolved one way or the other as well at this point. I >>> think both can safely be resolved at this point (260 can be a "won't >>> fix", >>> and 263 "fixed" as far as i can tell?) >>> >> Can we make a call on them one way or another? That would be helpful. >> Personally, I'm going to triage a couple of the ones I had in there: >> https://issues.apache.org/**jira/browse/GIRAPH-198 >> https://issues.apache.org/**jira/browse/GIRAPH-199 >> >> At this point it looks as though we don't really have any showstoppers >> for 0.2. At this point I'd like to proceed with a branch creation, RCs >> and testing via Bigtop and other means on my side of things. Will >> report accordingly. >> >> Thanks, >> Roman. >> > > --f46d0447a27feaeac804cd0f7988--