You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2021/07/02 12:58:00 UTC
[jira] [Updated] (UIMA-6328) UIMA Java SDK 2.11.0 release
[ https://issues.apache.org/jira/browse/UIMA-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6328:
---------------------------------------------
Description:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} 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
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) 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!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** 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)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) 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 {{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)
was:
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.html}} 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
- (/) Update the version in the {{uimaj-eclipse-update-site}}
- (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
- (/) 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!)
- (/) Call for a vote including URLs for
** Issue list
** Staging repository
** SVN staging spot (artifacts)
** SVN staging spot (update site)
** Git tag
- (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)
- (x) Copy the release artifacts from the staging spot to the dist spot in SVN
- (x) 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 {{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)
> UIMA Java SDK 2.11.0 release
> ----------------------------
>
> Key: UIMA-6328
> URL: https://issues.apache.org/jira/browse/UIMA-6328
> Project: UIMA
> Issue Type: Task
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
>
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.html}} 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
> - (/) Update the version in the {{uimaj-eclipse-update-site}}
> - (/) Build the {{uimaj-eclipse-update-site}} module with {{-Papache-release}}
> - (/) 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!)
> - (/) Call for a vote including URLs for
> ** Issue list
> ** Staging repository
> ** SVN staging spot (artifacts)
> ** SVN staging spot (update site)
> ** 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)
> - (x) Copy the release artifacts from the staging spot to the dist spot in SVN
> - (x) 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 {{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)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)