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 ChrisMattmann: https://wiki.apache.org/tika/ReleaseProcess?action=diff&rev1=35&rev2=36 Comment: - update guide for Git 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` + 1. `git clone https://git-wip-us.apache.org/repos/asf/tika.git release` 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. 1. Move any lingering unresolved issues from X.Y to X.(Y+1). - 1. `svn commit -m "Update CHANGES.txt for X.Y release." CHANGES.txt` + 1. `git add CHANGES.txt && git commit -m "Update CHANGES.txt for X.Y release." && git push origin` 1. Run `apache-rat:check` and fix any missing license headers / add excluded for properly non-licensed fails 1. `setenv MAVEN_OPTS "-Xms128m -Xmx256m"` (or `export MAVEN_OPTS="-Xms128m -Xmx256m"` if you are using bash) 1. `mvn release:prepare` @@ -43, +43 @@ 2. Head over to Nexus from #6 and "Release" the repository with message Apache Tika X.Y release (and make sure the box is checked to auto drop). 3. `svn rm https://dist.apache.org/repos/dist/release/tika/*` 4. `svn mv https://dist.apache.org/repos/dist/dev/tika/* https://dist.apache.org/repos/dist/release/tika/` - 5. `svn mv https://svn.apache.org/repos/asf/tika/tags/X.Y-rcN https://svn.apache.org/repos/asf/tika/tags/X.Y` + 5. `git clone https://git-wip-us.apache.org/repos/asf/tika.git X.Y-rcN` + 6. `git tag X.Y && git push --tags` The `*` wildcard will not work. * Else: 1. Drop the new Tika staging repository on repository.apache.org. @@ -68, +69 @@ 2. `cp /tika/trunk/tika-server/target/miredot /tika/site/src/resources/X.Y` 11. Check everything looks good with `mvn site:run`. 12. `mvn clean install` - 13. `svn commit -m "Update website for X.Y release."` + 13. `git add <any files changed for site> && git commit -m "Update website for X.Y release." && git push origin` 14. On the Tika JIRA, "release" version X.Y and update any (new) straggler X.Y issues to X.(Y+1). 15. Send announcements to [email protected], [email protected], and [email protected] lists (from your Apache email) - see http://s.apache.org/2hC for a sample. 16. Log on to https://reporter.apache.org/addrelease.html?tika and add the release data (version and date) to the database
