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=11&rev2=12 Comment: - bring release process current == Making a release == - 1. Update version numbers (from X.Y-dev to X.Y) for release in: - * pom.xml - version tag + 0. svn co https://svn.apache.org/repos/asf/tika/trunk tika + 1. Update CHANGES.txt with release date (Release X.Y - MM/dd/yyyy) and (if needed) add additional changelog entries + a. Create version in JIRA for release X.Y and X.Y+1 if not already done + b. Move any lingering issues from X.Y not already resolved to X.Y+1 + 2. svn commit -m "Update CHANGES.txt for X.Y release." CHANGES.txt + 3. setenv MAVEN_OPTS "-Xms128m -Xmx256m" (or export MAVEN_OPTS="-Xms128m -Xmx256m" if you are using bash) + 4. mvn release:prepare + a. Make sure all the release numbers are set to X.Y (from X.Y-dev) + b. tika tag name should be X.Y (version number) + c. watch for BUILD SUCCESSFUL message + 5. mvn release:perform + 6. Head over to https://repository.apache.org/ (Apache's Nexus Server) + a. Login with your ASF username and password + b. "Close" the staging repository with message Apache Tika X.Y release candidate #N. + c. Copy the URL from the closed staged repository for tika (you'll need this later) + 7. check in the contents of target/checkout/target/tika-X.Y.zip{.asc|.md5|.sha}, tika-app-X.Y.jar{.asc|.md5|.sha} and tika-server-X.Y.war (from tika-server/target/) and CHANGES.txt (rename to CHANGES-X.Y.txt) into: + a. https://dist.apache.org/repos/dist/dev/tika/ - 2. Update CHANGES.txt with release date (Release X.Y - MM/dd/yyyy) and (if needed) add additional changelog entries + 8. See the file in target/checkout/target/vote.txt - it contains the contents of the + release email you should send (with subject [VOTE] Apache Tika X.Y release to + [email protected] and to [email protected]). Add to it + some text like the following: - 3. Check if documentation needs an update + {{{ + In addition a staged Maven repository is available here: + <paste URL from #6c> + }}} - 4. Update news in src/site/src/documentation/content/xdocs/index.xml and for main lucene.apache.org site stored at https://svn.apache.org/repos/asf/lucene/site/. The second change may require additional rights + Also update the email to include links to the artifacts from #7 (including .sha, .md5 and + .asc and CHANGES.txt) - 5. Commit all these changes + 9. If the VOTE passes (else head back to #1) + a. send [RESULT] [VOTE] tallying the VOTE to [email protected] and [email protected] + b. head over to Nexus from #6 and "Release" the repository with message Apache Tika X.Y release. + c. svn mv https://dist.apache.org/repos/dist/dev/tika/* to https://dist.apache.org/repos/dist/release/tika/ - 6. Make a clean checkout - * svn co https://svn.apache.org/repos/asf/tika/trunk + 10. Deploy new Tika site (according to Website Update HOWTO (tika/site$ mvn install)). + 11. Send announcements to the user and developer lists - see http://s.apache.org/2hC for a sample. - 7. Build it. - * mvn package - - 8. Run unit tests - * mvn test - - 9. Do basic test to see if release looks ok - e.g. install it and run Tika command line on a sample document - - 10. Branch it for release maintenance - * svn copy https://svn.apache.org/repos/asf/lucene/tika/trunk \ - https://svn.apache.org/repos/asf/lucene/tika/branches/X.Y -m "Tika X.Y release maintenance branch and rc working copy." - 11. Create a branch for release maintenance - - 12. Sign it - [[http://www.apache.org/dev/mirror-step-by-step.html|Step-By-Step Guide to Mirroring Releases]]. - * e.g., gpg --armor --output tika-X.Y.tar.gz.asc --detach-sig tika-X.Y.tar.gz \ - md5sum tika-X.Y.tar.gz > tika-X.Y.tar.gz.md5 - - 13. Release Review and Vote: Use the following email as a template for a real email sent to the [email protected] and the [email protected] lists, calling for a vote on the release candidate (posted on a publicly accessible website): - - ---- - Hi Folks, - - I have posted a candidate for the Apache Tika X.Y release at - - http://people.apache.org/~yourusername/tika_X.Y/rcN/ - - See the included CHANGES.txt file for details on release contents and latest changes. The release was made from the X.Y-dev trunk. - - Please vote on releasing these packages as Apache Tika X.Y. The vote is open for the next 72 hours. Only votes from Lucene PMC and Tika committers are binding, but everyone is welcome to check the release candidate and voice their approval or disapproval. The vote passes if at least three binding +1 votes are cast. - - [ ] +1 Release the packages as Apache Tika X.Y. - - [ ] -1 Do not release the packages because... - - Thanks! - ----- - - 14. Based on feedback, cut new release candidates and update accordingly - - 15. Once vote passes, tag the tika release: - * svn copy https://svn.apache.org/repos/asf/lucene/tika/trunk \ - https://svn.apache.org/repos/asf/lucene/tika/tika/tags/X.Y -m "Tika X.Y release." - - 16. Copy release tar file to people.apache.org:/www/www.apache.org/dist/lucene/tika. based on vote (also included *.asc file and *.md5 file) - - 17. Wait 24 hours for release to propagate to mirrors. - - 18. Deploy new Tika site (according to Website Update HOWTO (tika/site$ mvn install)). - - 19. Deploy new main Lucene site (according to Website Update HOWTO but modified for Lucene site - update is to be performed in /www/lucene.apache.org directory). - - 20. Update Javadoc in people.apache.org:/www/lucene.apache.org/tika/apidocs. - - 21. Create version in JIRA for release X.Y. - - 22. Send announcements to the user and developer lists. - - == Preparing for new development == - - 1. Update version numbers for to A.B-dev (assuming A.B is next release number) in: - * pom.xml - version tag - - 2. Update CHANGES.txt with header for new changes - - 3. Create version in JIRA for development snapshots (A.B-dev) -
