[
https://issues.apache.org/jira/browse/UIMA-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6449:
---------------------------------------------
Description:
Ruta has no binary tarball release in which we would have to update
LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
bundles third-party JARs also used by the other Ruta bundles. It is the only
bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
up-to-date.
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (/) Update {{RELEASE_NOTES.md}} file
(https://issues.apache.org/jira/projects/UIMA/versions/12351726)
- (/) Check the LICENSE and NOTICE files for the binary release
- (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update API reference version in POM {{api_check_oldVersion}}
- (x) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
*Release build*
- (x) Clean local {{.m2/repository}}
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (x) Close the staging repository at {{https://repository.apache.org/}}
- (x) Check auto-staged artifacts at
{{https://dist.apache.org/repos/dist/dev/uima/}}
*Vote*
- (x) 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 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) 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}}
- (x) 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}}
- (x) 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}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) 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}}
- (x) 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}}
- (x) 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}}
- (x) Close release in Jira and GitHub
- (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:
Ruta has no binary tarball release in which we would have to update
LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
bundles third-party JARs also used by the other Ruta bundles. It is the only
bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
up-to-date.
*Prepare the code*
- (/) Create release branch
- (/) Update {{README}} file
- (x) Update {{RELEASE_NOTES.md}} file
(https://issues.apache.org/jira/projects/UIMA/versions/12351726)
- (x) Check the LICENSE and NOTICE files for the binary release
- (x) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
- (/) Update API reference version in POM {{api_check_oldVersion}}
- (x) Check that the Eclipse `classpath` files which are checked in as part of
the examples have the proper version numbers for their JARs
*Release build*
- (x) Clean local {{.m2/repository}}
- (x) Do a test build locally with {{-Papache-release}}
- (x) Check the issues report in {{issuesFixed}} if it looks ok
- (x) Do the release build ({{mvn -DautoVersionSubmodules=true release:prepare
release:perform}})
*Stage release candidate*
- (x) Close the staging repository at {{https://repository.apache.org/}}
- (x) Check auto-staged artifacts at
{{https://dist.apache.org/repos/dist/dev/uima/}}
*Vote*
- (x) 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 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) 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}}
- (x) 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}}
- (x) 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}}
- (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
- (x) Create new maintenance branch (when doing feature releases)
- (x) Update the version on the development branch (when doing feature releases)
- (x) Update the "current" release on the website with the new content (and
delete anything no longer part of the "current" release)
- (x) 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}}
- (x) 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}}
- (x) 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}}
- (x) Close release in Jira and GitHub
- (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)
> Ruta 3.2.0 release
> ------------------
>
> Key: UIMA-6449
> URL: https://issues.apache.org/jira/browse/UIMA-6449
> Project: UIMA
> Issue Type: Task
> Components: Ruta
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
>
> Ruta has no binary tarball release in which we would have to update
> LICENSE/NOTICE files. However, it has the {{ruta-ep-engine}} module which
> bundles third-party JARs also used by the other Ruta bundles. It is the only
> bundle that declares {{Embed-Dependency}}. So when updating dependencies, we
> need to check the files in {{ruta-ep-engine/src/main/readme_bin}} are
> up-to-date.
> *Prepare the code*
> - (/) Create release branch
> - (/) Update {{README}} file
> - (/) Update {{RELEASE_NOTES.md}} file
> (https://issues.apache.org/jira/projects/UIMA/versions/12351726)
> - (/) Check the LICENSE and NOTICE files for the binary release
> - (/) Make sure to remove all SNAPSHOT repositories and SNAPSHOT dependencies
> - (/) Update API reference version in POM {{api_check_oldVersion}}
> - (x) Check that the Eclipse `classpath` files which are checked in as part
> of the examples have the proper version numbers for their JARs
> *Release build*
> - (x) Clean local {{.m2/repository}}
> - (x) Do a test build locally with {{-Papache-release}}
> - (x) Check the issues report in {{issuesFixed}} if it looks ok
> - (x) Do the release build ({{mvn -DautoVersionSubmodules=true
> release:prepare release:perform}})
> *Stage release candidate*
> - (x) Close the staging repository at {{https://repository.apache.org/}}
> - (x) Check auto-staged artifacts at
> {{https://dist.apache.org/repos/dist/dev/uima/}}
> *Vote*
> - (x) 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 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) 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}}
> - (x) 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}}
> - (x) 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}}
> - (x) Release staging repository at {{https://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 into the development branch (e.g. {{main}})
> - (x) Create new maintenance branch (when doing feature releases)
> - (x) Update the version on the development branch (when doing feature
> releases)
> - (x) Update the "current" release on the website with the new content (and
> delete anything no longer part of the "current" release)
> - (x) 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}}
> - (x) 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}}
> - (x) 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}}
> - (x) Close release in Jira and GitHub
> - (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)
