Given that Jenkins now seems relatively stable and there are no
outstanding JIRA issues targeted for 0.6 I'd like to call the question.

Jeff

+1

On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
<[EMAIL PROTECTED]> wrote:
> Given that Jenkins now seems relatively stable and there are no outstanding
> JIRA issues targeted for 0.6 I'd like to call the question.
>
> Jeff

I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
0.6, but I should be able to do this until Tuesday, is this ok?

--sebastian

On 20.01.2012 09:43, Sean Owen wrote:
> +1
>
> On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
> <[EMAIL PROTECTED]> wrote:
>> Given that Jenkins now seems relatively stable and there are no outstanding
>> JIRA issues targeted for 0.6 I'd like to call the question.
>>
>> Jeff

Until we have a freeze, I think it is fine.

On Fri, Jan 20, 2012 at 2:31 AM, Sebastian Schelter <[EMAIL PROTECTED]> wrote:

> I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
> 0.6, but I should be able to do this until Tuesday, is this ok?
>
> --sebastian
>
> On 20.01.2012 09:43, Sean Owen wrote:
> > +1
> >
> > On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
> > <[EMAIL PROTECTED]> wrote:
> >> Given that Jenkins now seems relatively stable and there are no
> outstanding
> >> JIRA issues targeted for 0.6 I'd like to call the question.
> >>
> >> Jeff
>
>

+1

On Fri, Jan 20, 2012 at 8:04 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
> Until we have a freeze, I think it is fine.
>
> On Fri, Jan 20, 2012 at 2:31 AM, Sebastian Schelter <[EMAIL PROTECTED]> wrote:
>
>> I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
>> 0.6, but I should be able to do this until Tuesday, is this ok?
>>
>> --sebastian
>>
>> On 20.01.2012 09:43, Sean Owen wrote:
>> > +1
>> >
>> > On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
>> > <[EMAIL PROTECTED]> wrote:
>> >> Given that Jenkins now seems relatively stable and there are no
>> outstanding
>> >> JIRA issues targeted for 0.6 I'd like to call the question.
>> >>
>> >> Jeff
>>
>>

+1

On Fri, Jan 20, 2012 at 10:54 AM, Dmitriy Lyubimov <[EMAIL PROTECTED]>wrote:

> +1
>
> On Fri, Jan 20, 2012 at 8:04 AM, Ted Dunning <[EMAIL PROTECTED]>
> wrote:
> > Until we have a freeze, I think it is fine.
> >
> > On Fri, Jan 20, 2012 at 2:31 AM, Sebastian Schelter <[EMAIL PROTECTED]>
> wrote:
> >
> >> I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
> >> 0.6, but I should be able to do this until Tuesday, is this ok?
> >>
> >> --sebastian
> >>
> >> On 20.01.2012 09:43, Sean Owen wrote:
> >> > +1
> >> >
> >> > On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
> >> > <[EMAIL PROTECTED]> wrote:
> >> >> Given that Jenkins now seems relatively stable and there are no
> >> outstanding
> >> >> JIRA issues targeted for 0.6 I'd like to call the question.
> >> >>
> >> >> Jeff
> >>
> >>
>

+1 It's going to take a few days to complete the vote and administration
anyway. But time is of the essence as we are 20 days after our first
target already.
On 1/20/12 1:55 PM, Ted Dunning wrote:
> +1
>
> On Fri, Jan 20, 2012 at 10:54 AM, Dmitriy Lyubimov<[EMAIL PROTECTED]>wrote:
>
>> +1
>>
>> On Fri, Jan 20, 2012 at 8:04 AM, Ted Dunning<[EMAIL PROTECTED]>
>> wrote:
>>> Until we have a freeze, I think it is fine.
>>>
>>> On Fri, Jan 20, 2012 at 2:31 AM, Sebastian Schelter<[EMAIL PROTECTED]>
>> wrote:
>>>> I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
>>>> 0.6, but I should be able to do this until Tuesday, is this ok?
>>>>
>>>> --sebastian
>>>>
>>>> On 20.01.2012 09:43, Sean Owen wrote:
>>>>> +1
>>>>>
>>>>> On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
>>>>> <[EMAIL PROTECTED]>  wrote:
>>>>>> Given that Jenkins now seems relatively stable and there are no
>>>> outstanding
>>>>>> JIRA issues targeted for 0.6 I'd like to call the question.
>>>>>>
>>>>>> Jeff
>>>>

+1.

On Jan 20, 2012, at 2:09 PM, Jeff Eastman wrote:

> +1 It's going to take a few days to complete the vote and administration anyway. But time is of the essence as we are 20 days after our first target already.
>
>
> On 1/20/12 1:55 PM, Ted Dunning wrote:
>> +1
>>
>> On Fri, Jan 20, 2012 at 10:54 AM, Dmitriy Lyubimov<[EMAIL PROTECTED]>wrote:
>>
>>> +1
>>>
>>> On Fri, Jan 20, 2012 at 8:04 AM, Ted Dunning<[EMAIL PROTECTED]>
>>> wrote:
>>>> Until we have a freeze, I think it is fine.
>>>>
>>>> On Fri, Jan 20, 2012 at 2:31 AM, Sebastian Schelter<[EMAIL PROTECTED]>
>>> wrote:
>>>>> I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
>>>>> 0.6, but I should be able to do this until Tuesday, is this ok?
>>>>>
>>>>> --sebastian
>>>>>
>>>>> On 20.01.2012 09:43, Sean Owen wrote:
>>>>>> +1
>>>>>>
>>>>>> On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
>>>>>> <[EMAIL PROTECTED]>  wrote:
>>>>>>> Given that Jenkins now seems relatively stable and there are no
>>>>> outstanding
>>>>>>> JIRA issues targeted for 0.6 I'd like to call the question.
>>>>>>>
>>>>>>> Jeff
>>>>>
>

--------------------------------------------
Grant Ingersoll
http://www.lucidimagination.com

https://issues.apache.org/jira/browse/MAHOUT-939

examples/bin/asf-mail-examples.sh does not work. Classification->Bayes
(select 3, then select 1) fails because it has bad directory names.

File 'bayes.patch' in the above issue fixes this problem by imitating
the Clasification->SGD section. I added it to this issue because
previous commits from this issue broke the scripts. I can make a
separate JIRA if you like.

