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 >>>>> >>>>> >>>> >>> >>> >>> >
