reckart opened a new issue, #184: URL: https://github.com/apache/uima-ruta/issues/184
**Preparations** - [ ] Create release issue and release preparation branch - [ ] Update README.md file - [ ] Update RELEASE_NOTES.md file - [ ] Check the LICENSE and NOTICE files for the binary release / Eclipse plugins - [ ] Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies - [ ] Update API reference version in POM **Building** - [ ] Clean local `.m2` repository - [ ] Commit all changes and check out in a new clean build location - [ ] Run a trial 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`) **Staging** - [ ] Close the staging repository at https://repository.apache.org/ ↳https://repository.apache.org/content/repositories/orgapacheuima-1304 **Voting** - [ ] Call for a vote on the developer mailing list - [ ] Close vote and post vote results to the developer mailing list (wait at least for 72 hours, at least 3 +1 votes required for release, sign mail using same GPG key that was used to sign release) **Publishing** Copy the release artifacts from the staging spot to the dist spot in SVN - [ ] Copy the release artifacts from the staging spot to the dist spot in SVN `svn mv -m "Move final release candidate to dist spot" https://dist.apache.org/repos/dist/dev/uima/ruta-3.4.1-RC-202402051009-68e2f26/ https://dist.apache.org/repos/dist/release/uima/ruta-3.4.1` - [ ] **No need to do this next time because 3.4.1 was already archived** Copy existing Eclipse update site to the archive spot `svn copy -m "svn copy -m "Create eclipse plugin archive for ruta 3.4.0" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/ruta https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/ruta-3.4.0` - [ ] Delete existing Eclipse update site `svn rm -m "Removing previous update site to make space for new one" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/ruta` - [ ] Move the new update site from staging spot to release spot `svn mv -m "Installing Ruta 3.4.1 update site from accepted RC1" https://dist.apache.org/repos/dist/release/uima/ruta-3.4.1/eclipse-update-site/ https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/ruta` - [ ] Copy existing Eclipse update site to the archive spot `svn copy -m "Create eclipse plugin archive for ruta 3.4.1" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/ruta https://dist.apache.org/repos/dist/release/uima/archive-eclipse-update-site/ruta-3.4.1` - [ ] Release staging repository at https://repository.apache.org/ - [ ] Create a new git tag e.g. `rel/ruta-3.4.1` and remove the one not prefixed with `rel` - [ ] Merge the release preparation pull request - [ ] **No need to do this next time because 3.4.1 was already archived** Archive website: `svn copy -m "Creating versioned copy of current release documentation in archive" https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/ruta-current https://svn.apache.org/repos/asf/uima/site/archive/docs/d/ruta-3.4.0` - [ ] Update website - [ ] Archive website: `svn copy -m "Creating versioned copy of current release documentation in archive" https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/ruta-current https://svn.apache.org/repos/asf/uima/site/archive/docs/d/ruta-3.4.1` - [x] Register the release in [Whimsy](https://reporter.apache.org/addrelease.html?uima) - [x] Post release announcement to annou...@apache.org (Cc: dev@uima.apache.org, u...@uima.apache.org — once release has arrived at https://repo1.maven.org/maven2/org/apache/uima/ruta-core/ — sign mail using same GPG key that was used to sign release) - [ ] Close the release in the issue tracker -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@uima.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