I would propose running through the example scripts, with and without
a hadoop farm.
On Fri, Jan 20, 2012 at 4:02 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> +1.
>
> On Jan 20, 2012, at 2:09 PM, Jeff Eastman wrote:
>
>> +1 It's going to take a few days to complete the vote and administration anyway. But time is of the essence as we are 20 days after our first target already.
>>
>>
>> On 1/20/12 1:55 PM, Ted Dunning wrote:
>>> +1
>>>
>>> On Fri, Jan 20, 2012 at 10:54 AM, Dmitriy Lyubimov<[EMAIL PROTECTED]>wrote:
>>>
>>>> +1
>>>>
>>>> On Fri, Jan 20, 2012 at 8:04 AM, Ted Dunning<[EMAIL PROTECTED]>
>>>> wrote:
>>>>> Until we have a freeze, I think it is fine.
>>>>>
>>>>> On Fri, Jan 20, 2012 at 2:31 AM, Sebastian Schelter<[EMAIL PROTECTED]>
>>>> wrote:
>>>>>> I'd like to commit https://issues.apache.org/jira/browse/MAHOUT-737 for
>>>>>> 0.6, but I should be able to do this until Tuesday, is this ok?
>>>>>>
>>>>>> --sebastian
>>>>>>
>>>>>> On 20.01.2012 09:43, Sean Owen wrote:
>>>>>>> +1
>>>>>>>
>>>>>>> On Fri, Jan 20, 2012 at 8:24 AM, Jeff Eastman
>>>>>>> <[EMAIL PROTECTED]>  wrote:
>>>>>>>> Given that Jenkins now seems relatively stable and there are no
>>>>>> outstanding
>>>>>>>> JIRA issues targeted for 0.6 I'd like to call the question.
>>>>>>>>
>>>>>>>> Jeff
>>>>>>
>>
>
> --------------------------------------------
> Grant Ingersoll
> http://www.lucidimagination.com
>
>
>

--
Lance Norskog
[EMAIL PROTECTED]

By my reckoning, it has been more than 72 hours since voting opened and
we have received seven +1s and no dissenting votes were cast. I'm going
to close the vote now and declare that Mahout trunk is frozen until we
have completed the 0.6 release. By frozen, of course, I mean no more
commits except in response to newly-discovered defect JIRAs that arise
during testing.

Do we have somebody who wishes to be the build-meister for 0.6?

Jeff

I've kept this up to date, so works as far as I know:

https://cwiki.apache.org/MAHOUT/how-to-release.html

On Wed, Jan 25, 2012 at 3:26 PM, Jeff Eastman <[EMAIL PROTECTED]>wrote:

>  +dev@
>
> Didn't notice this was sent to me directly and not via dev@. Can somebody
> who understands the release process outline what it entails?
>
> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze for
> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>  To: Shannon
> Quinn <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
>
> To me it means you are in charge of building and assembling the various
> bits which comprise the 0.6 release. Initially, this would be RC-1 which
> we will all then test. Historically, there have been issues to be
> resolved that are uncovered during this process and RC-i eventually
> leads to a stable release. I think Maven can automate a lot of this
> process but I confess not to know the details.
>
>
>
>
> On 1/24/12 12:21 PM, Shannon Quinn wrote:
> > I'm interested; I'm just curious what being "build-meister" entails :P
> >
> > On 1/23/12 11:04 PM, Jeff Eastman wrote:
> >> By my reckoning, it has been more than 72 hours since voting opened
> >> and we have received seven +1s and no dissenting votes were cast. I'm
> >> going to close the vote now and declare that Mahout trunk is frozen
> >> until we have completed the 0.6 release. By frozen, of course, I mean
> >> no more commits except in response to newly-discovered defect JIRAs
> >> that arise during testing.
> >>
> >> Do we have somebody who wishes to be the build-meister for 0.6?
> >>
> >> Jeff
> >>
> >>
> >
> >
>
>
>
>

Thanks for the link Sean, I though this had been documented but could
not find the page. Now I see it is accessed from the Documentation tab
on the Mahout website and not from any of the Developer Resources links
on that page.

Shannon, not to put you on the spot, but "build-meister" == "release
engineer". You still interested?
On 1/25/12 9:33 AM, Sean Owen wrote:
> I've kept this up to date, so works as far as I know:
>
> https://cwiki.apache.org/MAHOUT/how-to-release.html
>
> On Wed, Jan 25, 2012 at 3:26 PM, Jeff Eastman<[EMAIL PROTECTED]>wrote:
>
>>   +dev@
>>
>> Didn't notice this was sent to me directly and not via dev@. Can somebody
>> who understands the release process outline what it entails?
>>
>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze for
>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>> <[EMAIL PROTECTED]>  <[EMAIL PROTECTED]>   To: Shannon
>> Quinn<[EMAIL PROTECTED]>  <[EMAIL PROTECTED]>
>>
>> To me it means you are in charge of building and assembling the various
>> bits which comprise the 0.6 release. Initially, this would be RC-1 which
>> we will all then test. Historically, there have been issues to be
>> resolved that are uncovered during this process and RC-i eventually
>> leads to a stable release. I think Maven can automate a lot of this
>> process but I confess not to know the details.
>>
>>
>>
>>
>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>> I'm interested; I'm just curious what being "build-meister" entails :P
>>>
>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>> and we have received seven +1s and no dissenting votes were cast. I'm
>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>> until we have completed the 0.6 release. By frozen, of course, I mean
>>>> no more commits except in response to newly-discovered defect JIRAs
>>>> that arise during testing.
>>>>
>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>
>>>> Jeff
>>>>
>>>>
>>>
>>
>>
>>

Definitely. I'm glad there's an explicit guide to follow, though I may still have questions in the next few days.

I'll get started on it today.

iPhone'd

On Jan 25, 2012, at 13:29, Jeff Eastman <[EMAIL PROTECTED]> wrote:

> Thanks for the link Sean, I though this had been documented but could not find the page. Now I see it is accessed from the Documentation tab on the Mahout website and not from any of the Developer Resources links on that page.
>
> Shannon, not to put you on the spot, but "build-meister" == "release engineer". You still interested?
>
>
> On 1/25/12 9:33 AM, Sean Owen wrote:
>> I've kept this up to date, so works as far as I know:
>>
>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>
>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff Eastman<[EMAIL PROTECTED]>wrote:
>>
>>>  +dev@
>>>
>>> Didn't notice this was sent to me directly and not via dev@. Can somebody
>>> who understands the release process outline what it entails?
>>>
>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze for
>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>> <[EMAIL PROTECTED]>  <[EMAIL PROTECTED]>   To: Shannon
>>> Quinn<[EMAIL PROTECTED]>  <[EMAIL PROTECTED]>
>>>
>>> To me it means you are in charge of building and assembling the various
>>> bits which comprise the 0.6 release. Initially, this would be RC-1 which
>>> we will all then test. Historically, there have been issues to be
>>> resolved that are uncovered during this process and RC-i eventually
>>> leads to a stable release. I think Maven can automate a lot of this
>>> process but I confess not to know the details.
>>>
>>>
>>>
>>>
>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>> I'm interested; I'm just curious what being "build-meister" entails :P
>>>>
>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>>> and we have received seven +1s and no dissenting votes were cast. I'm
>>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>>> until we have completed the 0.6 release. By frozen, of course, I mean
>>>>> no more commits except in response to newly-discovered defect JIRAs
>>>>> that arise during testing.
>>>>>
>>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>>
>>>>> Jeff
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>

I wonder what others think of a couple of issues that have popped up recently related to some stuff that is new to 0.6, namely:
M-957 and fixing a minor thing on M-939.  

I think I can get to them tonight or tomorrow.

On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:

