[ https://issues.apache.org/jira/browse/UIMA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6395: --------------------------------------------- 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* - (x) Copy the release artifacts from the staging spot to the dist spot in SVN - (/) 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}} - (x) Delete existing Eclipse update site {{svn delete -m "reset main Eclipse update subsite for uimaj - delete old one" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}} - (x) FIXME Remove the old update site and move the new one in at {{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}} - (x) Release staging repository at {{http://repository.apache.org/}} - (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not prefixed with {{rel}} - (x) Merge the release branch - (x) Update website - (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/uimaj-core/}} -- sign mail using same GPG key that was used to sign release) was: *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 - (x) VOTE (wait at least for 72 hours, at least 3 +1 votes required for release) - (x) Post vote results (sign mail using same GPG key that was used to sign release) *Publish release* - (x) Copy the release artifacts from the staging spot to the dist spot in SVN - (/) 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}} - (x) Delete existing Eclipse update site {{svn delete -m "reset main Eclipse update subsite for uimaj - delete old one" https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}} - (x) FIXME Remove the old update site and move the new one in at {{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}} - (x) Release staging repository at {{http://repository.apache.org/}} - (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not prefixed with {{rel}} - (x) Merge the release branch - (x) Update website - (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/uimaj-core/}} -- sign mail using same GPG key that was used to sign release) > Apache UIMA Java SDK 3.3.0 release > ---------------------------------- > > Key: UIMA-6395 > URL: https://issues.apache.org/jira/browse/UIMA-6395 > Project: UIMA > Issue Type: Task > Components: Core Java Framework > Reporter: Richard Eckart de Castilho > Assignee: Richard Eckart de Castilho > Priority: Major > > *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* > - (x) Copy the release artifacts from the staging spot to the dist spot in SVN > - (/) 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}} > - (x) Delete existing Eclipse update site {{svn delete -m "reset main Eclipse > update subsite for uimaj - delete old one" > https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3/uimaj}} > - (x) FIXME Remove the old update site and move the new one in at > {{https://dist.apache.org/repos/dist/release/uima/eclipse-update-site-v3}} > - (x) Release staging repository at {{http://repository.apache.org/}} > - (x) Create a new git tag e.g. {{rel/uimaj-3.2.0}} and remove the one not > prefixed with {{rel}} > - (x) Merge the release branch > - (x) Update website > - (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/uimaj-core/}} -- sign > mail using same GPG key that was used to sign release) -- This message was sent by Atlassian Jira (v8.20.7#820007)