giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianmarco De Francisci Morales <g...@apache.org>
Subject Re: [jira] [Commented] (GIRAPH-285) Release Giraph-0.2
Date Thu, 28 Feb 2013 09:57:30 GMT
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 <apache.mailbox@gmail.com>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 <janlugt@gmail.com
> >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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message