> Definitely. I'm glad there's an explicit guide to follow, though I may still have questions in the next few days.
>
> I'll get started on it today.
>
> iPhone'd
>
> On Jan 25, 2012, at 13:29, Jeff Eastman <[EMAIL PROTECTED]> wrote:
>
>> Thanks for the link Sean, I though this had been documented but could not find the page. Now I see it is accessed from the Documentation tab on the Mahout website and not from any of the Developer Resources links on that page.
>>
>> Shannon, not to put you on the spot, but "build-meister" == "release engineer". You still interested?
>>
>>
>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>> I've kept this up to date, so works as far as I know:
>>>
>>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>
>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff Eastman<[EMAIL PROTECTED]>wrote:
>>>
>>>> +dev@
>>>>
>>>> Didn't notice this was sent to me directly and not via dev@. Can somebody
>>>> who understands the release process outline what it entails?
>>>>
>>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze for
>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>>> <[EMAIL PROTECTED]>  <[EMAIL PROTECTED]>   To: Shannon
>>>> Quinn<[EMAIL PROTECTED]>  <[EMAIL PROTECTED]>
>>>>
>>>> To me it means you are in charge of building and assembling the various
>>>> bits which comprise the 0.6 release. Initially, this would be RC-1 which
>>>> we will all then test. Historically, there have been issues to be
>>>> resolved that are uncovered during this process and RC-i eventually
>>>> leads to a stable release. I think Maven can automate a lot of this
>>>> process but I confess not to know the details.
>>>>
>>>>
>>>>
>>>>
>>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>>> I'm interested; I'm just curious what being "build-meister" entails :P
>>>>>
>>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>>>> and we have received seven +1s and no dissenting votes were cast. I'm
>>>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>>>> until we have completed the 0.6 release. By frozen, of course, I mean
>>>>>> no more commits except in response to newly-discovered defect JIRAs
>>>>>> that arise during testing.
>>>>>>
>>>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>>>
>>>>>> Jeff
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>

--------------------------------------------
Grant Ingersoll
http://www.lucidimagination.com

I'd say continue to fix straightforward defects while Shannon gets into
the RC-1 build. IIRC, we've never managed to release an RC-1 so even if
the fixes miss it they will likely be in 0.6

