You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon" <ed...@apache.org> on 2013/03/05 11:53:20 UTC
Re: 0.6.1 Release plan
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HAMA%20AND%20fixVersion%20%3D%20%220.6.1%22%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Do we still have an blocker issues? Otherwise, I'll test TRUNK and cut
0.6.1 release candidates.
On Mon, Feb 18, 2013 at 3:46 PM, Edward J. Yoon <ed...@apache.org> wrote:
> All,
>
> Once HAMA-704 and {HAMA-733 or HAMA-734} issues are done, I would like
> to release as a Hama 0.6.1.
>
> Since my projects/environments are all changed to HDFS 2.0 based, so I
> really difficult to evaluate current Hama.
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
--
Best Regards, Edward J. Yoon
@eddieyoon
Re: 0.6.1 Release plan
Posted by "Edward J. Yoon" <ed...@apache.org>.
In fact, the main reason why I want to release is that Hama 0.6.0
doesn't support computing scalability [1][2]. In my opinion, rest are
almost efficiency issues except only this issue.
If Spilling Queue and HDFS 2.0 compatibility issues can not solved
within few months, let's release 0.6.1.
1. http://mail-archives.apache.org/mod_mbox/hama-dev/201211.mbox/%3CCAGQgZQSandbbfyL6does=z8YG6jtyjZQvoCjDzN4sDrYivJyoQ@mail.gmail.com%3E
2. http://markmail.org/message/2yf4lkgdoreq37gn
On Wed, Mar 6, 2013 at 9:08 AM, Edward J. Yoon <ed...@apache.org> wrote:
>> are really looking for an immediate release, we would be wasting time on
>
> I see.
>
> On Wed, Mar 6, 2013 at 8:08 AM, Suraj Menon <su...@apache.org> wrote:
>> Edward, we are on crossroads on lot of features. Sorted Queues have made
>> the complete refactor of messaging code a necessity. Hence I am working on
>> getting 2 pieces of puzzle together. Thus there are two ways of looking
>> into it. Maybe this is the best time to test the code and release before we
>> the next set of major changes. However, unless we have a set of users who
>> are really looking for an immediate release, we would be wasting time on
>> slicing a release. Also, have we got feedback from MRQL on how the current
>> partitioning strategy affects it?
>>
>> On Tue, Mar 5, 2013 at 5:53 AM, Edward J. Yoon <ed...@apache.org>wrote:
>>
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HAMA%20AND%20fixVersion%20%3D%20%220.6.1%22%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
>>>
>>> Do we still have an blocker issues? Otherwise, I'll test TRUNK and cut
>>> 0.6.1 release candidates.
>>>
>>> On Mon, Feb 18, 2013 at 3:46 PM, Edward J. Yoon <ed...@apache.org>
>>> wrote:
>>> > All,
>>> >
>>> > Once HAMA-704 and {HAMA-733 or HAMA-734} issues are done, I would like
>>> > to release as a Hama 0.6.1.
>>> >
>>> > Since my projects/environments are all changed to HDFS 2.0 based, so I
>>> > really difficult to evaluate current Hama.
>>> >
>>> > --
>>> > Best Regards, Edward J. Yoon
>>> > @eddieyoon
>>>
>>>
>>>
>>> --
>>> Best Regards, Edward J. Yoon
>>> @eddieyoon
>>>
>
>
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
--
Best Regards, Edward J. Yoon
@eddieyoon
Re: 0.6.1 Release plan
Posted by "Edward J. Yoon" <ed...@apache.org>.
> are really looking for an immediate release, we would be wasting time on
I see.
On Wed, Mar 6, 2013 at 8:08 AM, Suraj Menon <su...@apache.org> wrote:
> Edward, we are on crossroads on lot of features. Sorted Queues have made
> the complete refactor of messaging code a necessity. Hence I am working on
> getting 2 pieces of puzzle together. Thus there are two ways of looking
> into it. Maybe this is the best time to test the code and release before we
> the next set of major changes. However, unless we have a set of users who
> are really looking for an immediate release, we would be wasting time on
> slicing a release. Also, have we got feedback from MRQL on how the current
> partitioning strategy affects it?
>
> On Tue, Mar 5, 2013 at 5:53 AM, Edward J. Yoon <ed...@apache.org>wrote:
>
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HAMA%20AND%20fixVersion%20%3D%20%220.6.1%22%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
>>
>> Do we still have an blocker issues? Otherwise, I'll test TRUNK and cut
>> 0.6.1 release candidates.
>>
>> On Mon, Feb 18, 2013 at 3:46 PM, Edward J. Yoon <ed...@apache.org>
>> wrote:
>> > All,
>> >
>> > Once HAMA-704 and {HAMA-733 or HAMA-734} issues are done, I would like
>> > to release as a Hama 0.6.1.
>> >
>> > Since my projects/environments are all changed to HDFS 2.0 based, so I
>> > really difficult to evaluate current Hama.
>> >
>> > --
>> > Best Regards, Edward J. Yoon
>> > @eddieyoon
>>
>>
>>
>> --
>> Best Regards, Edward J. Yoon
>> @eddieyoon
>>
--
Best Regards, Edward J. Yoon
@eddieyoon
Re: 0.6.1 Release plan
Posted by Suraj Menon <su...@apache.org>.
Edward, we are on crossroads on lot of features. Sorted Queues have made
the complete refactor of messaging code a necessity. Hence I am working on
getting 2 pieces of puzzle together. Thus there are two ways of looking
into it. Maybe this is the best time to test the code and release before we
the next set of major changes. However, unless we have a set of users who
are really looking for an immediate release, we would be wasting time on
slicing a release. Also, have we got feedback from MRQL on how the current
partitioning strategy affects it?
On Tue, Mar 5, 2013 at 5:53 AM, Edward J. Yoon <ed...@apache.org>wrote:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HAMA%20AND%20fixVersion%20%3D%20%220.6.1%22%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
>
> Do we still have an blocker issues? Otherwise, I'll test TRUNK and cut
> 0.6.1 release candidates.
>
> On Mon, Feb 18, 2013 at 3:46 PM, Edward J. Yoon <ed...@apache.org>
> wrote:
> > All,
> >
> > Once HAMA-704 and {HAMA-733 or HAMA-734} issues are done, I would like
> > to release as a Hama 0.6.1.
> >
> > Since my projects/environments are all changed to HDFS 2.0 based, so I
> > really difficult to evaluate current Hama.
> >
> > --
> > Best Regards, Edward J. Yoon
> > @eddieyoon
>
>
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
>