Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Prepare the code
Create release branch- Update README file
- Update RELEASE_NOTES.md 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
- Check that the Eclipse `classpath` files which are checked in as part of the examples have the proper version numbers for their JARs
- Update the version in the uimaj-eclipse-update-site
- Set dropPrevVersions to true in the uimaj-eclipse-update-site POM
Release build
- Clean local m2 repository
- Do a test build locally with -Papache-release
- Check the issues report in issuesFixed if it looks ok
- Do the release build (mvn -DautoVersionSubmodules=true release:prepare release:perform)
- Build the Eclipse update site using mvn -f uimaj-eclipse-update-site/pom.xml clean install -Papache-release
Stage release candidate
- 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
- Copy the update site to a subdirectory of the release staging spot and commit (Caution: the update site contains a .svn folder that needs to be removed!)
Vote
- Call for a vote including URLs for
- 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)
Publish release
- Copy existing Eclipse update site to the archive spot: svn copy -m "create eclipse plugin archive for uimaj-3.0.0-3.2.0" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/uimaj-3.0.0-3.2.0
- Remove old Eclipse update site: svn rm -m "Removing previous UIMAJ update site to make space for new one" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
- Move new Eclipse update site from the staging to the release spot: svn mv -m "Installing UIMAJ 3.3.0 update site from accepted RC3" https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3/eclipse-update-site-v3/uimaj https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj
- Move the other release artifacts from the staging spot to the dist spot in SVN: svn mv -m "Installing UIMAJ 3.3.0 final to release spot" https://dist.apache.org/repos/dist/dev/uima/uima-uimaj-3.3.0-RC3 https://dist.apache.org/repos/dist/release/uima/uimaj-3.3.0
- Release staging repository at https://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 into the development branch (e.g. main)
- Create new maintenance branch (when doing feature releases)
- Update the version on the development branch (when doing feature releases)
- Update the "current" release on the website with the new content (and delete anything no longer part of the "current" release)
- Copy the "current" release to a versioned release svn copy -m "Current UIMAJ release is 3.3.0" https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0
- Copy the versioned release to the archive spot already: svn copy -m "Archiving UIMAJ 3.3.0 documentation" https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.3.0 https://svn.apache.org/repos/asf/uima/site/archive/docs/d/uimaj-3.3.0
- Delete the previous version documentation: svn rm -m "Deleting documentation for previous release" https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-3.2.0
- Close release in Jira and GitHub
- Post release announcement to announce@apache.org (Cc: dev@uima.apache.org, user@uima.apache.org – 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)
Attachments
Issue Links
- links to