You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Sean Owen <sr...@gmail.com> on 2011/05/06 16:25:29 UTC
[VOTE] Code freeze for 0.5 release May 20
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
pretty good time for 0.5.
I suggest we enter a code freeze upon passing of this vote. The only
changes will be fixes, more tests, doc improvements. I'll act as
release engineer then to head up the release (with helping hands along
the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
targeting a release on May 20.
What say?
Sean
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Dmitriy Lyubimov <dl...@gmail.com>.
+1
On Fri, May 6, 2011 at 7:25 AM, Sean Owen <sr...@gmail.com> wrote:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>
> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
> pretty good time for 0.5.
>
> I suggest we enter a code freeze upon passing of this vote. The only
> changes will be fixes, more tests, doc improvements. I'll act as
> release engineer then to head up the release (with helping hands along
> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
> targeting a release on May 20.
>
> What say?
>
> Sean
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sebastian Schelter <ss...@apache.org>.
+1
On 06.05.2011 16:25, Sean Owen wrote:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>
> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
> pretty good time for 0.5.
>
> I suggest we enter a code freeze upon passing of this vote. The only
> changes will be fixes, more tests, doc improvements. I'll act as
> release engineer then to head up the release (with helping hands along
> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
> targeting a release on May 20.
>
> What say?
>
> Sean
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Grant Ingersoll <gs...@apache.org>.
+1.
On May 6, 2011, at 10:25 AM, Sean Owen wrote:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>
> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
> pretty good time for 0.5.
>
> I suggest we enter a code freeze upon passing of this vote. The only
> changes will be fixes, more tests, doc improvements. I'll act as
> release engineer then to head up the release (with helping hands along
> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
> targeting a release on May 20.
>
> What say?
>
> Sean
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Jake Mannix <ja...@gmail.com>.
finally committed after re-running all tests and build-reuters.sh on
freshly
applied manually created patch.
I've got nothing holding up code freeze now.
-jake
On Fri, May 6, 2011 at 12:28 PM, Jake Mannix <ja...@gmail.com> wrote:
> tests pass, running build-reuters.sh to make sure that this still works,
> and
> produces LDA document/topic vectors, then to commit.
>
> -jake
>
>
> On Fri, May 6, 2011 at 11:52 AM, Jake Mannix <ja...@gmail.com>wrote:
>
>> +1 for EOD (UTC - coming on quick!), with the caveat that my patch for
>> MAHOUT-682 is actually cleaned up and done, and I'm running unit tests
>> and the reuters example now to verify that it really really really is
>> good,
>> then I'm committing it (it's essentially the patch which is currently
>> attached to that JIRA, if anyone cares to look it over).
>>
>> -jake
>>
>>
>> On Fri, May 6, 2011 at 11:41 AM, Sean Owen <sr...@gmail.com> wrote:
>>
>>> (All committers.)
>>>
>>> On Fri, May 6, 2011 at 7:39 PM, Shannon Quinn <sq...@gatech.edu> wrote:
>>> > (not sure if this is PMC only or all Mahout committers :) )
>>>
>>
>>
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Jake Mannix <ja...@gmail.com>.
tests pass, running build-reuters.sh to make sure that this still works,
and
produces LDA document/topic vectors, then to commit.
-jake
On Fri, May 6, 2011 at 11:52 AM, Jake Mannix <ja...@gmail.com> wrote:
> +1 for EOD (UTC - coming on quick!), with the caveat that my patch for
> MAHOUT-682 is actually cleaned up and done, and I'm running unit tests
> and the reuters example now to verify that it really really really is
> good,
> then I'm committing it (it's essentially the patch which is currently
> attached to that JIRA, if anyone cares to look it over).
>
> -jake
>
>
> On Fri, May 6, 2011 at 11:41 AM, Sean Owen <sr...@gmail.com> wrote:
>
>> (All committers.)
>>
>> On Fri, May 6, 2011 at 7:39 PM, Shannon Quinn <sq...@gatech.edu> wrote:
>> > (not sure if this is PMC only or all Mahout committers :) )
>>
>
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Jake Mannix <ja...@gmail.com>.
+1 for EOD (UTC - coming on quick!), with the caveat that my patch for
MAHOUT-682 is actually cleaned up and done, and I'm running unit tests
and the reuters example now to verify that it really really really is good,
then I'm committing it (it's essentially the patch which is currently
attached to that JIRA, if anyone cares to look it over).
-jake
On Fri, May 6, 2011 at 11:41 AM, Sean Owen <sr...@gmail.com> wrote:
> (All committers.)
>
> On Fri, May 6, 2011 at 7:39 PM, Shannon Quinn <sq...@gatech.edu> wrote:
> > (not sure if this is PMC only or all Mahout committers :) )
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sean Owen <sr...@gmail.com>.
(All committers.)
On Fri, May 6, 2011 at 7:39 PM, Shannon Quinn <sq...@gatech.edu> wrote:
> (not sure if this is PMC only or all Mahout committers :) )
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Shannon Quinn <sq...@gatech.edu>.
+1
(not sure if this is PMC only or all Mahout committers :) )
On 5/6/2011 11:17 AM, Jeff Eastman wrote:
> +1
>
> -----Original Message-----
> From: Sean Owen [mailto:srowen@gmail.com]
> Sent: Friday, May 06, 2011 7:25 AM
> To: Mahout Dev List
> Subject: [VOTE] Code freeze for 0.5 release May 20
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>
> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
> pretty good time for 0.5.
>
> I suggest we enter a code freeze upon passing of this vote. The only
> changes will be fixes, more tests, doc improvements. I'll act as
> release engineer then to head up the release (with helping hands along
> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
> targeting a release on May 20.
>
> What say?
>
> Sean
RE: [VOTE] Code freeze for 0.5 release May 20
Posted by Jeff Eastman <je...@Narus.com>.
+1
-----Original Message-----
From: Sean Owen [mailto:srowen@gmail.com]
Sent: Friday, May 06, 2011 7:25 AM
To: Mahout Dev List
Subject: [VOTE] Code freeze for 0.5 release May 20
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
pretty good time for 0.5.
I suggest we enter a code freeze upon passing of this vote. The only
changes will be fixes, more tests, doc improvements. I'll act as
release engineer then to head up the release (with helping hands along
the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
targeting a release on May 20.
What say?
Sean
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sean Owen <sr...@gmail.com>.
I have now pushed our release candidate:
https://repository.apache.org/content/repositories/orgapachemahout-024/
Have a look. I'll call a vote soon.
On Tue, May 17, 2011 at 3:28 PM, Benson Margulies <bi...@gmail.com>wrote:
> I dropped the previous 'rc' from the Apache nexus.
>
> On Tue, May 17, 2011 at 10:17 AM, Sean Owen <sr...@gmail.com> wrote:
> > I had meant to start releasing as of the 20th for a release next week,
> > but, why don't I go ahead and do a dry run and call a vote? If anybody
> > objects, we'll not pass the vote, but otherwise we just go ahead.
> >
> > On Tue, May 17, 2011 at 3:16 PM, Grant Ingersoll <gs...@apache.org>
> wrote:
> >>
> >> On May 15, 2011, at 3:51 PM, Sean Owen wrote:
> >>
> >>> With any luck the same release process works; Benson's tried most of
> >>> it recently. I suppose you can do a dry run if you're bored to test
> >>> the wiki documentation. But I imagine even better would be to try a
> >>> few examples and double-check the bits not covered by unit tests work.
> >>>
> >>> All in all not expecting much hassle at the end of the week for the
> release.
> >>
> >> Is your intent then to put up RCs for us to view/vote today so we can
> release on the 20th?
> >>
> >>
> >
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Benson Margulies <bi...@gmail.com>.
I dropped the previous 'rc' from the Apache nexus.
On Tue, May 17, 2011 at 10:17 AM, Sean Owen <sr...@gmail.com> wrote:
> I had meant to start releasing as of the 20th for a release next week,
> but, why don't I go ahead and do a dry run and call a vote? If anybody
> objects, we'll not pass the vote, but otherwise we just go ahead.
>
> On Tue, May 17, 2011 at 3:16 PM, Grant Ingersoll <gs...@apache.org> wrote:
>>
>> On May 15, 2011, at 3:51 PM, Sean Owen wrote:
>>
>>> With any luck the same release process works; Benson's tried most of
>>> it recently. I suppose you can do a dry run if you're bored to test
>>> the wiki documentation. But I imagine even better would be to try a
>>> few examples and double-check the bits not covered by unit tests work.
>>>
>>> All in all not expecting much hassle at the end of the week for the release.
>>
>> Is your intent then to put up RCs for us to view/vote today so we can release on the 20th?
>>
>>
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sean Owen <sr...@gmail.com>.
I had meant to start releasing as of the 20th for a release next week,
but, why don't I go ahead and do a dry run and call a vote? If anybody
objects, we'll not pass the vote, but otherwise we just go ahead.
On Tue, May 17, 2011 at 3:16 PM, Grant Ingersoll <gs...@apache.org> wrote:
>
> On May 15, 2011, at 3:51 PM, Sean Owen wrote:
>
>> With any luck the same release process works; Benson's tried most of
>> it recently. I suppose you can do a dry run if you're bored to test
>> the wiki documentation. But I imagine even better would be to try a
>> few examples and double-check the bits not covered by unit tests work.
>>
>> All in all not expecting much hassle at the end of the week for the release.
>
> Is your intent then to put up RCs for us to view/vote today so we can release on the 20th?
>
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Grant Ingersoll <gs...@apache.org>.
On May 15, 2011, at 3:51 PM, Sean Owen wrote:
> With any luck the same release process works; Benson's tried most of
> it recently. I suppose you can do a dry run if you're bored to test
> the wiki documentation. But I imagine even better would be to try a
> few examples and double-check the bits not covered by unit tests work.
>
> All in all not expecting much hassle at the end of the week for the release.
Is your intent then to put up RCs for us to view/vote today so we can release on the 20th?
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sean Owen <sr...@gmail.com>.
With any luck the same release process works; Benson's tried most of
it recently. I suppose you can do a dry run if you're bored to test
the wiki documentation. But I imagine even better would be to try a
few examples and double-check the bits not covered by unit tests work.
All in all not expecting much hassle at the end of the week for the release.
On Sun, May 15, 2011 at 8:07 PM, Grant Ingersoll <gs...@apache.org> wrote:
> Sean,
>
> Anything I can do to help prep. an RC?
>
> -Grant
>
> On May 9, 2011, at 2:13 PM, Sebastian Schelter wrote:
>
>> There is an implementation of an algorithm called ALS-WR which was developed for the Netflix-Prize. It contains a parallelized matrix factorization, but the algorithm itself is iterative which is not a good fit for the MapReduce paradigm, so this implementation should be considered experimental at best currently.
>>
>> --sebastian
>>
>>
>> On 09.05.2011 19:26, Sean Owen wrote
>>> What you see in trunk now is basically what you'll get.
>>> I know Sebastian has done a lot of work on this piece since 0.4, yes,
>>> so I imagine the answer is 'yes' it's new and different and perhaps
>>> better for your purpose.
>>>
>>> On Mon, May 9, 2011 at 6:03 PM, James James<re...@yahoo.com> wrote:
>>>> Hi,
>>>>
>>>> I was wondering if the new release 0.5 will include the new implementation of a
>>>> SVD-based recommender? I know there exists an old implementation in Mahout, but
>>>> it does not really scalable.
>>>>
>>>> Thanks,
>>>>
>>>> James
>>>>
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> From: Sean Owen<sr...@gmail.com>
>>>> To: Mahout Dev List<de...@mahout.apache.org>
>>>> Sent: Mon, May 9, 2011 4:30:34 AM
>>>> Subject: Re: [VOTE] Code freeze for 0.5 release May 20
>>>>
>>>> OK, hearing no objections in a few hours, this will have passed. If
>>>> so, only fixes related to 0.5, or test/doc/checkstyle improvements,
>>>> from here to release.
>>>>
>>>> On Fri, May 6, 2011 at 3:25 PM, Sean Owen<sr...@gmail.com> wrote:
>>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>>>>> e
>>>>>
>>>>> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
>>>>> pretty good time for 0.5.
>>>>>
>>>>> I suggest we enter a code freeze upon passing of this vote. The only
>>>>> changes will be fixes, more tests, doc improvements. I'll act as
>>>>> release engineer then to head up the release (with helping hands along
>>>>> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>>> targeting a release on May 20.
>>>>>
>>>>> What say?
>>>>>
>>>>> Sean
>>>>>
>>>>
>>
>
> --------------------------
> Grant Ingersoll
> Lucene Revolution -- Lucene and Solr User Conference
> May 25-26 in San Francisco
> www.lucenerevolution.org
>
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Grant Ingersoll <gs...@apache.org>.
Sean,
Anything I can do to help prep. an RC?
-Grant
On May 9, 2011, at 2:13 PM, Sebastian Schelter wrote:
> There is an implementation of an algorithm called ALS-WR which was developed for the Netflix-Prize. It contains a parallelized matrix factorization, but the algorithm itself is iterative which is not a good fit for the MapReduce paradigm, so this implementation should be considered experimental at best currently.
>
> --sebastian
>
>
> On 09.05.2011 19:26, Sean Owen wrote
>> What you see in trunk now is basically what you'll get.
>> I know Sebastian has done a lot of work on this piece since 0.4, yes,
>> so I imagine the answer is 'yes' it's new and different and perhaps
>> better for your purpose.
>>
>> On Mon, May 9, 2011 at 6:03 PM, James James<re...@yahoo.com> wrote:
>>> Hi,
>>>
>>> I was wondering if the new release 0.5 will include the new implementation of a
>>> SVD-based recommender? I know there exists an old implementation in Mahout, but
>>> it does not really scalable.
>>>
>>> Thanks,
>>>
>>> James
>>>
>>>
>>>
>>>
>>> ________________________________
>>> From: Sean Owen<sr...@gmail.com>
>>> To: Mahout Dev List<de...@mahout.apache.org>
>>> Sent: Mon, May 9, 2011 4:30:34 AM
>>> Subject: Re: [VOTE] Code freeze for 0.5 release May 20
>>>
>>> OK, hearing no objections in a few hours, this will have passed. If
>>> so, only fixes related to 0.5, or test/doc/checkstyle improvements,
>>> from here to release.
>>>
>>> On Fri, May 6, 2011 at 3:25 PM, Sean Owen<sr...@gmail.com> wrote:
>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>>>> e
>>>>
>>>> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
>>>> pretty good time for 0.5.
>>>>
>>>> I suggest we enter a code freeze upon passing of this vote. The only
>>>> changes will be fixes, more tests, doc improvements. I'll act as
>>>> release engineer then to head up the release (with helping hands along
>>>> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>> targeting a release on May 20.
>>>>
>>>> What say?
>>>>
>>>> Sean
>>>>
>>>
>
--------------------------
Grant Ingersoll
Lucene Revolution -- Lucene and Solr User Conference
May 25-26 in San Francisco
www.lucenerevolution.org
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sebastian Schelter <ss...@apache.org>.
There is an implementation of an algorithm called ALS-WR which was
developed for the Netflix-Prize. It contains a parallelized matrix
factorization, but the algorithm itself is iterative which is not a good
fit for the MapReduce paradigm, so this implementation should be
considered experimental at best currently.
--sebastian
On 09.05.2011 19:26, Sean Owen wrote
> What you see in trunk now is basically what you'll get.
> I know Sebastian has done a lot of work on this piece since 0.4, yes,
> so I imagine the answer is 'yes' it's new and different and perhaps
> better for your purpose.
>
> On Mon, May 9, 2011 at 6:03 PM, James James<re...@yahoo.com> wrote:
>> Hi,
>>
>> I was wondering if the new release 0.5 will include the new implementation of a
>> SVD-based recommender? I know there exists an old implementation in Mahout, but
>> it does not really scalable.
>>
>> Thanks,
>>
>> James
>>
>>
>>
>>
>> ________________________________
>> From: Sean Owen<sr...@gmail.com>
>> To: Mahout Dev List<de...@mahout.apache.org>
>> Sent: Mon, May 9, 2011 4:30:34 AM
>> Subject: Re: [VOTE] Code freeze for 0.5 release May 20
>>
>> OK, hearing no objections in a few hours, this will have passed. If
>> so, only fixes related to 0.5, or test/doc/checkstyle improvements,
>> from here to release.
>>
>> On Fri, May 6, 2011 at 3:25 PM, Sean Owen<sr...@gmail.com> wrote:
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>>> e
>>>
>>> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
>>> pretty good time for 0.5.
>>>
>>> I suggest we enter a code freeze upon passing of this vote. The only
>>> changes will be fixes, more tests, doc improvements. I'll act as
>>> release engineer then to head up the release (with helping hands along
>>> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
>>> targeting a release on May 20.
>>>
>>> What say?
>>>
>>> Sean
>>>
>>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sean Owen <sr...@gmail.com>.
What you see in trunk now is basically what you'll get.
I know Sebastian has done a lot of work on this piece since 0.4, yes,
so I imagine the answer is 'yes' it's new and different and perhaps
better for your purpose.
On Mon, May 9, 2011 at 6:03 PM, James James <re...@yahoo.com> wrote:
> Hi,
>
> I was wondering if the new release 0.5 will include the new implementation of a
> SVD-based recommender? I know there exists an old implementation in Mahout, but
> it does not really scalable.
>
> Thanks,
>
> James
>
>
>
>
> ________________________________
> From: Sean Owen <sr...@gmail.com>
> To: Mahout Dev List <de...@mahout.apache.org>
> Sent: Mon, May 9, 2011 4:30:34 AM
> Subject: Re: [VOTE] Code freeze for 0.5 release May 20
>
> OK, hearing no objections in a few hours, this will have passed. If
> so, only fixes related to 0.5, or test/doc/checkstyle improvements,
> from here to release.
>
> On Fri, May 6, 2011 at 3:25 PM, Sean Owen <sr...@gmail.com> wrote:
>>https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>>e
>>
>> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
>> pretty good time for 0.5.
>>
>> I suggest we enter a code freeze upon passing of this vote. The only
>> changes will be fixes, more tests, doc improvements. I'll act as
>> release engineer then to head up the release (with helping hands along
>> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
>> targeting a release on May 20.
>>
>> What say?
>>
>> Sean
>>
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by James James <re...@yahoo.com>.
Hi,
I was wondering if the new release 0.5 will include the new implementation of a
SVD-based recommender? I know there exists an old implementation in Mahout, but
it does not really scalable.
Thanks,
James
________________________________
From: Sean Owen <sr...@gmail.com>
To: Mahout Dev List <de...@mahout.apache.org>
Sent: Mon, May 9, 2011 4:30:34 AM
Subject: Re: [VOTE] Code freeze for 0.5 release May 20
OK, hearing no objections in a few hours, this will have passed. If
so, only fixes related to 0.5, or test/doc/checkstyle improvements,
from here to release.
On Fri, May 6, 2011 at 3:25 PM, Sean Owen <sr...@gmail.com> wrote:
>https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>e
>
> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
> pretty good time for 0.5.
>
> I suggest we enter a code freeze upon passing of this vote. The only
> changes will be fixes, more tests, doc improvements. I'll act as
> release engineer then to head up the release (with helping hands along
> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
> targeting a release on May 20.
>
> What say?
>
> Sean
>
Re: [VOTE] Code freeze for 0.5 release May 20
Posted by Sean Owen <sr...@gmail.com>.
OK, hearing no objections in a few hours, this will have passed. If
so, only fixes related to 0.5, or test/doc/checkstyle improvements,
from here to release.
On Fri, May 6, 2011 at 3:25 PM, Sean Owen <sr...@gmail.com> wrote:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MAHOUT+AND+fixVersion+%3D+%220.5%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>
> 127 issues resolved for 0.5, and 6 months since 0.4 was released. Yep,
> pretty good time for 0.5.
>
> I suggest we enter a code freeze upon passing of this vote. The only
> changes will be fixes, more tests, doc improvements. I'll act as
> release engineer then to head up the release (with helping hands along
> the way) per https://cwiki.apache.org/MAHOUT/how-to-release.html
> targeting a release on May 20.
>
> What say?
>
> Sean
>