I would think so. We would need to update Giraph to be able to run on 2.0.4-alpha as well, that would need to happen first (but is pretty easy.) I think there are some IO and API components (edge input etc) that everyone is still working fast on and they might have a waypoint in mind before they ok a release. Other folks will need to jump in here and fill in details if this is the case.
I have seen a lot of funny breaks in the build the last few weeks, for myself I would like to see that stuff nice and stable before the release occurs. On Thu, Mar 28, 2013 at 2:25 PM, Roman Shaposhnik (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/GIRAPH-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616670#comment-13616670] > > Roman Shaposhnik commented on GIRAPH-285: > ----------------------------------------- > > Ping! Over at Bigtop we're currently working on stabilizing Hadoop > 2.0.4-alpha to make sure we've got a completely integrated release based on > that version of Hadoop. It would extremely nice if we could include Giraph > release as part of the Bigtop 0.6.0 distribution. > > Is there any chance of a 0.2.0 release within a couple of weeks or so? > > > 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 >
