You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tika.apache.org by Apache Wiki <wi...@apache.org> on 2017/12/08 23:15:59 UTC
[Tika Wiki] Update of "ReleaseProcess" by TimothyAllison
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 TimothyAllison:
https://wiki.apache.org/tika/ReleaseProcess?action=diff&rev1=51&rev2=52
1. `git clone https://github.com/apache/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. 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. Query open issues: e.g. "project = Tika AND resolution = unresolved AND fixVersion = 1.16"
1. Upper right, select bulk change
@@ -29, +29 @@
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.
1. Head over to https://repository.apache.org/ (Apache's Nexus Server)
1. Login with your ASF username and password
+ 1. Make sure there is only one repo from your build and that it contains everything. A transmission failure can lead to multiple repositories, none of which are valid
1. "Close" the staging repository with message `Apache Tika X.Y release candidate #N`.
1. Copy the URL from the closed staged repository for Tika (you'll need this later)
1. Update CHANGES.txt with a "Release X.Y + 1 - Current Development" section.