[
https://issues.apache.org/jira/browse/MAHOUT-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Palumbo updated MAHOUT-2076:
-----------------------------------
Summary: add a /release directory with a skeleton settings.xml for releases
and instructions/scripts to release/deploy and any mixture therof (was: add a
/release directory with a skeleton settings.xml for releases)
> add a /release directory with a skeleton settings.xml for releases and
> instructions/scripts to release/deploy and any mixture therof
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-2076
> URL: https://issues.apache.org/jira/browse/MAHOUT-2076
> Project: Mahout
> Issue Type: New Feature
> Components: release
> Affects Versions: 0.14.0
> Reporter: Andrew Palumbo
> Assignee: Joe Olson
> Priority: Minor
> Fix For: 14.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> add a {{/release}} directory with {{settings.xml}} and all necessary variable
> changes to make a release candidate and to deploy.
> {code:bash}
> change-scalaversion.sh 2.11
> mvn release:prepare -Papache-release
> mvn release:perform -Papache-release
> change-scala-version 2.12
> mvn release:prepare -Papache-release
> mvn release:perform -Papache-release{code}
>
> It may be as simple as adding your personal GPG information to the
> `~/.m2/settings.xml` file. and running a script like above. Spark and Flink
> have examples which could be overkill:
> Spark:
> [https://github.com/apache/spark/blob/master/dev/make-distribution.sh]
> [https://github.com/apache/spark/tree/master/dev/create-release]
> Flink:
> [https://github.com/apache/flink/tree/master/tools/releasing]
> I would also propose that we consider a {{Makefile}} for our builds or
> {{cmake}}, as we are moving closer to python and .cpp modules. Could be
> useful, we should at least consider it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
