Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tika Wiki" for change notification.
The "ReleaseProcess" page has been changed by NickBurch: https://wiki.apache.org/tika/ReleaseProcess?action=diff&rev1=33&rev2=34 Comment: Add rat step, and tweak numbering Either way, please update these instructions with any clarifications you think might help the next release manager. 1. `svn co https://svn.apache.org/repos/asf/tika/trunk release` - 2. Update CHANGES.txt with release date (Release X.Y - MM/dd/yyyy) and (if needed) add additional changelog entries. + 1. Update CHANGES.txt with release date (Release X.Y - MM/dd/yyyy) and (if needed) add additional changelog entries. 1. On the Tika JIRA, create versions X.Y, X.(Y+1), and X.(Y+2), if not already done. - 2. Move any lingering unresolved issues from X.Y to X.(Y+1). + 1. Move any lingering unresolved issues from X.Y to X.(Y+1). - 3. `svn commit -m "Update CHANGES.txt for X.Y release." CHANGES.txt` + 1. `svn commit -m "Update CHANGES.txt for X.Y release." CHANGES.txt` + 1. Run `apache-rat:check` and fix any missing license headers / add excluded for properly non-licensed fails - 4. `setenv MAVEN_OPTS "-Xms128m -Xmx256m"` (or `export MAVEN_OPTS="-Xms128m -Xmx256m"` if you are using bash) + 1. `setenv MAVEN_OPTS "-Xms128m -Xmx256m"` (or `export MAVEN_OPTS="-Xms128m -Xmx256m"` if you are using bash) - 5. `mvn release:prepare` + 1. `mvn release:prepare` 1. Make sure all the release numbers are set to X.Y (from X.Y-dev) - 2. When prompted, the scm tag name should be X.Y (version number). If this is a release candidate, the tag should be X.Y-rcN. + 1. When prompted, the scm tag name should be X.Y (version number). If this is a release candidate, the tag should be X.Y-rcN. - 3. Watch for a `BUILD SUCCESSFUL` message + 1. Watch for a `BUILD SUCCESSFUL` message - 4. Make sure you have `gnupg` (or variant) installed (see http://www.apache.org/dev/openpgp.html) + 1. Make sure you have `gnupg` (or variant) installed (see http://www.apache.org/dev/openpgp.html) - 6. `mvn release:perform` + 1. `mvn release:perform` 1. Make sure you can log on to https://repository.apache.org/ - 2. Make sure you have the following entry in your `~/.m2/settings.xml` file: http://maven.apache.org/settings.html#Servers. The server ID should be apache.releases.https. + 1. Make sure you have the following entry in your `~/.m2/settings.xml` file: http://maven.apache.org/settings.html#Servers. The server ID should be apache.releases.https. - 7. Head over to https://repository.apache.org/ (Apache's Nexus Server) + 1. Head over to https://repository.apache.org/ (Apache's Nexus Server) 1. Login with your ASF username and password - 2. "Close" the staging repository with message `Apache Tika X.Y release candidate #N`. + 1. "Close" the staging repository with message `Apache Tika X.Y release candidate #N`. - 3. Copy the URL from the closed staged repository for Tika (you'll need this later) + 1. Copy the URL from the closed staged repository for Tika (you'll need this later) - 8. Update CHANGES.txt with a "Release X.Y + 1 - Current Development" section. + 1. Update CHANGES.txt with a "Release X.Y + 1 - Current Development" section. - 9. Check the contents of `target/checkout/target/X.Y/*` into https://dist.apache.org/repos/dist/dev/tika/ (tika-X.Y-src.zip{.asc|.md5|.sha}, tika-app-X.Y.jar{.asc|.md5|.sha} and tika-server-X.Y.jar{.asc|.md5|.sha}, and CHANGES.txt. + 1. Check the contents of `target/checkout/target/X.Y/*` into https://dist.apache.org/repos/dist/dev/tika/ (tika-X.Y-src.zip{.asc|.md5|.sha}, tika-app-X.Y.jar{.asc|.md5|.sha} and tika-server-X.Y.jar{.asc|.md5|.sha}, and CHANGES.txt. 1. `svn co https://dist.apache.org/repos/dist/dev/tika/ dist.dev.tika` 2. `cd dist.dev.tika` 3. `svn rm ./*`
