giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eli Reisman <>
Subject Re: [jira] [Commented] (GIRAPH-285) Release Giraph-0.2
Date Wed, 20 Feb 2013 23:29:24 GMT
I'm +1 on this happening soon.

>From my own perspective, I think the basic YARN implementation will be done
soon, and there will be a bunch of little sub-JIRAs to flesh it out. It
would be fun to get a few more of those in. I also see there is a lot of
potentially API-affecting stuff happening around the vertex and edge
inputs, and the "vertex as an interface" work. Also, there may still be a
couple residual concurrency issues floating around from our recent move to
threaded compute tasks. It would be interesting to hear how folks are
feeling about the stability of that stuff. Or other things that really
should be completed before a release that I have not been following?

Given all this, I feel like a release within a month or 6 weeks would not
be crazy? Longer would not bother me, but I agree its time, we've been
talking about it since last fall. ;)

On Wed, Feb 20, 2013 at 10:39 AM, Pradeep Gollakota (JIRA)

>     [
> Pradeep Gollakota commented on GIRAPH-285:
> ------------------------------------------
> Any progress on this guys? The 0.2 version of Giraph is MUCH better to
> work with and it would be great to have a stable released version of this
> soon (especially considering 0.1 was released last February).
> > Release Giraph-0.2
> > ------------------
> >
> >                 Key: GIRAPH-285
> >                 URL:
> >             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:

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