On 1/25/12 2:01 PM, Grant Ingersoll wrote:
> I wonder what others think of a couple of issues that have popped up recently related to some stuff that is new to 0.6, namely:
> M-957 and fixing a minor thing on M-939.
>
> I think I can get to them tonight or tomorrow.
>
> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>
>> Definitely. I'm glad there's an explicit guide to follow, though I may still have questions in the next few days.
>>
>> I'll get started on it today.
>>
>> iPhone'd
>>
>> On Jan 25, 2012, at 13:29, Jeff Eastman<[EMAIL PROTECTED]>  wrote:
>>
>>> Thanks for the link Sean, I though this had been documented but could not find the page. Now I see it is accessed from the Documentation tab on the Mahout website and not from any of the Developer Resources links on that page.
>>>
>>> Shannon, not to put you on the spot, but "build-meister" == "release engineer". You still interested?
>>>
>>>
>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>> I've kept this up to date, so works as far as I know:
>>>>
>>>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>>
>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff Eastman<[EMAIL PROTECTED]>wrote:
>>>>
>>>>> +dev@
>>>>>
>>>>> Didn't notice this was sent to me directly and not via dev@. Can somebody
>>>>> who understands the release process outline what it entails?
>>>>>
>>>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze for
>>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>>>> <[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>    To: Shannon
>>>>> Quinn<[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>
>>>>>
>>>>> To me it means you are in charge of building and assembling the various
>>>>> bits which comprise the 0.6 release. Initially, this would be RC-1 which
>>>>> we will all then test. Historically, there have been issues to be
>>>>> resolved that are uncovered during this process and RC-i eventually
>>>>> leads to a stable release. I think Maven can automate a lot of this
>>>>> process but I confess not to know the details.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>>>> I'm interested; I'm just curious what being "build-meister" entails :P
>>>>>>
>>>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>>>>> and we have received seven +1s and no dissenting votes were cast. I'm
>>>>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>>>>> until we have completed the 0.6 release. By frozen, of course, I mean
>>>>>>> no more commits except in response to newly-discovered defect JIRAs
>>>>>>> that arise during testing.
>>>>>>>
>>>>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>>>>
>>>>>>> Jeff
>>>>>>>
>>>>>>>
>>>>>
>>>>>
> --------------------------------------------
> Grant Ingersoll
> http://www.lucidimagination.com
>
>
>
>

and 959, testing it...

On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
<[EMAIL PROTECTED]> wrote:
> I'd say continue to fix straightforward defects while Shannon gets into the
> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
> fixes miss it they will likely be in 0.6
>
>
> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>
>> I wonder what others think of a couple of issues that have popped up
>> recently related to some stuff that is new to 0.6, namely:
>> M-957 and fixing a minor thing on M-939.
>>
>> I think I can get to them tonight or tomorrow.
>>
>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>
>>> Definitely. I'm glad there's an explicit guide to follow, though I may
>>> still have questions in the next few days.
>>>
>>> I'll get started on it today.
>>>
>>> iPhone'd
>>>
>>> On Jan 25, 2012, at 13:29, Jeff Eastman<[EMAIL PROTECTED]>
>>>  wrote:
>>>
>>>> Thanks for the link Sean, I though this had been documented but could
>>>> not find the page. Now I see it is accessed from the Documentation tab on
>>>> the Mahout website and not from any of the Developer Resources links on that
>>>> page.
>>>>
>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>> engineer". You still interested?
>>>>
>>>>
>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>
>>>>> I've kept this up to date, so works as far as I know:
>>>>>
>>>>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>>>
>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>> Eastman<[EMAIL PROTECTED]>wrote:
>>>>>
>>>>>> +dev@
>>>>>>
>>>>>> Didn't notice this was sent to me directly and not via dev@. Can
>>>>>> somebody
>>>>>> who understands the release process outline what it entails?
>>>>>>
>>>>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze
>>>>>> for
>>>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>>>>> <[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>    To:
>>>>>> Shannon
>>>>>> Quinn<[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>
>>>>>>
>>>>>> To me it means you are in charge of building and assembling the
>>>>>> various
>>>>>> bits which comprise the 0.6 release. Initially, this would be RC-1
>>>>>> which
>>>>>> we will all then test. Historically, there have been issues to be
>>>>>> resolved that are uncovered during this process and RC-i eventually
>>>>>> leads to a stable release. I think Maven can automate a lot of this
>>>>>> process but I confess not to know the details.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>>>>>
>>>>>>> I'm interested; I'm just curious what being "build-meister" entails
>>>>>>> :P
>>>>>>>
>>>>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>>>>>
>>>>>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>>>>>> and we have received seven +1s and no dissenting votes were cast.
>>>>>>>> I'm
>>>>>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>>>>>> until we have completed the 0.6 release. By frozen, of course, I
>>>>>>>> mean
>>>>>>>> no more commits except in response to newly-discovered defect JIRAs
>>>>>>>> that arise during testing.
>>>>>>>>
>>>>>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>>>>>
>>>>>>>> Jeff
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>> --------------------------------------------
>> Grant Ingersoll
>> http://www.lucidimagination.com
>>
>>
>>
>>
>

i am seeking more input on 959 now after looking at it in more
details. I will not be committing it unless convinced that patch
actually has value. I believe as it is now, it is switching
serialization behavior to one not desired by default.

-d

On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov <[EMAIL PROTECTED]> wrote:
> and 959, testing it...
>
> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
> <[EMAIL PROTECTED]> wrote:
>> I'd say continue to fix straightforward defects while Shannon gets into the
>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>> fixes miss it they will likely be in 0.6
>>
>>
>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>
>>> I wonder what others think of a couple of issues that have popped up
>>> recently related to some stuff that is new to 0.6, namely:
>>> M-957 and fixing a minor thing on M-939.
>>>
>>> I think I can get to them tonight or tomorrow.
>>>
>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>
>>>> Definitely. I'm glad there's an explicit guide to follow, though I may
>>>> still have questions in the next few days.
>>>>
>>>> I'll get started on it today.
>>>>
>>>> iPhone'd
>>>>
>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<[EMAIL PROTECTED]>
>>>>  wrote:
>>>>
>>>>> Thanks for the link Sean, I though this had been documented but could
>>>>> not find the page. Now I see it is accessed from the Documentation tab on
>>>>> the Mahout website and not from any of the Developer Resources links on that
>>>>> page.
>>>>>
>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>> engineer". You still interested?
>>>>>
>>>>>
>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>
>>>>>> I've kept this up to date, so works as far as I know:
>>>>>>
>>>>>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>>>>
>>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>>> Eastman<[EMAIL PROTECTED]>wrote:
>>>>>>
>>>>>>> +dev@
>>>>>>>
>>>>>>> Didn't notice this was sent to me directly and not via dev@. Can
>>>>>>> somebody
>>>>>>> who understands the release process outline what it entails?
>>>>>>>
>>>>>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze
>>>>>>> for
>>>>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>>>>>> <[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>    To:
>>>>>>> Shannon
>>>>>>> Quinn<[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>
>>>>>>>
>>>>>>> To me it means you are in charge of building and assembling the
>>>>>>> various
>>>>>>> bits which comprise the 0.6 release. Initially, this would be RC-1
>>>>>>> which
>>>>>>> we will all then test. Historically, there have been issues to be
>>>>>>> resolved that are uncovered during this process and RC-i eventually
>>>>>>> leads to a stable release. I think Maven can automate a lot of this
>>>>>>> process but I confess not to know the details.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>>>>>>
>>>>>>>> I'm interested; I'm just curious what being "build-meister" entails
>>>>>>>> :P
>>>>>>>>
>>>>>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>>>>>>
>>>>>>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>>>>>>> and we have received seven +1s and no dissenting votes were cast.
>>>>>>>>> I'm
>>>>>>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>>>>>>> until we have completed the 0.6 release. By frozen, of course, I
>>>>>>>>> mean
>>>>>>>>> no more commits except in response to newly-discovered defect JIRAs
>>>>>>>>> that arise during testing.
>>>>>>>>>
>>>>>>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>>>>>>
>>>>>>>>> Jeff
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>> --------------------------------------------
>>> Grant Ingersoll
>>> http://www.lucidimagination.com
>>>
>>>
>>>
>>>
>>

959 is out of code freeze list now. Sorry for noise on the thread.

-d

On Wed, Jan 25, 2012 at 1:49 PM, Dmitriy Lyubimov <[EMAIL PROTECTED]> wrote:
> i am seeking more input on 959 now after looking at it in more
> details. I will not be committing it unless convinced that patch
> actually has value. I believe as it is now, it is switching
> serialization behavior to one not desired by default.
>
> -d
>
> On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov <[EMAIL PROTECTED]> wrote:
>> and 959, testing it...
>>
>> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
>> <[EMAIL PROTECTED]> wrote:
>>> I'd say continue to fix straightforward defects while Shannon gets into the
>>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>>> fixes miss it they will likely be in 0.6
>>>
>>>
>>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>>
>>>> I wonder what others think of a couple of issues that have popped up
>>>> recently related to some stuff that is new to 0.6, namely:
>>>> M-957 and fixing a minor thing on M-939.
>>>>
>>>> I think I can get to them tonight or tomorrow.
>>>>
>>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>>
>>>>> Definitely. I'm glad there's an explicit guide to follow, though I may
>>>>> still have questions in the next few days.
>>>>>
>>>>> I'll get started on it today.
>>>>>
>>>>> iPhone'd
>>>>>
>>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<[EMAIL PROTECTED]>
>>>>>  wrote:
>>>>>
>>>>>> Thanks for the link Sean, I though this had been documented but could
>>>>>> not find the page. Now I see it is accessed from the Documentation tab on
>>>>>> the Mahout website and not from any of the Developer Resources links on that
>>>>>> page.
>>>>>>
>>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>>> engineer". You still interested?
>>>>>>
>>>>>>
>>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>>
>>>>>>> I've kept this up to date, so works as far as I know:
>>>>>>>
>>>>>>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>>>>>
>>>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>>>> Eastman<[EMAIL PROTECTED]>wrote:
>>>>>>>
>>>>>>>> +dev@
>>>>>>>>
>>>>>>>> Didn't notice this was sent to me directly and not via dev@. Can
>>>>>>>> somebody
>>>>>>>> who understands the release process outline what it entails?
>>>>>>>>
>>>>>>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze
>>>>>>>> for
>>>>>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>>>>>>> <[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>    To:
>>>>>>>> Shannon
>>>>>>>> Quinn<[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>
>>>>>>>>
>>>>>>>> To me it means you are in charge of building and assembling the
>>>>>>>> various
>>>>>>>> bits which comprise the 0.6 release. Initially, this would be RC-1
>>>>>>>> which
>>>>>>>> we will all then test. Historically, there have been issues to be
>>>>>>>> resolved that are uncovered during this process and RC-i eventually
>>>>>>>> leads to a stable release. I think Maven can automate a lot of this
>>>>>>>> process but I confess not to know the details.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>>>>>>>
>>>>>>>>> I'm interested; I'm just curious what being "build-meister" entails
>>>>>>>>> :P
>>>>>>>>>
>>>>>>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>>>>>>>
>>>>>>>>>> By my reckoning, it has been more than 72 hours since voting opened
>>>>>>>>>> and we have received seven +1s and no dissenting votes were cast.
>>>>>>>>>> I'm
>>>>>>>>>> going to close the vote now and declare that Mahout trunk is frozen
>>>>>>>>>> until we have completed the 0.6 release. By frozen, of course, I
>>>>>>>>>> mean
>>>>>>>>>> no more commits except in response to newly-discovered defect JIRAs
>>>>>>>>>> that arise during testing.
>>>>>>>>>>
>>>>>>>>>> Do we have somebody who wishes to be the build-meister for 0.6?
>>>>>>>>>>
>>>>>>>>>> Jeff
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>

Couple questions from the build meister.

All the tests run just fine, so we're set on the code end of things.

Step 2 mentions updating news; I'm not clear where this resides, or what
news I should include?
Step 4 mentions updating Mahout's KEYS file; I've done so, but I'm
getting an error when I try to commit ("access to
'/repos/asf/!svn/act/lots-of-hex' forbidden").

I'm pressing ahead with the other steps. Thanks in advance.

On 1/25/2012 5:05 PM, Dmitriy Lyubimov wrote:
> 959 is out of code freeze list now. Sorry for noise on the thread.
>
> -d
>
> On Wed, Jan 25, 2012 at 1:49 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>  wrote:
>> i am seeking more input on 959 now after looking at it in more
>> details. I will not be committing it unless convinced that patch
>> actually has value. I believe as it is now, it is switching
>> serialization behavior to one not desired by default.
>>
>> -d
>>
>> On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>  wrote:
>>> and 959, testing it...
>>>
>>> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
>>> <[EMAIL PROTECTED]>  wrote:
>>>> I'd say continue to fix straightforward defects while Shannon gets into the
>>>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>>>> fixes miss it they will likely be in 0.6
>>>>
>>>>
>>>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>>> I wonder what others think of a couple of issues that have popped up
>>>>> recently related to some stuff that is new to 0.6, namely:
>>>>> M-957 and fixing a minor thing on M-939.
>>>>>
>>>>> I think I can get to them tonight or tomorrow.
>>>>>
>>>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>>>
>>>>>> Definitely. I'm glad there's an explicit guide to follow, though I may
>>>>>> still have questions in the next few days.
>>>>>>
>>>>>> I'll get started on it today.
>>>>>>
>>>>>> iPhone'd
>>>>>>
>>>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<[EMAIL PROTECTED]>
>>>>>>   wrote:
>>>>>>
>>>>>>> Thanks for the link Sean, I though this had been documented but could
>>>>>>> not find the page. Now I see it is accessed from the Documentation tab on
>>>>>>> the Mahout website and not from any of the Developer Resources links on that
>>>>>>> page.
>>>>>>>
>>>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>>>> engineer". You still interested?
>>>>>>>
>>>>>>>
>>>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>>> I've kept this up to date, so works as far as I know:
>>>>>>>>
>>>>>>>> https://cwiki.apache.org/MAHOUT/how-to-release.html
>>>>>>>>
>>>>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>>>>> Eastman<[EMAIL PROTECTED]>wrote:
>>>>>>>>
>>>>>>>>> +dev@
>>>>>>>>>
>>>>>>>>> Didn't notice this was sent to me directly and not via dev@. Can
>>>>>>>>> somebody
>>>>>>>>> who understands the release process outline what it entails?
>>>>>>>>>
>>>>>>>>> -------- Original Message --------  Subject: Re: [VOTE] Code Freeze
>>>>>>>>> for
>>>>>>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff Eastman
>>>>>>>>> <[EMAIL PROTECTED]>     <[EMAIL PROTECTED]>      To:
>>>>>>>>> Shannon
>>>>>>>>> Quinn<[EMAIL PROTECTED]>     <[EMAIL PROTECTED]>
>>>>>>>>>
>>>>>>>>> To me it means you are in charge of building and assembling the
>>>>>>>>> various
>>>>>>>>> bits which comprise the 0.6 release. Initially, this would be RC-1
>>>>>>>>> which
>>>>>>>>> we will all then test. Historically, there have been issues to be
>>>>>>>>> resolved that are uncovered during this process and RC-i eventually
>>>>>>>>> leads to a stable release. I think Maven can automate a lot of this
>>>>>>>>> process but I confess not to know the details.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 1/24/12 12:21 PM, Shannon Quinn wrote:
>>>>>>>>>> I'm interested; I'm just curious what being "build-meister" entails
>>>>>>>>>> :P
>>>>>>>>>>
>>>>>>>>>> On 1/23/12 11:04 PM, Jeff Eastman wrote:
>>>>>>>>>>> By my reckoning, it has been more than 72 hours since voting opened

#2 is pointing you to where the web site lives in SVN;
https://svn.apache.org/repos/asf/mahout/site/new_website
You want a new "0.6 released" point -- copy the old one as you like.
The live copy is available from people.apache.org. See /www and you'll find
it. Eventually you will push the new page there.

#4 you are updating the Mahout KEYS file right? You should be able to
commit to that just fine. E-mail me off-list if it just won't work and I'll
try to commit it.

On Fri, Jan 27, 2012 at 3:56 AM, Shannon Quinn <[EMAIL PROTECTED]> wrote:

> Couple questions from the build meister.
>
> All the tests run just fine, so we're set on the code end of things.
>
> Step 2 mentions updating news; I'm not clear where this resides, or what
> news I should include?
> Step 4 mentions updating Mahout's KEYS file; I've done so, but I'm getting
> an error when I try to commit ("access to '/repos/asf/!svn/act/lots-of-**hex'
> forbidden").
>
> I'm pressing ahead with the other steps. Thanks in advance.
>
>
> On 1/25/2012 5:05 PM, Dmitriy Lyubimov wrote:
>
>> 959 is out of code freeze list now. Sorry for noise on the thread.
>>
>> -d
>>
>> On Wed, Jan 25, 2012 at 1:49 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>  wrote:
>>
>>> i am seeking more input on 959 now after looking at it in more
>>> details. I will not be committing it unless convinced that patch
>>> actually has value. I believe as it is now, it is switching
>>> serialization behavior to one not desired by default.
>>>
>>> -d
>>>
>>> On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>>  wrote:
>>>
>>>> and 959, testing it...
>>>>
>>>> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
>>>> <[EMAIL PROTECTED]>  wrote:
>>>>
>>>>> I'd say continue to fix straightforward defects while Shannon gets
>>>>> into the
>>>>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>>>>> fixes miss it they will likely be in 0.6
>>>>>
>>>>>
>>>>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>>>
>>>>>> I wonder what others think of a couple of issues that have popped up
>>>>>> recently related to some stuff that is new to 0.6, namely:
>>>>>> M-957 and fixing a minor thing on M-939.
>>>>>>
>>>>>> I think I can get to them tonight or tomorrow.
>>>>>>
>>>>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>>>>
>>>>>>  Definitely. I'm glad there's an explicit guide to follow, though I
>>>>>>> may
>>>>>>> still have questions in the next few days.
>>>>>>>
>>>>>>> I'll get started on it today.
>>>>>>>
>>>>>>> iPhone'd
>>>>>>>
>>>>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<jdog@**windwardsolutions.com<[EMAIL PROTECTED]>
>>>>>>> >
>>>>>>>  wrote:
>>>>>>>
>>>>>>>  Thanks for the link Sean, I though this had been documented but
>>>>>>>> could
>>>>>>>> not find the page. Now I see it is accessed from the Documentation
>>>>>>>> tab on
>>>>>>>> the Mahout website and not from any of the Developer Resources
>>>>>>>> links on that
>>>>>>>> page.
>>>>>>>>
>>>>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>>>>> engineer". You still interested?
>>>>>>>>
>>>>>>>>
>>>>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>>>
>>>>>>>>> I've kept this up to date, so works as far as I know:
>>>>>>>>>
>>>>>>>>> https://cwiki.apache.org/**MAHOUT/how-to-release.html<https://cwiki.apache.org/MAHOUT/how-to-release.html>
>>>>>>>>>
>>>>>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>>>>>> Eastman<jdog@**windwardsolutions.com <[EMAIL PROTECTED]>
>>>>>>>>> >wrote:
>>>>>>>>>
>>>>>>>>>  +dev@
>>>>>>>>>>
>>>>>>>>>> Didn't notice this was sent to me directly and not via dev@. Can
>>>>>>>>>> somebody
>>>>>>>>>> who understands the release process outline what it entails?
>>>>>>>>>>
>>>>>>>>>> -------- Original Message --------  Subject: Re: [VOTE] Code
>>>>>>>>>> Freeze
>>>>>>>>>> for
>>>>>>>>>> Mahout 0.6  Date: Tue, 24 Jan 2012 12:34:15 -0700  From: Jeff
>>>>>>>>>> Eastman
>>>>>>>>>> <[EMAIL PROTECTED]>     <[EMAIL PROTECTED]>
>>>>

Seems we have 4 open issues against 0.6 at the moment.  3 of them I have and am waiting for responses from the original reporters for feedback.  Two of them are related (957, 962, and there is a patch)

On Jan 27, 2012, at 3:20 AM, Sean Owen wrote:

> #2 is pointing you to where the web site lives in SVN;
> https://svn.apache.org/repos/asf/mahout/site/new_website
> You want a new "0.6 released" point -- copy the old one as you like.
> The live copy is available from people.apache.org. See /www and you'll find
> it. Eventually you will push the new page there.
>
> #4 you are updating the Mahout KEYS file right? You should be able to
> commit to that just fine. E-mail me off-list if it just won't work and I'll
> try to commit it.
>
> On Fri, Jan 27, 2012 at 3:56 AM, Shannon Quinn <[EMAIL PROTECTED]> wrote:
>
>> Couple questions from the build meister.
>>
>> All the tests run just fine, so we're set on the code end of things.
>>
>> Step 2 mentions updating news; I'm not clear where this resides, or what
>> news I should include?
>> Step 4 mentions updating Mahout's KEYS file; I've done so, but I'm getting
>> an error when I try to commit ("access to '/repos/asf/!svn/act/lots-of-**hex'
>> forbidden").
>>
>> I'm pressing ahead with the other steps. Thanks in advance.
>>
>>
>> On 1/25/2012 5:05 PM, Dmitriy Lyubimov wrote:
>>
>>> 959 is out of code freeze list now. Sorry for noise on the thread.
>>>
>>> -d
>>>
>>> On Wed, Jan 25, 2012 at 1:49 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>> i am seeking more input on 959 now after looking at it in more
>>>> details. I will not be committing it unless convinced that patch
>>>> actually has value. I believe as it is now, it is switching
>>>> serialization behavior to one not desired by default.
>>>>
>>>> -d
>>>>
>>>> On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>>> and 959, testing it...
>>>>>
>>>>> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
>>>>> <[EMAIL PROTECTED]>  wrote:
>>>>>
>>>>>> I'd say continue to fix straightforward defects while Shannon gets
>>>>>> into the
>>>>>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>>>>>> fixes miss it they will likely be in 0.6
>>>>>>
>>>>>>
>>>>>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>>>>
>>>>>>> I wonder what others think of a couple of issues that have popped up
>>>>>>> recently related to some stuff that is new to 0.6, namely:
>>>>>>> M-957 and fixing a minor thing on M-939.
>>>>>>>
>>>>>>> I think I can get to them tonight or tomorrow.
>>>>>>>
>>>>>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>>>>>
>>>>>>> Definitely. I'm glad there's an explicit guide to follow, though I
>>>>>>>> may
>>>>>>>> still have questions in the next few days.
>>>>>>>>
>>>>>>>> I'll get started on it today.
>>>>>>>>
>>>>>>>> iPhone'd
>>>>>>>>
>>>>>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<jdog@**windwardsolutions.com<[EMAIL PROTECTED]>
>>>>>>>>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Thanks for the link Sean, I though this had been documented but
>>>>>>>>> could
>>>>>>>>> not find the page. Now I see it is accessed from the Documentation
>>>>>>>>> tab on
>>>>>>>>> the Mahout website and not from any of the Developer Resources
>>>>>>>>> links on that
>>>>>>>>> page.
>>>>>>>>>
>>>>>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>>>>>> engineer". You still interested?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>>>>
>>>>>>>>>> I've kept this up to date, so works as far as I know:
>>>>>>>>>>
>>>>>>>>>> https://cwiki.apache.org/**MAHOUT/how-to-release.html<https://cwiki.apache.org/MAHOUT/how-to-release.html>
>>>>>>>>>>
>>>>>>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>>>>>>> Eastman<jdog@**windwardsolutions.com <[EMAIL PROTECTED]>
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> +dev@
>>>>>>>>>>>
>>>>>>>>>>> Didn't notice this was sent to me directly and not via dev@. Can

Grant Ingersoll
http://www.lucidimagination.com

No worries; gives me time to compile the changes to post on the site.

On 1/27/2012 4:46 PM, Grant Ingersoll wrote:
> Seems we have 4 open issues against 0.6 at the moment.  3 of them I have and am waiting for responses from the original reporters for feedback.  Two of them are related (957, 962, and there is a patch)
>
> On Jan 27, 2012, at 3:20 AM, Sean Owen wrote:
>
>> #2 is pointing you to where the web site lives in SVN;
>> https://svn.apache.org/repos/asf/mahout/site/new_website
>> You want a new "0.6 released" point -- copy the old one as you like.
>> The live copy is available from people.apache.org. See /www and you'll find
>> it. Eventually you will push the new page there.
>>
>> #4 you are updating the Mahout KEYS file right? You should be able to
>> commit to that just fine. E-mail me off-list if it just won't work and I'll
>> try to commit it.
>>
>> On Fri, Jan 27, 2012 at 3:56 AM, Shannon Quinn<[EMAIL PROTECTED]>  wrote:
>>
>>> Couple questions from the build meister.
>>>
>>> All the tests run just fine, so we're set on the code end of things.
>>>
>>> Step 2 mentions updating news; I'm not clear where this resides, or what
>>> news I should include?
>>> Step 4 mentions updating Mahout's KEYS file; I've done so, but I'm getting
>>> an error when I try to commit ("access to '/repos/asf/!svn/act/lots-of-**hex'
>>> forbidden").
>>>
>>> I'm pressing ahead with the other steps. Thanks in advance.
>>>
>>>
>>> On 1/25/2012 5:05 PM, Dmitriy Lyubimov wrote:
>>>
>>>> 959 is out of code freeze list now. Sorry for noise on the thread.
>>>>
>>>> -d
>>>>
>>>> On Wed, Jan 25, 2012 at 1:49 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>>> i am seeking more input on 959 now after looking at it in more
>>>>> details. I will not be committing it unless convinced that patch
>>>>> actually has value. I believe as it is now, it is switching
>>>>> serialization behavior to one not desired by default.
>>>>>
>>>>> -d
>>>>>
>>>>> On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>
>>>>>> and 959, testing it...
>>>>>>
>>>>>> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
>>>>>> <[EMAIL PROTECTED]>   wrote:
>>>>>>
>>>>>>> I'd say continue to fix straightforward defects while Shannon gets
>>>>>>> into the
>>>>>>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>>>>>>> fixes miss it they will likely be in 0.6
>>>>>>>
>>>>>>>
>>>>>>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>>>>>
>>>>>>>> I wonder what others think of a couple of issues that have popped up
>>>>>>>> recently related to some stuff that is new to 0.6, namely:
>>>>>>>> M-957 and fixing a minor thing on M-939.
>>>>>>>>
>>>>>>>> I think I can get to them tonight or tomorrow.
>>>>>>>>
>>>>>>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>>>>>>
>>>>>>>> Definitely. I'm glad there's an explicit guide to follow, though I
>>>>>>>>> may
>>>>>>>>> still have questions in the next few days.
>>>>>>>>>
>>>>>>>>> I'll get started on it today.
>>>>>>>>>
>>>>>>>>> iPhone'd
>>>>>>>>>
>>>>>>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<jdog@**windwardsolutions.com<[EMAIL PROTECTED]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Thanks for the link Sean, I though this had been documented but
>>>>>>>>>> could
>>>>>>>>>> not find the page. Now I see it is accessed from the Documentation
>>>>>>>>>> tab on
>>>>>>>>>> the Mahout website and not from any of the Developer Resources
>>>>>>>>>> links on that
>>>>>>>>>> page.
>>>>>>>>>>
>>>>>>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>>>>>>> engineer". You still interested?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>>>>>
>>>>>>>>>>> I've kept this up to date, so works as far as I know:
>>>>>>>>>>>
>>>>>>>>>>> https://cwiki.apache.org/**MAHOUT/how-to-release.html<https://cwiki.apache.org/MAHOUT/how-to-release.html>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Jan 25, 2012 at 3:26 PM, Jeff
>>>>>>>>>>> Eastman<jdog@**windwardsolutions.com<[EMAIL PROTECTED]>

I think M-957 is good to go.  I think M-960 is the only thing open now and it is assigned to Sean.
On Jan 27, 2012, at 4:59 PM, Shannon Quinn wrote:

> No worries; gives me time to compile the changes to post on the site.
>
> On 1/27/2012 4:46 PM, Grant Ingersoll wrote:
>> Seems we have 4 open issues against 0.6 at the moment.  3 of them I have and am waiting for responses from the original reporters for feedback.  Two of them are related (957, 962, and there is a patch)
>>
>> On Jan 27, 2012, at 3:20 AM, Sean Owen wrote:
>>
>>> #2 is pointing you to where the web site lives in SVN;
>>> https://svn.apache.org/repos/asf/mahout/site/new_website
>>> You want a new "0.6 released" point -- copy the old one as you like.
>>> The live copy is available from people.apache.org. See /www and you'll find
>>> it. Eventually you will push the new page there.
>>>
>>> #4 you are updating the Mahout KEYS file right? You should be able to
>>> commit to that just fine. E-mail me off-list if it just won't work and I'll
>>> try to commit it.
>>>
>>> On Fri, Jan 27, 2012 at 3:56 AM, Shannon Quinn<[EMAIL PROTECTED]>  wrote:
>>>
>>>> Couple questions from the build meister.
>>>>
>>>> All the tests run just fine, so we're set on the code end of things.
>>>>
>>>> Step 2 mentions updating news; I'm not clear where this resides, or what
>>>> news I should include?
>>>> Step 4 mentions updating Mahout's KEYS file; I've done so, but I'm getting
>>>> an error when I try to commit ("access to '/repos/asf/!svn/act/lots-of-**hex'
>>>> forbidden").
>>>>
>>>> I'm pressing ahead with the other steps. Thanks in advance.
>>>>
>>>>
>>>> On 1/25/2012 5:05 PM, Dmitriy Lyubimov wrote:
>>>>
>>>>> 959 is out of code freeze list now. Sorry for noise on the thread.
>>>>>
>>>>> -d
>>>>>
>>>>> On Wed, Jan 25, 2012 at 1:49 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>
>>>>>> i am seeking more input on 959 now after looking at it in more
>>>>>> details. I will not be committing it unless convinced that patch
>>>>>> actually has value. I believe as it is now, it is switching
>>>>>> serialization behavior to one not desired by default.
>>>>>>
>>>>>> -d
>>>>>>
>>>>>> On Wed, Jan 25, 2012 at 1:27 PM, Dmitriy Lyubimov<[EMAIL PROTECTED]>
>>>>>> wrote:
>>>>>>
>>>>>>> and 959, testing it...
>>>>>>>
>>>>>>> On Wed, Jan 25, 2012 at 1:15 PM, Jeff Eastman
>>>>>>> <[EMAIL PROTECTED]>   wrote:
>>>>>>>
>>>>>>>> I'd say continue to fix straightforward defects while Shannon gets
>>>>>>>> into the
>>>>>>>> RC-1 build. IIRC, we've never managed to release an RC-1 so even if the
>>>>>>>> fixes miss it they will likely be in 0.6
>>>>>>>>
>>>>>>>>
>>>>>>>> On 1/25/12 2:01 PM, Grant Ingersoll wrote:
>>>>>>>>
>>>>>>>>> I wonder what others think of a couple of issues that have popped up
>>>>>>>>> recently related to some stuff that is new to 0.6, namely:
>>>>>>>>> M-957 and fixing a minor thing on M-939.
>>>>>>>>>
>>>>>>>>> I think I can get to them tonight or tomorrow.
>>>>>>>>>
>>>>>>>>> On Jan 25, 2012, at 3:20 PM, Shannon Quinn wrote:
>>>>>>>>>
>>>>>>>>> Definitely. I'm glad there's an explicit guide to follow, though I
>>>>>>>>>> may
>>>>>>>>>> still have questions in the next few days.
>>>>>>>>>>
>>>>>>>>>> I'll get started on it today.
>>>>>>>>>>
>>>>>>>>>> iPhone'd
>>>>>>>>>>
>>>>>>>>>> On Jan 25, 2012, at 13:29, Jeff Eastman<jdog@**windwardsolutions.com<[EMAIL PROTECTED]>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks for the link Sean, I though this had been documented but
>>>>>>>>>>> could
>>>>>>>>>>> not find the page. Now I see it is accessed from the Documentation
>>>>>>>>>>> tab on
>>>>>>>>>>> the Mahout website and not from any of the Developer Resources
>>>>>>>>>>> links on that
>>>>>>>>>>> page.
>>>>>>>>>>>
>>>>>>>>>>> Shannon, not to put you on the spot, but "build-meister" == "release
>>>>>>>>>>> engineer". You still interested?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 1/25/12 9:33 AM, Sean Owen wrote:
>>>>>>>>>>>
>>
Grant Ingersoll
http://www.lucidimagination.com

Oh, didn't realize someone had marked that for me.
It is assigned to Sebastian now, and is not for 0.6

On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll <[EMAIL PROTECTED]>wrote:

> I think M-957 is good to go.  I think M-960 is the only thing open now and
> it is assigned to Sean.
>
>

Shall I mark 957 as resolved, then?

On 1/28/2012 10:33 AM, Sean Owen wrote:
> Oh, didn't realize someone had marked that for me.
> It is assigned to Sebastian now, and is not for 0.6
>
> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>wrote:
>
>> I think M-957 is good to go.  I think M-960 is the only thing open now and
>> it is assigned to Sean.
>>
>>

Should be done, looks like we are good to go.

On Jan 28, 2012, at 4:39 PM, Shannon Quinn wrote:

> Shall I mark 957 as resolved, then?
>
> On 1/28/2012 10:33 AM, Sean Owen wrote:
>> Oh, didn't realize someone had marked that for me.
>> It is assigned to Sebastian now, and is not for 0.6
>>
>> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>wrote:
>>
>>> I think M-957 is good to go.  I think M-960 is the only thing open now and
>>> it is assigned to Sean.
>>>
>>>

Now we have two issues open: 966 and 967.

On 1/30/2012 8:20 AM, Grant Ingersoll wrote:
> Should be done, looks like we are good to go.
>
> On Jan 28, 2012, at 4:39 PM, Shannon Quinn wrote:
>
>> Shall I mark 957 as resolved, then?
>>
>> On 1/28/2012 10:33 AM, Sean Owen wrote:
>>> Oh, didn't realize someone had marked that for me.
>>> It is assigned to Sebastian now, and is not for 0.6
>>>
>>> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>wrote:
>>>
>>>> I think M-957 is good to go.  I think M-960 is the only thing open now and
>>>> it is assigned to Sean.
>>>>
>>>>
>
>

Reporters should not be marking them for 0.6. I'll fix that.

On Tue, Jan 31, 2012 at 12:27 PM, Shannon Quinn <[EMAIL PROTECTED]> wrote:

> Now we have two issues open: 966 and 967.
>
>
> On 1/30/2012 8:20 AM, Grant Ingersoll wrote:
>
>> Should be done, looks like we are good to go.
>>
>> On Jan 28, 2012, at 4:39 PM, Shannon Quinn wrote:
>>
>>  Shall I mark 957 as resolved, then?
>>>
>>> On 1/28/2012 10:33 AM, Sean Owen wrote:
>>>
>>>> Oh, didn't realize someone had marked that for me.
>>>> It is assigned to Sebastian now, and is not for 0.6
>>>>
>>>> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>**
>>>> wrote:
>>>>
>>>>  I think M-957 is good to go.  I think M-960 is the only thing open now
>>>>> and
>>>>> it is assigned to Sean.
>>>>>
>>>>>
>>>>>
>>
>>

Shannon, any luck on an RC?

On Jan 31, 2012, at 7:29 AM, Sean Owen wrote:

> Reporters should not be marking them for 0.6. I'll fix that.
>
> On Tue, Jan 31, 2012 at 12:27 PM, Shannon Quinn <[EMAIL PROTECTED]> wrote:
>
>> Now we have two issues open: 966 and 967.
>>
>>
>> On 1/30/2012 8:20 AM, Grant Ingersoll wrote:
>>
>>> Should be done, looks like we are good to go.
>>>
>>> On Jan 28, 2012, at 4:39 PM, Shannon Quinn wrote:
>>>
>>> Shall I mark 957 as resolved, then?
>>>>
>>>> On 1/28/2012 10:33 AM, Sean Owen wrote:
>>>>
>>>>> Oh, didn't realize someone had marked that for me.
>>>>> It is assigned to Sebastian now, and is not for 0.6
>>>>>
>>>>> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>**
>>>>> wrote:
>>>>>
>>>>> I think M-957 is good to go.  I think M-960 is the only thing open now
>>>>>> and
>>>>>> it is assigned to Sean.
>>>>>>
>>>>>>
>>>>>>
>>>
>>>

Running step 9 in the process now: the maven release. Once the tests are
finished running, it should be a simple matter of reviewing the
artifacts and calling the vote. With any luck that'll start tonight.

On 1/31/12 6:43 PM, Grant Ingersoll wrote:
> Shannon, any luck on an RC?
>
> On Jan 31, 2012, at 7:29 AM, Sean Owen wrote:
>
>> Reporters should not be marking them for 0.6. I'll fix that.
>>
>> On Tue, Jan 31, 2012 at 12:27 PM, Shannon Quinn<[EMAIL PROTECTED]>  wrote:
>>
>>> Now we have two issues open: 966 and 967.
>>>
>>>
>>> On 1/30/2012 8:20 AM, Grant Ingersoll wrote:
>>>
>>>> Should be done, looks like we are good to go.
>>>>
>>>> On Jan 28, 2012, at 4:39 PM, Shannon Quinn wrote:
>>>>
>>>> Shall I mark 957 as resolved, then?
>>>>> On 1/28/2012 10:33 AM, Sean Owen wrote:
>>>>>
>>>>>> Oh, didn't realize someone had marked that for me.
>>>>>> It is assigned to Sebastian now, and is not for 0.6
>>>>>>
>>>>>> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>**
>>>>>> wrote:
>>>>>>
>>>>>> I think M-957 is good to go.  I think M-960 is the only thing open now
>>>>>>> and
>>>>>>> it is assigned to Sean.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>
>

Build crashed on me due to a java heap size problem. It was uploading
the gzipped release to the repository and counting out the KBs, but
apparently 32772 KB was its limit. Any suggestions? Just try closing out
more programs? :P

On 1/31/2012 6:43 PM, Grant Ingersoll wrote:
> Shannon, any luck on an RC?
>
> On Jan 31, 2012, at 7:29 AM, Sean Owen wrote:
>
>> Reporters should not be marking them for 0.6. I'll fix that.
>>
>> On Tue, Jan 31, 2012 at 12:27 PM, Shannon Quinn<[EMAIL PROTECTED]>  wrote:
>>
>>> Now we have two issues open: 966 and 967.
>>>
>>>
>>> On 1/30/2012 8:20 AM, Grant Ingersoll wrote:
>>>
>>>> Should be done, looks like we are good to go.
>>>>
>>>> On Jan 28, 2012, at 4:39 PM, Shannon Quinn wrote:
>>>>
>>>> Shall I mark 957 as resolved, then?
>>>>> On 1/28/2012 10:33 AM, Sean Owen wrote:
>>>>>
>>>>>> Oh, didn't realize someone had marked that for me.
>>>>>> It is assigned to Sebastian now, and is not for 0.6
>>>>>>
>>>>>> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll<[EMAIL PROTECTED]>**
>>>>>> wrote:
>>>>>>
>>>>>> I think M-957 is good to go.  I think M-960 is the only thing open now
>>>>>>> and
>>>>>>> it is assigned to Sean.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>
>

The tests need heap to run, but not the upload. You will have had to set
MAVEN_OPTS=-Xmx1g or something to get the test part to pass; I can't
imagine there's a memory issue for upload. Maybe your internet connection
is slow, or some hop along the way -- try again? does release:prepare
succeed? I would do that first, and then release:perform only if it works.

On Wed, Feb 1, 2012 at 3:12 AM, Shannon Quinn <[EMAIL PROTECTED]> wrote:

> Build crashed on me due to a java heap size problem. It was uploading the
> gzipped release to the repository and counting out the KBs, but apparently
> 32772 KB was its limit. Any suggestions? Just try closing out more
> programs? :P
>
>
>

On Jan 28, 2012, at 10:33 AM, Sean Owen wrote:

> Oh, didn't realize someone had marked that for me.
> It is assigned to Sebastian now, and is not for 0.6

Probably b/c you are the "lead" on that component.

>
> On Sat, Jan 28, 2012 at 3:28 PM, Grant Ingersoll <[EMAIL PROTECTED]>wrote:
>
>> I think M-957 is good to go.  I think M-960 is the only thing open now and
>> it is assigned to Sean.
>>
>>