Repository: mahout Updated Branches: refs/heads/branch-0.14.0 5acdd99d3 -> 98d345cbc
MAHOUT-2037 Release Plugin Project: http://git-wip-us.apache.org/repos/asf/mahout/repo Commit: http://git-wip-us.apache.org/repos/asf/mahout/commit/98d345cb Tree: http://git-wip-us.apache.org/repos/asf/mahout/tree/98d345cb Diff: http://git-wip-us.apache.org/repos/asf/mahout/diff/98d345cb Branch: refs/heads/branch-0.14.0 Commit: 98d345cbca531ab8906a447b3c949d9871462cf1 Parents: 5acdd99 Author: Trevor a.k.a @rawkintrevo <[email protected]> Authored: Tue Jun 5 11:38:37 2018 -0500 Committer: Trevor a.k.a @rawkintrevo <[email protected]> Committed: Tue Jun 5 11:38:37 2018 -0500 ---------------------------------------------------------------------- website/developers/how-to-release.md | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mahout/blob/98d345cb/website/developers/how-to-release.md ---------------------------------------------------------------------- diff --git a/website/developers/how-to-release.md b/website/developers/how-to-release.md index 92912d1..8c4eb5e 100644 --- a/website/developers/how-to-release.md +++ b/website/developers/how-to-release.md @@ -45,18 +45,9 @@ warnings) 1. Check that all tests pass after a clean compile: `mvn clean test` 1. Check that there are no remaining unresolved Jira issues with the upcoming version number listed as the "Fix" version 1. Publish any previously unpublished third-party dependenciess: [Thirdparty Dependencies](thirdparty-dependencies.html) -1. Build and preview resulting artifacts: - ```bash - cd buildtools - ./build-all-release-jars.sh - ``` -1. Make sure packages will come out looking right <a name="HowToRelease-Makingarelease"></a> ## Making a release -* Check if documentation needs an update -* *Needs correction* Update the web site's news by updating a working copy of the SVN directory at https://svn.apache.org/repos/asf/mahout/site/new_website -* *Needs clarification* Commit these changes. It is important to do this prior to the build so that it is reflected in the copy of the website included with the release for documentation purposes. * If this is your first release, add your key to the KEYS file (located on GitHub at https://github.com/apache/mahout/master/distribution/KEYS) and copy it to the release directory. Make sure you commit your change. See http://www.apache.org/dev/release-signing.html. * Ensure you have set up standard Apache committer settings in ~/.m2/settings.xml as per [this page](http://maven.apache.org/developers/committer-settings.html) @@ -88,12 +79,15 @@ warnings) </server> ``` -* *Clarify which env var is better or choose one* Set environment variable `MAVEN_OPTS` to `-Xmx1024m` to ensure the tests can run: `export JAVA_OPTIONS="-Xmx1g"` + * If you are outside the US, then svn.apache.org may not resolve to the main US-based Subversion servers. (Compare the IP address you get for svn.apache.org with svn.us.apache.org to see if they are different.) This will cause problems during the release since it will create a revision and then immediately access, but, there is a replication lag of perhaps a minute to the non-US servers. To temporarily force using the US-based server, edit your equivalent of /etc/hosts and map the IP address of svn.us.apache.org to svn.apache.org. * Create the release candidate: `mvn -Pmahout-release,apache-release release:prepare release:perform` -`mvn -Papache-release release:perform` + * If you have problems authenticating to svn.apache.org, try adding to the command line `-Dusername=USERNAME -Dpassword=PASSWORD` -* If there is an issue first try doing: `mvn -Dmahout-release,apache-release release:rollback` followed by `mvn -Dmahout-release,apache-release,hadoop2 release:clean` as this will likely save you time and do the right thing. You may also have to rollback the version numbers in the POM files. If you want to skip test cases while rebuilding, use `mvn -DpreparationGoals="clean compile" release:prepare release:perform` +* If there is an issue first try doing: + 1. `mvn -Dmahout-release,apache-release release:rollback` + 1. followed by `mvn -Dmahout-release,apache-release release:clean` as this will likely save you time and do the right thing. You may also have to rollback the version numbers in the POM files. + 1. _Optional_ If you want to skip test cases while rebuilding, use `mvn -DpreparationGoals="clean compile" release:prepare release:perform` * Review the artifacts, etc. on the Apache Repository (using Sonatype's Nexus application) site: https://repository.apache.org/. You will need to login using your ASF SVN credentials and then browse to the staging area. * Once you have reviewed the artifacts, you will need to "Close" out the staging area under Nexus, which then makes the artifacts available for
