[UIMA-6331] uimaFIT 3.2.0 release

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.2.0uimaFIT
• Component/s: uimaFIT
• Assignee: Richard Eckart de Castilho
• Reporter: Richard Eckart de Castilho
• Created: 05/Mar/21 13:53
• Updated: 07/May/21 10:36
• Resolved: 07/May/21 10:36

Description

• Create release branch
• Update README file
• Check the LICENSE and NOTICE files for the binary release
• Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
• Update Jira version in POM for fixed-issues report
• Update API comparison version in POM
• Clean local m2 repository and build locally with -Papache-release
• Check the issues report in issuesFixed if it looks ok
• Check that the Java version in the current terminal java -version corresponds to the minimum supported version (i.e. Java 1.8)
• Do the release build (mvn -DautoVersionSubmodules=true release:prepare release:perform)
• Close the staging repository at http://repository.apache.org/
• Check out release staging svn spot https://dist.apache.org/repos/dist/dev/uima/
• Copy artifacts from target/checkout/target to a subdirectory of the release staging spot
• Call for a vote including URLs for
  • Issue list
  • Staging repository
  • SVN staging spot (artifacts)
  • Git tag
• VOTE (wait at least for 72 hours, at least 3 +1 votes required for release)
• Post vote results (sign mail using same GPG key that was used to sign release)
• Copy the release artifacts from the staging spot to the dist spot in SVN (and remove older release)
• Release staging repository at http://repository.apache.org/
• Create a new git tag e.g. rel/uimaj-3.2.0 and remove the one not prefixed with rel
• Merge the release branch
• Update website
• Post release announcement to [e-mail] (Cc: [e-mail], [e-mail] – once release has arrived at https://repo1.maven.org/maven2/org/apache/uima/uimaj-core/ – sign mail using same GPG key that was used to sign release)

Issue Links

• links to: GitHub Pull Request #152