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 8BA9BE635 for ; Thu, 28 Feb 2013 09:58:12 +0000 (UTC) Received: (qmail 94899 invoked by uid 500); 28 Feb 2013 09:58:12 -0000 Delivered-To: apmail-giraph-dev-archive@giraph.apache.org Received: (qmail 94686 invoked by uid 500); 28 Feb 2013 09:58:11 -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 94674 invoked by uid 99); 28 Feb 2013 09:58:11 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 09:58:11 +0000 Received: from localhost (HELO mail-oa0-f53.google.com) (127.0.0.1) (smtp-auth username gdfm, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 09:58:11 +0000 Received: by mail-oa0-f53.google.com with SMTP id m1so3225778oag.12 for ; Thu, 28 Feb 2013 01:58:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-originating-ip:in-reply-to:references :from:date:message-id:subject:to:content-type:x-gm-message-state; bh=L2tdRc0uCkP2s5XHngNrXgYUwrnpI0y+UP8RBC+IGKo=; b=gixBqX+cVrf3hqt2qcYqLPa3HStSKQmEA6qEzyXSAFVUXR4uHXnWD8VlonYYsWCE8X LbE77vfPe1R7Gxmd7W2PMC6S4XjZzx8AS91BUhDpjWu40PSrAkO7eGRlwxef6RbDei8w 911kz91/FvsSbyEjXHjddXGGNs+saGMqxjwLShxlOLqJU8CBuphn2l+dHfpgIWSRf4Sc 8po+w6qSwv/KIO3YoiXy/AGgk7Ur8AQjesO1XFHH5vSY6P7Fs1hmNcKhzcEjvIM5ouqo N2hhjcLL9/Hvjtv02Vsuo2MNmUGvwaCTTxF/jj2mrZWjORs1OuKZofCiyDbZFkHLZjhG wq6Q== X-Received: by 10.60.32.243 with SMTP id m19mr5259681oei.13.1362045490095; Thu, 28 Feb 2013 01:58:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.150.6 with HTTP; Thu, 28 Feb 2013 01:57:30 -0800 (PST) X-Originating-IP: [213.27.241.137] In-Reply-To: References: From: Gianmarco De Francisci Morales Date: Thu, 28 Feb 2013 10:57:30 +0100 Message-ID: Subject: Re: [jira] [Commented] (GIRAPH-285) Release Giraph-0.2 To: dev@giraph.apache.org Content-Type: multipart/alternative; boundary=e89a8fb1ebc49b065604d6c5ed83 X-Gm-Message-State: ALoCoQlVwxy+O/X6ZxBwGtIBx6ETsqYOKVHAUEF3w7hbxgtLyR7Kt6c0i0ySH7C5l/5oJTdwfPBA --e89a8fb1ebc49b065604d6c5ed83 Content-Type: text/plain; charset=ISO-8859-1 Personally, I don't think a half-baked and untested integration with YARN will do any good to a release. I would go for a stable release and fix the API. YARN is experimental anyway, so trunk seems the right place. Cheers, -- Gianmarco On Thu, Feb 28, 2013 at 3:09 AM, Eli Reisman wrote: > I'd really like to get the first stage of GIRAPH-13 into this release. I > think I will be done with that patch (and ready to expand on it in future > JIRAs that don't have to get into the release) in 1-2 weeks tops. Maybe a > lot less ;) > > > On Mon, Feb 25, 2013 at 10:57 AM, Jan van der Lugt >wrote: > > > That seems like a good call, a big refactor such as compatibility with > YARN > > will require a lot of testing and probably have a few follow-up JIRAs. > The > > last stable release was a year ago, getting a new version out there is > > important, in my opinion, for a few reasons: > > - will make the user mailing list calmer, since people won't use 0.1 > > anymore > > - will make academic comparisons easier, since articles can refer to 0.2 > > instead of a specific revision > > - will make the project seem more mature, fostering adaptation > > > > - Jan > > > > On Mon, Feb 25, 2013 at 6:42 PM, Claudio Martella (JIRA) < > jira@apache.org > > >wrote: > > > > > > > > [ > > > > > > https://issues.apache.org/jira/browse/GIRAPH-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586113#comment-13586113 > > ] > > > > > > Claudio Martella commented on GIRAPH-285: > > > ----------------------------------------- > > > > > > totally agree alessandro. > > > > > > I think the port to yarn can wait. i haven't seen anybody asking on the > > > ml, and it can easily go to trunk. refactor and api though is more > > > important for the current one. > > > > > > > Release Giraph-0.2 > > > > ------------------ > > > > > > > > Key: GIRAPH-285 > > > > URL: > https://issues.apache.org/jira/browse/GIRAPH-285 > > > > Project: Giraph > > > > Issue Type: Task > > > > Reporter: Avery Ching > > > > Assignee: Avery Ching > > > > > > > > I think it's time to do this. Trunk is moving fast and we need to > > > provide something for users that is fixed. Giraph has already > > progressed a > > > lot from 0.1. Jakob, can you please share your notes on releasing 0.1? > > > I'd really appreciate having them as a way to get started. > > > > > > -- > > > This message is automatically generated by JIRA. > > > If you think it was sent incorrectly, please contact your JIRA > > > administrators > > > For more information on JIRA, see: > > http://www.atlassian.com/software/jira > > > > > > --e89a8fb1ebc49b065604d6c5ed83--