[
https://issues.apache.org/jira/browse/MAHOUT-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Palumbo updated MAHOUT-2076:
-----------------------------------
Description:
add a {{{{/release}}}} directory with {{settins.xml}}}}\{{and all necessary
variable changes to make a release with: }}
{{```bash}}
change-scalaversion.sh 2.11
{{mvn release:prepare -Papache-release}}
mvn release:perfoerm -Papache-release
change scala versionm 2.12
```
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 wouls also prpose that we consider Makefiles for our builds, as we are moving
closer to python and .cpp modules. Could be useful, we should at least
consider it.
was:
add a {{{{/release}}}} directory with {{settins.xml}}}}{{and all necessary
variable changes to make a release with: }}
{{```bash}}
change-scalaversion.sh 2.11
{{mvn release:prepare -Papache-release}}
mvn release:perfoerm -Papache-release
change scala versionm 2.12
```
It may be as simple as adding your personal GPG information to the
`~/.m2/settings.xml` file. and running a script like above. Pulas and spark
have nice examples:
> add a /release directory with a skeleton settings.xml for releases
> ------------------------------------------------------------------
>
> 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: Andrew Palumbo
> Priority: Minor
> Fix For: 14.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> add a {{{{/release}}}} directory with {{settins.xml}}}}\{{and all necessary
> variable changes to make a release with: }}
> {{```bash}}
> change-scalaversion.sh 2.11
> {{mvn release:prepare -Papache-release}}
> mvn release:perfoerm -Papache-release
> change scala versionm 2.12
> ```
>
> 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 wouls also prpose that we consider Makefiles for our builds, 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)
