> We should keep the release-timing up and make our next release before 2012 > (IMO).
I think so. > And in general we should focus a bit more on algebraic computation, this > isn't possible with giraph and can be very helpful. Our goal is clear. IMO, we should focus on easy-to-use system in the short-term. On Wed, Aug 17, 2011 at 10:14 PM, Thomas Jungblut <[email protected]> wrote: > Okay so you going to focus on HAMA-410 Edward? > After that Whirr stuff I'll take care of HAMA-409, it would be great if > Miklos is going to help me a bit if he has time :) > We should keep the release-timing up and make our next release before 2012 > (IMO). > > And in general we should focus a bit more on algebraic computation, this > isn't possible with giraph and can be very helpful. > > 2011/8/17 Edward J. Yoon <[email protected]> > >> HAMA-410 must be fixed and tested before release 0.4.0. It's heavily >> related with other many next issues I think e.g., InputOutput system, >> Fault tolerant, ..., .etc. >> >> If that architecture is not good, we should re-implement it. >> >> Miklos, How's HAMA-409 going? >> >> On Tue, Aug 16, 2011 at 11:05 PM, Thomas Jungblut >> <[email protected]> wrote: >> > Hey guys, >> > >> > I guess we have to speak about what we want to do next and in which >> order. >> > And maybe what our goals are for the next monts. >> > >> > We have 3 larger tasks in the Pipe and their assignee: >> > - HAMA-410 Multiple Tasks per Groom (Edward) >> > - HAMA-409 Pregel API (Miklos, Edward, me) >> > - Fault Tolerance and various subtasks, e.G. HAMA-199 >> > >> > What are our plans for the next months and 0.4.0 release? >> > >> > I saw Edward already tweet about several project goals like "new 5+ >> > committers, 3+ PPMC members". >> > >> > Where do you see us in 3-4 months? >> > >> > Best regards, >> > Thomas >> > >> >> >> >> -- >> Best Regards, Edward J. Yoon >> @eddieyoon >> > > > > -- > Thomas Jungblut > Berlin > > mobile: 0170-3081070 > > business: [email protected] > private: [email protected] > -- Best Regards, Edward J. Yoon @eddieyoon
