[jira] [Commented] (MAHOUT-1668) Automate release process

["Ted Dunning (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAHOUT-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393127#comment-14393127 ] 

Ted Dunning commented on MAHOUT-1668:
-------------------------------------

Signing cannot be done on shared hardware that you don't control.  That still leaves a vat of stuff that can be done by the automated system, but you need some way for the release manager to verify that the bits in the release are exactly what is expected.





> Automate release process
> ------------------------
>
>                 Key: MAHOUT-1668
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1668
>             Project: Mahout
>          Issue Type: Task
>            Reporter: Stevo Slavic
>            Assignee: Stevo Slavic
>             Fix For: 0.10.0
>
>
> 0.10.0 will be first release since project switched to git. Some changes have to be made in build scripts to support the release process, the Apache way. As consequence, how-to-make-release docs will likely need to be updated as well. Also, it would be nice to automate release process as much as possible, e.g. via dedicated Jenkins build job(s), so it's easy for any committer to cut out a release for vote, and after vote either finalize release or easily make a new RC - this will enable us to release faster and more often.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)